Examkin

Soru

Zorluk: ZorDesign Traffic Routing and Failover Strategies

Match each traffic routing and failover requirement with the most appropriate Azure load balancing or traffic routing service configuration. Each service configuration may be used once, more than once, or not at all.

  • A global web application requires SSL offloading at the network edge, URL-path-based routing, and instant failover between active-active regions using Anycast IPv4/IPv6 addresses.Deploy Azure Front Door configured with routing rules and global backend pools.
  • A business-critical database service requires global routing of SQL Server TCP traffic on port 1433, using Anycast IP addresses to onboard client traffic onto the Microsoft backbone at the nearest point of presence.Deploy an Azure Cross-Region Load Balancer frontend routing to regional Standard Load Balancers.
  • A legacy enterprise system running a proprietary TCP service on port 8080 requires global failover between an on-premises environment and an Azure region, utilizing DNS-based routing.Deploy Azure Traffic Manager with nested profiles and TCP health probes.
  • A web application hosted in a single Azure region requires internal load balancing across multiple Virtual Machine Scale Sets based on path rules, along with cookie-based session affinity.Deploy an Azure Application Gateway with path-based routing and cookie-based affinity enabled.

Cevap

Matching pairs: 1) Global web app with SSL offload/Anycast matches Azure Front Door; 2) SQL Server TCP 1433 over Anycast matches Azure Cross-Region Load Balancer; 3) Legacy TCP 8080 with DNS-based hybrid failover matches Azure Traffic Manager; 4) Single-region path-routing with cookie affinity matches Azure Application Gateway.
Each workload's requirement maps to the specific capabilities of Azure's load balancing services: Azure Front Door for global HTTP/HTTPS with Anycast and WAF; Azure Cross-Region Load Balancer for global TCP/UDP with Anycast; Azure Traffic Manager for DNS-based hybrid/custom TCP routing; and Azure Application Gateway for regional L7 routing with session affinity.

Adım Adım Çözüm

1
Analyze the network protocols and regional scopes of each scenario.
Identify that two scenarios require global Layer 7 routing (HTTP/HTTPS), one requires global Layer 4 routing (TCP 1433), one requires custom TCP on port 8080 across hybrid environments, and one requires regional Layer 7 routing.
This categorizes the candidate Azure routing services into L4 vs L7, and regional vs global.
2
Differentiate between global Layer 7 options based on performance and protocol constraints.
Map the global HTTPS scenario with WAF and SSL offloading to Azure Front Door, and the regional HTTPS scenario with session affinity to Azure Application Gateway.
Azure Front Door provides global Anycast-based routing, while Azure Application Gateway provides regional-only load balancing features.
3
Differentiate between global Layer 4 options and hybrid/custom port options.
Map the SQL Server TCP port 1433 Anycast requirement to Azure Cross-Region Load Balancer, and the legacy hybrid TCP port 8080 DNS-based requirement to Azure Traffic Manager.
Cross-Region Load Balancer provides Layer 4 Anycast routing, whereas Traffic Manager operates via DNS and supports external/on-premises endpoints for any custom port.

Anahtar Kavram

Design Traffic Routing and Failover Strategies
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru