What should you do first?

You have an Azure Active Directory (Azure AD) tenant named contoso.com and an Azure virtual network named VNET1.

To VNET1, you deploy an Azure Active Directory Domain Services (Azure AD DS) managed domain named litwareinc.com.

To VNET1, you plan to deploy a Windows Virtual Desktop host pool named Pool1. You need to ensure that you can deploy Windows 10 Enterprise host pools to Pool1.

What should you do first?

A. Modify the settings of the litwareinc.com DNS zone.

B. Modify the DNS settings of VNET1.

C. Add a custom domain name to contoso.com.

D. Implement Azure AD Connect cloud sync.

View Answer

Answer: B

Explanation:

To deploy a Windows Virtual Desktop (WVD) host pool and ensure that you can deploy Windows 10 Enterprise multi-session hosts, you need to have proper domain services and networking in place. Given the deployment of Azure Active Directory Domain Services (Azure AD DS) managed domain and the need for the virtual machines in the host pool to join this domain, the virtual network settings must allow these VMs to locate and join the managed domain.

Here are the steps you would typically take:

A. Modify the settings of the litwareinc.com DNS zone: While Azure AD DS creates its own DNS zone, you generally do not need to modify this for the VMs to join the domain, as it is managed by Azure.

B. Modify the DNS settings of VNET1: This is a critical step. The DNS settings of the virtual network must be configured to point to the Azure AD DS managed domain DNS, which allows the VMs in the host pool to resolve the domain and domain services necessary for domain join operations.

C. Add a custom domain name to contoso.com: Adding a custom domain name to the Azure AD tenant is often a preliminary step before setting up Azure AD DS, but since Azure AD DS is already deployed with the domain name litwareinc.com, this step is not immediately necessary for deploying the WVD host pool.

D. Implement Azure AD Connect cloud sync: Azure AD Connect sync is used to synchronize on-premises AD with Azure AD and is not directly related to the deployment of a WVD host pool. Since you’re using Azure AD DS, which provides a managed domain without the need for synchronization from an on-premises environment, this is not the first step needed for deploying Windows 10 Enterprise host pools.

Based on the given scenario, the first step you should take is:

B. Modify the DNS settings of VNET1: You should point the DNS settings of VNET1 to the Azure AD DS managed domain DNS servers. This configuration allows the VMs within the host pool to resolve and join the managed domain, which is necessary for deploying Windows 10 Enterprise VMs into the WVD host pool named Pool1.