Hotspot Question You plan to deploy a custom database solution that will have multiple instances as shown in the following table. Client applications will access database servers by using…

Question

Exhibits

Answer Area

• Global load balancing service:
  Azure Application GatewayAzure Front DoorAzure Load BalancerAzure Traffic Manager
• Availability Zone load balancing service:
  Azure Application GatewayAzure Front DoorAzure Load BalancerAzure Traffic Manager

Explanation

This hotspot question tests knowledge of Azure load balancing services for a multi-region database deployment that must survive regional outages without exposing VMs directly to the internet.

Approach. For global load balancing across regions using a DNS name (db.contoso.com) with failover capability during regional outages, Azure Traffic Manager is the correct choice - it is a DNS-based global traffic routing service that distributes traffic across regions and maintains availability during regional failures. For load balancing within each region among the database VMs without exposing them to the internet, an Internal (Private) Azure Load Balancer (Standard tier, internal) is appropriate, as it operates at Layer 4 within a VNet without a public IP, ensuring VMs do not connect to or receive traffic from the internet directly. Traffic Manager handles the global DNS resolution to the correct regional endpoint, while the internal load balancer distributes traffic among VM instances within each region.

Concept tested. Azure load balancing architecture: using Azure Traffic Manager for global DNS-based failover across regions, and Azure Internal Load Balancer for intra-region distribution without internet exposure - distinguishing between global vs. regional and public vs. internal load balancing options.

Reference. https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/load-balancing-overview

No community discussion yet for this question.