MENU
A customer requires Azure NetApp Files volumes to be contained in a specially purposed subnet within your Azure Virtual Network (VNet). The volumes can be accessed directly from within Azure over VNet peering or from on-premises over a Virtual Network Gateway.
Which subnet can the customer use that is dedicated to Azure NetApp Files without being connected to the public Internet?
Azure NetApp Files volumes need to be placed in a specially purposed subnet within your Azure Virtual Network (VNet) to ensure proper isolation and security. This subnet must be delegated specifically to Azure NetApp Files services.
A delegated subnet in Azure allows certain Azure resources (like Azure NetApp Files) to have exclusive use of that subnet. It ensures that no other services or VMs can be deployed in that subnet, enhancing security and performance. Moreover, it ensures that the volumes are only accessible through private connectivity options like VNet peering or a Virtual Network Gateway, without any exposure to the public internet.
Subnets such as basic, default, or dedicated do not have the specific delegation capabilities required for Azure NetApp Files, making delegated the correct answer for this scenario.