Question
Hotspot Question You have an Azure subscription. The subscription contains virtual machines that run Windows Server 2016 and are configured as shown in the following table. You create a public Azure DNS zone named adatum.com and a private Azure DNS zone named contoso.com. You create a virtual network link for contoso.com as shown in the following exhibit. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Answer:
Exhibits
Answer Area
- When VM1 starts, a record for VM1 is added to the contoso.com DNS zone.Yes
- When VM2 starts, a record for VM2 is added to the contoso.com DNS zone.Yes
- When VM3 starts, a record for VM3 is added to the adatum.com DNS zone.No
Explanation
The virtual network link for contoso.com has auto-registration enabled, which means any VM in the linked virtual network (VNet1) will automatically have DNS records created in the contoso.com private zone when they start. VM1 and VM2 are both in VNet1, so they get auto-registered into contoso.com. VM3 is in VNet2, which is not linked to contoso.com, so it does not get auto-registered there. The public DNS zone adatum.com does not support auto-registration - records in public DNS zones must be created manually, so VM3's startup does not trigger any record creation in adatum.com.
Topics
#Azure DNS#Private DNS Zones#Auto-registration#Virtual Network Links
Community Discussion
No community discussion yet for this question.