An organization is designing a high-availability and disaster recovery architecture for various workloads deployed in Azure. You need to select the appropriate load balancing and traffic routing services. Match each application routing requirement with the optimal Azure service.
- Route global HTTPS traffic to web applications across multiple regions with path-based routing, SSL offload, and fast Anycast failover.Azure Front Door
- Load balance non-HTTP TCP traffic globally across multiple Azure regions with low latency using Anycast IP address advertising.Azure Cross-region Load Balancer
- Distribute HTTP(S) traffic within a single Azure region using URL path-based rules and cookie-based affinity.Azure Application Gateway
- Load balance global TCP/UDP endpoints using DNS-based name resolution with weighted or priority-based routing policies.Azure Traffic Manager
Answer
Route global HTTPS traffic with path-based routing matches Azure Front Door; Load balance global TCP traffic using Anycast matches Azure Cross-region Load Balancer; Distribute regional HTTP(S) traffic with path-based rules matches Azure Application Gateway; Load balance global TCP/UDP endpoints using DNS matches Azure Traffic Manager.
The correct pairings are determined by matching the geographic scope (global vs. regional), the OSI layer (layer 4 TCP/UDP vs. layer 7 HTTP/S), and the routing mechanism (Anycast vs. DNS-based) of the requirements with the respective features of Azure Front Door, Azure Cross-region Load Balancer, Azure Application Gateway, and Azure Traffic Manager.
Step-by-Step Solution
Key Concept
Selecting the appropriate Azure load balancing and traffic routing services based on application protocol (HTTP/S vs. TCP/UDP), routing layer (Layer 4 vs. Layer 7), and geographic scope (Global vs. Regional).
Estimated Time:2m 0s