Examkin

Question

Difficulty: MediumDesign Traffic Routing and Failover Strategies

A financial services company hosts a critical web API across two Azure regions: East US and West Europe. The API requires SSL offloading, URL path-based routing to direct requests (such as routing /payments to a dedicated backend pool), and a global failover mechanism that achieves a recovery time objective (RTO) of less than one minute. Which traffic routing solution should you recommend?

  1. Deploy Azure Front Door to route global traffic, configure path-based routing rules, and perform SSL offloading.Answer
  2. B
    Deploy Azure Traffic Manager to manage global traffic routing, and configure path-based routing and SSL offloading directly on the Traffic Manager profile.
  3. C
    Deploy Azure Application Gateway in a multi-region configuration to route traffic globally, configure path-based routing rules, and perform SSL offloading.
  4. D
    Deploy Azure Traffic Manager to route traffic globally, and deploy Azure Load Balancer in each region to perform path-based routing and SSL offloading.

Answer

Deploy Azure Front Door to route global traffic, configure path-based routing rules, and perform SSL offloading.
The correct option is the one proposing Azure Front Door. Azure Front Door is an Anycast-enabled global Layer 7 load balancer. It natively supports SSL/TLS termination, URL path-based routing, and rapid backend health monitoring that enables failover in less than a minute.

Step-by-Step Solution

1
Analyze the layer routing requirements.
The requirements specify SSL offloading and URL path-based routing (e.g., /payments), which are Layer 7 (application layer) features.
This rules out Layer 4 load balancing solutions and DNS-only solutions at the entry point unless chained, though a unified global solution is preferred.
2
Evaluate the global failover and RTO requirements.
The RTO must be less than one minute. DNS-based solutions like Traffic Manager rely on client DNS caching and TTL, which can delay failover times beyond one minute for many clients.
Anycast-based routing (used by Azure Front Door) bypasses DNS propagation delays for failover, offering split-second failover times.
3
Select the service that meets all criteria natively.
Azure Front Door natively combines global Anycast routing, Layer 7 path-based routing, SSL offloading, and rapid failover via sub-minute health probes.
It fulfills the complete requirement set without introducing regional limits or DNS TTL caching issues.

Key Concept

Azure Front Door is a global, Anycast-based Layer 7 load balancer that supports SSL offloading, path-based routing, and sub-minute global failover, whereas Azure Traffic Manager is a DNS-level load balancer subject to DNS TTL caching.
Estimated Time:1m 30s
Rate this question

Topics

Design Traffic Routing and Failover Strategies

More questions from this topic