You have an Azure AD tenant named contoso.com and an Azure virtual network named VNET2
To VNET2, you deploy Azure AD DS (Azure Active Directory Domain Services) managed domain named liwareinc.com To VNET2, you decide to deploy a WVD host pool named Pool2
You need to ensure that you can deploy Windows 10 Enterprise host pools to Pool2
What would you do first?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: B
After Azure AD DS is successfully deployed, you should configure the VNET to allow other connected virtual machines and applications to utilize the managed domain.
To provide this connectivity, you should modify the DNS server settings for your VNET to point to the two IP addresses where the managed domain is deployed.
Option A is incorrect.
You don't need to change the settings for liwareinc.com DNS Zone.
Option B is correct.
Changing the DNS settings for VNET2 will enable you to deploy Windows 10 Enterprise host pools to Pool2.
Option C is incorrect.
You don't need to add the custom domain name to contoso.com.
Option D is incorrect.
Implementing Azure AD Connect cloud sync won't help in meeting the goal.
To know more about how to create and configure an Azure Active Directory Domain Services managed domain, please visit the below-given link:
To deploy Windows 10 Enterprise host pools to the WVD host pool named Pool2 in an Azure virtual network named VNET2 with Azure AD DS managed domain named liwareinc.com, the first step would be to join the VMs in the host pool to the domain.
To join the VMs to the domain, the VMs must be able to resolve the domain name of the managed domain liwareinc.com. This can be achieved by adding DNS settings for the managed domain to the virtual network. Therefore, the correct answer is B. Change the DNS settings for VNET2.
By default, when you deploy Azure AD DS, it creates a DNS zone that matches the domain name of your managed domain (liwareinc.com in this case). This DNS zone is automatically populated with the necessary DNS records, including the SRV record that clients need to locate the domain controller(s) for the domain. So, option A is not relevant for this scenario.
Option C, adding a custom domain name to contoso.com, is not required for this scenario as it does not address the requirements of joining the VMs to the Azure AD DS managed domain.
Option D, implementing Azure AD Connect cloud sync, is not required for this scenario as it is used for synchronizing on-premises Active Directory with Azure AD, which is not required for joining VMs to an Azure AD DS managed domain.