Examkin

Question

Difficulty: HardDesign Traffic Routing and Failover Strategies

A logistics company is designing a global traffic routing and high-availability architecture for its hybrid fleet management platform deployed in the East US and North Europe regions.

The platform includes two distinct workloads:
1. A web application that requires edge-based SSL/TLS termination, URL path-based routing, and immediate session failover.
2. A high-throughput telemetry ingestion endpoint that communicates over a custom TCP port 88838883 (MQTT) and must route clients to the lowest-latency active datacenter.

Which global routing configuration should you recommend to meet these requirements with the lowest operational complexity?

  1. A
    Configure Azure Front Door to route traffic for both the web application and the telemetry ingestion service, utilizing custom domain routing and protocol translation.
  2. Configure Azure Front Door to route traffic for the web application, and configure Azure Traffic Manager using performance routing to resolve the endpoint for the telemetry ingestion service.Answer
  3. C
    Configure Azure Traffic Manager using priority routing for both the web application and the telemetry ingestion service, relying on DNS-level failover for both workloads.
  4. D
    Configure Azure Application Gateway with multi-site listeners in both regions to globally distribute traffic for both the web application and the telemetry ingestion service.

Answer

Configure Azure Front Door to route traffic for the web application, and configure Azure Traffic Manager using performance routing to resolve the endpoint for the telemetry ingestion service.
The correct option correctly pairs Azure Front Door with Azure Traffic Manager. Azure Front Door handles the HTTP/HTTPS web application, providing required Layer 77 capabilities like SSL/TLS termination at the edge and URL path-based routing. Azure Traffic Manager resolves the DNS queries for the custom TCP port 88838883 (MQTT) telemetry ingestion service, routing clients to the lowest-latency healthy regional endpoint. Since Traffic Manager works at the DNS level, it is protocol-agnostic and supports non-HTTP TCP traffic.

Step-by-Step Solution

1
Analyze the web application requirements.
The web application requires Layer 77 capabilities including SSL/TLS termination, URL path-based routing, and immediate failover.
Azure Front Door is a global Layer 77 Anycast-based load balancer designed for HTTP/HTTPS workloads, making it the correct choice for this workload.
2
Analyze the telemetry ingestion service requirements.
The telemetry service uses custom TCP port 88838883 (MQTT) and requires global routing to the lowest-latency active datacenter.
Azure Front Door only supports HTTP/HTTPS protocols and cannot ingest or route custom TCP port traffic.
3
Select the routing mechanism for the telemetry ingestion service.
Azure Traffic Manager resolves the endpoint DNS requests based on performance (latency).
Traffic Manager operates at the DNS level and is protocol-agnostic, allowing it to route clients on custom ports like port 88838883 to the closest healthy regional endpoint.

Key Concept

Selecting and combining global Azure load balancing services based on protocol support (Layer 77 HTTP/HTTPS vs. protocol-agnostic DNS routing).
Estimated Time:2m 30s
Rate this question

Topics

Design Traffic Routing and Failover Strategies

More questions from this topic