Question

Difficulty: HardDesign Traffic Routing and Failover Strategies

An enterprise is designing a global disaster recovery and traffic routing solution for a hybrid system deployed across the Azure East US region and an on-premises datacenter in Paris. The system contains the following workloads:

* Workload 1: A legacy inventory database application that communicates over TCP port 84438443. This workload requires global failover based on client proximity, but does not support HTTP protocols.
* Workload 2: A public-facing e-commerce web application (HTTPS) that requires SSL termination at the edge, URL path-based routing to different backend pools, and web application firewall (WAF) protection.

You need to design a routing and failover strategy that minimizes latency and meets all technical requirements. Which two actions should you include in the design?

  1. Deploy Azure Front Door to route traffic for Workload 2.Answer
  2. Deploy Azure Traffic Manager to route traffic for Workload 1.Answer
  3. C
    Deploy Azure Front Door to route traffic for both Workload 1 and Workload 2.
  4. D
    Deploy Azure Traffic Manager to route traffic for both Workload 1 and Workload 2.
  5. E
    Deploy an Azure Cross-region Load Balancer to route traffic for Workload 2.

Answer

Deploy Azure Front Door to route traffic for Workload 2, and deploy Azure Traffic Manager to route traffic for Workload 1.
Deploying Azure Front Door for the e-commerce workload (Workload 2) meets the Layer 7 requirements (SSL termination, path-based routing, and WAF protection) using Anycast. Deploying Azure Traffic Manager for the database workload (Workload 1) allows routing of non-HTTP TCP traffic on port 8443 using DNS routing.

Step-by-Step Solution

1
Analyze Workload 1 requirements.
Workload 1 uses a raw TCP protocol on port 84438443 and requires global proximity-based routing and failover.
Since Workload 1 is non-HTTP, any Layer 7 routing service (like Azure Front Door) is ruled out. A DNS-based routing solution like Azure Traffic Manager is required because it operates at the DNS layer and can route any protocol/port.
2
Analyze Workload 2 requirements.
Workload 2 requires SSL termination, WAF protection, and path-based routing for an HTTPS endpoint.
These are Layer 7 features. Azure Front Door is a global Layer 7 load balancer that utilizes Anycast DNS/routing to minimize latency, terminate SSL at the edge, apply WAF rules, and route traffic based on URL paths.
3
Compare and select the matching Azure services.
Azure Traffic Manager is selected for Workload 1, and Azure Front Door is selected for Workload 2.
This combination successfully meets all routing, protocol, security, and failover requirements while keeping latency minimal.

Key Concept

Selecting global traffic routing solutions based on protocol support (Layer 4/DNS vs. Layer 7 Anycast) and feature requirements (SSL offloading, WAF, and path-based routing).
Rate this question