Examkin

Soru

Zorluk: Çok zorDesign Traffic Routing and Failover Strategies

An organization is designing a high-availability global infrastructure across the East US and West US regions for two key services:

* Service A: An HTTPS-based web portal requiring URL path-based routing (e.g., `/api/*` to an API cluster and `/static/*` to storage), SSL offloading, and client session stickiness.
* Service B: A proprietary database synchronization engine running on custom TCP port 14330 that requires low-latency routing to the nearest region, with a strict failover detection and client redirection time of under 10 seconds.

Which global traffic routing and failover strategy should you recommend to meet these requirements?

  1. Deploy Azure Front Door for Service A to handle SSL offloading and path-based routing. Deploy a cross-region Azure Load Balancer (Global tier) for Service B with a TCP health probe configured with a 5-second interval and 2 failures.Cevap
  2. B
    Deploy Azure Front Door for both Service A and Service B, configuring a standard HTTP/S routing rule for Service A and a custom TCP routing rule on port 14330 for Service B.
  3. C
    Deploy Azure Traffic Manager for both workloads, utilizing TCP-based health probes and setting the DNS Time-to-Live (TTL) to 5 seconds to ensure fast redirection and protocol compatibility.
  4. D
    Deploy Azure Front Door for Service A to handle SSL offloading and path-based routing. Deploy Azure Traffic Manager for Service B, configuring a TCP health probe with a 5-second interval and a 5-second DNS Time-to-Live (TTL).

Cevap

Deploy Azure Front Door for the HTTP/S portal and a cross-region Azure Load Balancer for the custom TCP service.
The correct strategy combines Azure Front Door for the Layer 7 HTTPS workload and a cross-region Azure Load Balancer (Global tier) for the custom TCP workload. Azure Front Door handles SSL offloading and path-based routing natively at the edge. The cross-region Load Balancer acts at Layer 4, supporting custom TCP port 14330, and provides deterministic failover under 10 seconds via Anycast routing, avoiding DNS caching issues that affect Traffic Manager.

Adım Adım Çözüm

1
Analyze protocol requirements for both services.
Service A requires HTTPS (Layer 7) features including path-based routing and SSL offloading. Service B requires custom TCP port 14330 (Layer 4).
This establishes the layer at which each routing solution must operate.
2
Evaluate global load balancing options for the HTTP/S workload.
Azure Front Door is selected for Service A because it is an Anycast-based global Layer 7 load balancer that handles SSL offloading, URL path-routing, and session affinity.
This directly satisfies all requirements of Service A.
3
Evaluate global load balancing and failover requirements for the custom TCP workload.
A cross-region Azure Load Balancer is selected for Service B because it operates at Layer 4, supports custom TCP ports, uses Anycast IP addresses, and provides near-instantaneous failover by bypassing DNS cache limitations. Traffic Manager cannot guarantee the sub-10 second failover requirement due to client-side DNS caching.
This satisfies the protocol and low-latency/fast-failover requirements of Service B.

Anahtar Kavram

Selecting the correct global load balancer based on Layer 4 vs. Layer 7 capabilities, protocol support, and failover latency constraints.
Bu soruyu puanla

Konular

Design Traffic Routing and Failover Strategies

Bu konudan daha fazla soru