Question
Your network contains an on-premises Active Directory domain that syncs to a Microsoft Entra tenant. The domain contains the domain controllers shown in the following table.
| Name | Network location | IP address | Configuration |
|---|---|---|---|
| Server1 | On-premises datacenter | 10.10.1.1 | Domain controller, DNS server |
| Server2 | Azure virtual network named VNET1 | 10.20.1.1 | Domain controller, DNS server |
The DNS servers are configured to forward requests to an external DNS service.
You create a new virtual network named VNET2 that is peered to VNET1 and has gateway transit enabled.
You plan to implement an Azure Virtual Desktop host pool in VNET2. The session hosts will be joined to the Active Directory domain.
You need to configure DNS to meet the following requirements:
- Ensure that Azure Virtual Desktop users can resolve on-premises servers and Azure resources.
- Ensure that Azure Virtual Desktop remains operational if a DNS server fails.
- Minimize administrative effort.
What should you configure?
- A. the DNS settings of VNET2 to use Server2 and Server1 Correct
- B. the DNS settings of VNET2 to use the Azure DNS service
- C. the DNS settings of the virtual machines to use Server2 and Server1
- D. the DNS settings of the virtual machines to use the Azure DNS service
Explanation
Domain-joined session hosts must use the AD DS DNS servers to locate domain controllers and resolve on-premises names, and those servers forward other queries externally. Setting custom DNS servers on VNET2 applies them to every session host automatically through DHCP, and listing both Server2 and Server1 keeps resolution working if one fails. Setting DNS on each virtual machine works but adds administrative effort, and Azure-provided DNS cannot resolve the on-premises Active Directory zone, so domain join would fail.
