An administrator configures secure network access to an Azure Storage account named stcorpdata. The administrator disables public network access to the storage account and deploys a Private Endpoint in Subnet-App within a virtual network named VNet-Core. A private DNS zone named privatelink.blob.core.windows.net is created and linked to VNet-Core, containing a DNS A record pointing stcorpdata.blob.core.windows.net to the private IP address of the Private Endpoint.
An Azure Virtual Machine named VM-App is deployed in a peered virtual network named VNet-Spoke. Although the virtual network peering between VNet-Core and VNet-Spoke is successfully established, applications on VM-App cannot connect to the storage account because they resolve stcorpdata.blob.core.windows.net to its public IP address instead of its private IP address.
What should the administrator do to resolve the DNS resolution issue from VM-App?
- Link the private DNS zone privatelink.blob.core.windows.net to the VNet-Spoke virtual network.Cevap
- BConfigure gateway transit on the virtual network peering connection between VNet-Core and VNet-Spoke.
- CAssign the Private DNS Zone Contributor role on the private DNS zone to the managed identity of VM-App.
- DCreate an inbound Network Security Group (NSG) rule in Subnet-App that allows DNS queries (UDP port 53) from VNet-Spoke.