AZ-700 Question 27
Select 2You are designing name resolution for a new multi-tier application hosted entirely within a single Azure Virtual Network (VNet). Each tier resides in its own subnet, and new virtual machines (VMs) are frequently deployed or removed. On-premises users must also be able to resolve the private hostnames of the Azure VMs without manual DNS entries. Which two approaches should you use to satisfy these requirements?
- A
Configure an Azure Private DNS zone for your custom domain, link it to the VNet, and enable automatic DNS registration for your VMs.
- B
Rely on the Azure-provided default DNS (168.63.129.16) strictly for all internal name resolution needs.
- C
Create a conditional forwarder in your on-premises DNS server to forward queries for the Azure private domain to Azure� Private DNS zone.
- D
Point each Azure VM� primary DNS setting to your on-premises DNS server for all name resolution requests.
- E
Deploy domain controllers in the Azure VNet specifically for DNS replication with on-premises Active Directory.
Show answer and explanation
Correct answers: A, C
Explanation
Using Azure Private DNS zones (Option 1) allows automatic registration of private hostnames, eliminating the need to manually create DNS records. Pairing it with a conditional forwarder in on-premises DNS servers (Option 3) ensures that on-premises clients can also resolve those private hostnames in Azure with minimal administrative overhead. For more details on Azure Private DNS best practices, refer to Microsoft's documentation at https://learn.microsoft.com/azure/dns/private-dns-overview.
- A. Correct.
Option 1 is correct. Azure Private DNS zones allow VMs in the same VNet to have their host records automatically registered, simplifying management. Linking the zone to the VNet ensures that newly added VMs automatically receive name resolution without requiring manual updates.
- B. Incorrect.
Option 2 is incorrect. While the Azure-provided default DNS can resolve names for VMs in the same VNet, it does not support the dynamic DNS registration or custom domain requirements. It is limited in terms of custom domain name resolution and does not extend easily to on-premises queries.
- C. Correct.
Option 3 is correct. Creating a conditional forwarder in on-premises DNS to forward queries for the Azure private domain to the Private DNS zone ensures that on-premises clients can look up Azure VM hostnames without manual records in the on-prem DNS server.
- D. Incorrect.
Option 4 is incorrect. Pointing each Azure VM to the on-prem DNS server as primary can introduce network latency and complexity. It also requires additional configuration for forwarding requests back to Azure for local name resolution. It is less robust compared to integrating a Private DNS zone in Azure.
- E. Incorrect.
Option 5 is incorrect. While deploying on-premises-style domain controllers in Azure can be a valid approach for certain hybrid scenarios, it is not necessary if your main objectives are dynamic registration and easy on-prem resolution. Azure Private DNS zones are typically more straightforward to set up and manage than replicating entire AD DNS infrastructure in Azure.