AZ-104 - Configure and Manage Virtual Networking (19% of the exam) - Section 4.3
Configure name resolution and load balancing using Azure DNS, Azure Load Balancer, and Application Gateway.
Use Azure DNS public zones for internet name resolution and private DNS zones inside virtual networks, then distinguish Azure Load Balancer (Layer 4, TCP/UDP), Application Gateway (Layer 7, HTTP/HTTPS with path-based routing), and Traffic Manager (DNS-based global routing). Choose the service by whether routing happens at the network layer, the application layer, or across regions.
Azure DNSprivate DNS zonesAzure Load BalancerApplication GatewayTraffic Manager
Practice question for this objective
lock_openFree sampleConfigure and Manage Virtual Networkingmedium
An architect wants to distribute traffic for a public-facing application across several global Azure regions using a DNS-based load balancing approach. Which Azure DNS service is designed for this scenario?
AAzure Private DNS distributes traffic across the global Azure regions
BAzure Public DNS distributes traffic across the global Azure regions
CAzure DNS Private Resolver distributes traffic across the global Azure regions
DAzure Traffic Manager distributes traffic across the global Azure regionscheck_circle Correct
Traffic Manager is the DNS-based global traffic load balancer among the Azure DNS services. Azure Traffic Manager is a DNS-based traffic load balancer that distributes traffic to your public facing applications across the global Azure regions.
Why A is wrong: Azure Private DNS resolves names within virtual networks; it is not a DNS-based global traffic load balancer.
Why B is wrong: Azure Public DNS hosts DNS domains for record management; it does not perform DNS-based traffic load balancing across regions.
Why C is wrong: The Private Resolver enables querying private zones across on-premises and Azure; it does not load balance public application traffic.
Why D is correct: Correct. Azure Traffic Manager is a DNS-based traffic load balancer that distributes traffic to your public facing applications across the global Azure regions.
Exam traps in Configure and Manage Virtual Networking
Answers that look right on this material and are not. Each one is a distractor from a different question in the AZ-104 bank for this domain.
A public load balancer with a private IP frontend configuration
errorWhy it is wrong: Selecting a private IP frontend creates an internal load balancer, not a public one; the pairing described is inconsistent.
Yes
errorWhy it is wrong: Answering Yes would overlook the documented global peering constraint, since resources in one network cannot reach the front-end IP of a basic load balancer in a globally peered network.
The spoke virtual network must deploy its own VPN gateway
errorWhy it is wrong: A virtual network using a remote gateway for transit cannot also have its own gateway, since a virtual network can have only one gateway.