Question

Difficulty: EasyDesign Traffic Routing and Failover Strategies

An organization is designing a hybrid traffic routing and failover strategy for two distinct global workloads:
1. A global web application running on HTTP that requires SSL offloading and URL path-based routing.
2. A legacy TCP-based service that requires global DNS-based failover.

Which of the following Azure services should you include in the design to meet these requirements? (Select TWO.)

  1. Azure Front Door to provide Anycast-based routing, SSL offloading, and URL path-based routing for the web applicationAnswer
  2. Azure Traffic Manager to provide DNS-based routing and failover for the legacy TCP serviceAnswer
  3. C
    Azure Traffic Manager to perform SSL offloading and URL path-based routing for the web application
  4. D
    Azure Application Gateway to provide global DNS-based failover for the legacy TCP service

Answer

The correct services are Azure Front Door for the HTTP web application and Azure Traffic Manager for the legacy TCP service.
The design requires two different routing mechanisms. The global HTTP application needs layer 7 intelligence, which is provided by Azure Front Door using Anycast routing, path-based rules, and edge SSL termination. The legacy TCP service does not use HTTP, so it requires a protocol-agnostic DNS routing mechanism, which is provided by Azure Traffic Manager.

Step-by-Step Solution

1
Analyze the requirements for the global HTTP application, which include SSL offloading and URL path-based routing.
Azure Front Door is selected because it is a global, Anycast-based layer 7 load balancer capable of terminating SSL and routing based on URL paths.
Only layer 7 load balancers with global reach can satisfy HTTP-specific routing rules and SSL offloading at the network edge.
2
Analyze the requirements for the legacy TCP-based service, which require global DNS-based failover.
Azure Traffic Manager is selected because it operates at the DNS level and can distribute non-HTTP TCP traffic globally.
Since the legacy service is non-HTTP TCP, HTTP-specific load balancers cannot handle the traffic, making DNS-based global routing the appropriate choice.

Key Concept

Contrasting global Anycast-based layer 7 routing (Azure Front Door) with global DNS-based routing (Azure Traffic Manager) depending on workload protocol and capability requirements.
Rate this question