Question
Your on-premises network contains an Active Directory Domain Services (AD DS) domain named fabrikam.com. The domain contains a domain controller named DC1. DC1 has the DNS Server role installed and hosts the DNS primary zone for fabrikam.com.
You have an Azure subscription that contains a virtual network named VNet1. VNet1 contains a virtual machine named VM1.
The on-premises network is connected to Azure by using a Site-to-Site (S2S) VPN.
From the Azure Command-Line interface (CLI), you run the following commands.
New-AzPrivateDnsZone -Name azure.fabrikam.com -ResourceGroupName RG1
New-AzPrivateDnsVirtualNetworkLink -ZoneName "azure.fabrikam.com" -ResourceGroupName "RG1" -Name "DNSlink" -VirtualNetworkId $VNET1.id
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Explanation
Statement 1 (No): azure.fabrikam.com is an Azure private DNS zone. Private zones are resolvable only from linked virtual networks and have no publicly reachable name servers that a delegation could point to, so adding a delegation to the on-premises fabrikam.com zone does not let on-premises hosts resolve its records.
Statement 2 (Yes): A conditional forwarder for azure.fabrikam.com on DC1 sends those queries over the Site-to-Site VPN to a DNS server or Azure DNS Private Resolver inbound endpoint in VNet1, which answers from the linked private zone. This lets on-premises hosts resolve the records.
Statement 3 (No): The virtual network link was created without the -EnableRegistration switch, so it is a resolution-only link. VM records are registered automatically only when registration is enabled on the virtual network link.
