Hotspot Question You have an Azure subscription named Subscription1. Subscription1 contains the resources in the following table. In Azure, you create a private DNS zone named adatum.com. You set…

Question

Exhibit

Answer Area

• The A record for VM5 will be registered automatically in the adatum.com.zone.No
• VM5 can resolve VM9.adatum.com.No
• VM6 can resolve VM9.adatum.com.Yes

Explanation

VMs can only auto-register and resolve records in a Private DNS Zone if their Virtual Network is appropriately linked as a registration or resolution network.

Approach. This question relies on a standard scenario table where VM5 is in VNet1, VM6 is in VNet2, and VM9 is in VNet3. 1) The 'registration virtual network' is set to VNet2. Therefore, only VMs within VNet2 (VM6) will automatically register their A records. VM5 is in VNet1 and will not auto-register, making the first statement 'No'. 2) VM5 cannot resolve 'VM9.adatum.com' because VNet1 is not linked to the private DNS zone at all (neither for registration nor resolution), making the second statement 'No'. 3) VM6 can resolve 'VM9.adatum.com' because its network (VNet2) is linked to the zone. Registration networks inherently include DNS resolution capabilities, and the scenario's zone exhibit typically contains a manually added A record for VM9, making the third statement 'Yes'.

Common mistakes.

• common_mistake. A frequent misconception is that merely creating a Private DNS zone within a subscription allows all VMs in that subscription to use it. In Azure, you must explicitly create Virtual Network Links (designated for either 'resolution' or 'registration') for each VNet that needs to query or update the zone.

Concept tested. Azure Private DNS Zones, Virtual Network Links, Auto-registration vs. Resolution

Reference. https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links

No community discussion yet for this question.