Examkin

Soru

Zorluk: KolayDesign Traffic Routing and Failover Strategies

Match each Azure traffic routing and load balancing service to its appropriate architecture requirement.

  • Global routing for HTTP(S) workloads with Anycast, SSL offloading, and web application firewall integration.Azure Front Door
  • Global DNS-based routing for non-HTTP or multi-protocol endpoints requiring path/port independent redirection.Azure Traffic Manager
  • Regional routing for HTTP(S) workloads supporting URL path-based routing and cookie-based affinity.Azure Application Gateway
  • Regional load balancing for non-HTTP TCP/UDP workloads requiring high-throughput and ultra-low latency.Azure Load Balancer

Cevap

Global routing for HTTP(S) workloads with Anycast matches Azure Front Door; Global DNS-based routing matches Azure Traffic Manager; Regional routing for HTTP(S) workloads matches Azure Application Gateway; Regional load balancing for non-HTTP TCP/UDP workloads matches Azure Load Balancer.
The correct matches align each load balancing service with its specific scope (global or regional) and network layer (Layer 4 or Layer 7). Azure Front Door and Azure Traffic Manager handle global traffic at Layer 7 and DNS level respectively. Azure Application Gateway and Azure Load Balancer distribute regional traffic at Layer 7 and Layer 4 respectively.

Adım Adım Çözüm

1
Identify the geographical scope for each requirement.
Requirements 1 and 2 are global; Requirements 3 and 4 are regional.
This narrows down choices between global load balancers (Azure Front Door, Azure Traffic Manager) and regional load balancers (Azure Application Gateway, Azure Load Balancer).
2
Identify the protocol layer (Layer 7 HTTP/S vs. Layer 4 TCP/UDP/DNS) for the global services.
Global HTTP(S) workloads needing SSL offloading match Azure Front Door; global DNS-based multi-protocol workloads match Azure Traffic Manager.
Azure Front Door is a Layer 7 Anycast service, whereas Azure Traffic Manager operates purely at the DNS level (Layer 4/DNS).
3
Identify the protocol layer for the regional services.
Regional HTTP(S) path-based routing matches Azure Application Gateway; regional TCP/UDP workloads match Azure Load Balancer.
Azure Application Gateway operates at Layer 7 (supporting URL-based routing), while Azure Load Balancer is a Layer 4 TCP/UDP distribution service.

Anahtar Kavram

Selecting Azure load balancing and traffic routing services based on protocol layer (Layer 4 vs. Layer 7) and geographic scope (global vs. regional).
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru