AZ-104 Question 232
Single answerYour company hosts a custom internal web application on a set of Azure virtual machines within the same virtual network. Employees access this application via a site-to-site VPN from the on-premises environment, and they need a single domain name that resolves internally for both Azure-based and on-premises clients. Additionally, traffic should be balanced across all VMs. Which solution should you implement to meet these requirements?
- A
Use an internal Azure Load Balancer and integrate a Private DNS zone linked to the virtual network, then configure your on-premises DNS to forward queries for that private zone.
- B
Use a public Azure Load Balancer with a publicly routable IP address and create an A record for the domain in a public DNS zone.
- C
Use Azure Traffic Manager with Priority routing, and rely on the default trafficmanager.net domain for name resolution.
- D
Use Azure Front Door with a custom subdomain and point on-premises DNS to the provided edge endpoints.
Show answer and explanation
Correct answer: A
Explanation
To meet the scenario requirements, you need an internal load balancing solution coupled with private DNS for name resolution that is accessible over the site-to-site VPN. Option 1 achieves this by distributing traffic internally while ensuring consistent name resolution across both Azure and on-premises environments.
- A. Correct.
An internal Load Balancer combined with Azure Private DNS ensures internal-only name resolution, and on-premises DNS can be configured to forward queries. This meets the requirement for internal access over VPN and distributes traffic across VMs.
- B. Incorrect.
A public Azure Load Balancer would expose the application externally, which is not required for an internal application accessed over a VPN.
- C. Incorrect.
Traffic Manager primarily manages traffic across different endpoints or regions, and it uses a public-facing DNS domain. This is not suitable for a purely internal solution requiring private name resolution.
- D. Incorrect.
Azure Front Door is also a global, public endpoint solution intended primarily for public-facing applications. It is unnecessary for an internal-only application.