Hotspot Question You have an Azure virtual machine that runs Windows Server 2019 and has the following configurations: Name: VM1 Location: West US Connected to: VNET1 Private IP address: 10.1.0.4…

Question

Exhibits

Answer Area

• Adatum.pri can be linked to VNET1Yes
• VM1 can automatically register to Adatum.priNo
• Contoso.pri can be linked to VNET1Yes
• VM1 can automatically register to Contoso.priNo
• Adatum.com can be linked to VNET1No
• VM1 can automatically register to Adatum.comNo
• Contoso.com can be linked to VNET1No
• VM1 can automatically register to Contoso.comNo

Explanation

The correct selections are 'The private zones only' for both linking to VNET1 and automatic VM registration, as these features are exclusive to Azure Private DNS zones.

Approach. 1. Analyze the VM and VNET context: VM1 is in 'West US' and connected to 'VNET1'. Its DNS suffix is 'Adatum.com'. 2. Evaluate 'DNS zones that you can link to VNET1': * Azure Public DNS zones (Adatum.com, Contoso.com) cannot be directly linked to an Azure Virtual Network (VNET). They are for public resolution via global DNS servers. * Azure Private DNS zones (Adatum.pri, Contoso.pri) are designed to be linked to VNETs. This allows resources within the linked VNET to resolve names within that private zone using Azure's default DNS resolvers. Private DNS zones can be linked to VNETs across different Azure regions. * Therefore, only private DNS zones can be linked to VNET1. The option 'The private zones only' correctly encapsulates both Adatum.pri and Contoso.pri as eligible for linking. 3. Evaluate 'DNS zones to which VM1 can automatically register': * Automatic registration of Virtual Machine (VM) records (specifically, A records for their private IP addresses) into an Azure DNS zone is a feature exclusive to Azure Private DNS zones. Public DNS zones do not support this functionality. * For a VM to automatically register, the VNET it belongs to must be linked to the private DNS zone with automatic registration enabled. The VM's own DNS suffix (Adatum.com in this case) does not dictate which type of zone can support automatic registration. Regardless of the VM's configured suffix, Azure's automatic registration mechanism only works with private zones. When registered, the VM would typically create a record like hostname.privatezonename (e.g., VM1.Adatum.pri if linked to Adatum.pri). * Since only private DNS zones support automatic registration, 'The private zones only' is the correct choice, referring to the capability of Adatum.pri and Contoso.pri.

Common mistakes.

• common_mistake. Common mistakes include confusing the capabilities of Azure Public DNS zones with Azure Private DNS zones. Forgetting that Public DNS zones cannot be linked to VNETs or support automatic VM registration is a frequent error. Another mistake is overthinking the VM's Windows DNS suffix (Adatum.com) and incorrectly concluding that it must register into the Adatum.com public zone, or that private zones with different names are unsuitable. The core concept is that only Azure Private DNS zones offer VNET linking and automatic VM registration, irrespective of the zone's name or location relative to the VM, as long as VNET linking is possible.

Concept tested. The core concept tested is the fundamental difference between Azure Public DNS zones and Azure Private DNS zones, specifically their respective capabilities regarding Virtual Network (VNET) linking and automatic Virtual Machine (VM) registration. It assesses understanding that VNET linking and automatic VM registration are exclusive features of Azure Private DNS zones.

No community discussion yet for this question.