Match each application architecture scenario to the most appropriate Azure load balancing or traffic routing service. Each service may be used once, more than once, or not at all.
- A global web application that requires SSL offloading, URL path-based routing, and immediate failover using Anycast routing.Azure Front Door
- A global application using custom TCP ports that requires DNS-based routing to endpoints with configurable TTL for failover.Azure Traffic Manager
- A web application restricted to a single region that requires URL-path routing, private backend IP addresses, and Web Application Firewall (WAF) protection.Azure Application Gateway
- A regional database cluster requiring high-throughput, ultra-low latency TCP load balancing for backend virtual machines.Azure Load Balancer
Cevap
The global web application with SSL offloading and Anycast routing matches Azure Front Door. The global TCP application using DNS routing matches Azure Traffic Manager. The regional web application with private backend IPs and WAF matches Azure Application Gateway. The regional database cluster matches Azure Load Balancer.
The correct matches are based on mapping the architectural scope (global vs. regional) and the required networking layer (Layer 4 vs. Layer 7). Global Layer 7 routing with Anycast maps to Azure Front Door. Global DNS-based Layer 4 routing maps to Azure Traffic Manager. Regional Layer 7 routing with private IP backends and WAF maps to Azure Application Gateway. Regional Layer 4 high-performance TCP load balancing maps to Azure Load Balancer.
Adım Adım Çözüm
Anahtar Kavram
Selecting Azure load balancing services based on geographical scope (global vs. regional) and protocol layer (Layer 4 vs. Layer 7).