AZ-700 Question 37
Single answerYou have an Azure private DNS zone named internal.corp. A new virtual network named VNet01 has been deployed, and your team wants all resources in VNet01 to resolve DNS queries for internal.corp using Azure� built-in DNS. Which method should you use to achieve this requirement?
- A
Create a virtual network link from the private DNS zone (internal.corp) to VNet01, enabling auto-registration if needed.
- B
Manually configure the VNet01 DNS server settings to point to the Azure public DNS name servers.
- C
Deploy a private endpoint in the same region as the private DNS zone for resolution of internal.corp in VNet01.
- D
Add the private DNS zone name (internal.corp) as a custom DNS suffix in the network interface settings for all VMs in VNet01.
Show answer and explanation
Correct answer: A
Explanation
Linking a private DNS zone to a virtual network in Azure is done by creating a virtual network link from the private DNS zone to the desired VNet. This ensures that any resources in the VNet can resolve DNS queries for that private zone. Refer to Microsoft documentation on 'Azure Private DNS' for more details on configuring a virtual network link and enabling auto-registration.
- A. Correct.
Option 1 is correct. To enable DNS resolution for the private zone in VNet01, you must create a virtual network link within the private DNS zone settings and associate it with VNet01. The 'Enable auto-registration' option allows for automatic registration of new virtual machines� DNS records in that zone.
- B. Incorrect.
Option 2 is incorrect. Pointing the VNet directly to Azure public DNS name servers will not enable resolving private DNS names in the private DNS zone. Public DNS servers only resolve publicly accessible domains, not private DNS zones.
- C. Incorrect.
Option 3 is incorrect. A private endpoint allows secure connectivity to Azure PaaS services over private IP addresses but does not provide DNS name resolution for a general private zone in the VNet. It� used specifically for connecting to certain Azure services privately.
- D. Incorrect.
Option 4 is incorrect. Simply adding a custom DNS suffix in each VM� network interface will not automatically resolve the private DNS zone records. VMs still need to use Azure� internal DNS service or a custom DNS server that is aware of the private DNS zone.