Microsoft Certified: Azure Administrator AssociateMonitor and maintain Azure resourcesMedium
A global company uses Azure Front Door to manage traffic to their web applications hosted in multiple Azure regions. They need to ensure that if one of their primary application regions becomes unavailable, traffic is automatically routed to a healthy secondary region without manual intervention. Which Azure Front Door routing method should they configure?
- AWeighted
- BLatency
- CPriority
- DSession Affinity
Show answer & explanationAnswer & explanation
Correct answer: C. Priority
The Priority routing method in Azure Front Door allows you to assign priorities to backend pools. If the highest priority backend pool becomes unhealthy, traffic automatically fails over to the next available priority pool.
Why the other options are wrong
- A. Weighted routing distributes traffic based on specified weights among healthy backends, suitable for load balancing, not primary/secondary failover.
- B. Latency routing directs traffic to the backend with the lowest latency from the client, optimizing performance but not guaranteeing failover to a specific secondary in a disaster.
- D. Session Affinity ensures that requests from the same client are always sent to the same backend, which is a session management feature, not a failover mechanism.
Azure Front Door Priority Routing
An Azure Front Door routing method that directs all traffic to the primary (highest priority) healthy backend pool. If the primary becomes unhealthy, traffic automatically fails over to the next highest priority healthy backend pool.
- Ideal for active/passive or active/standby disaster recovery scenarios.
- Provides automatic failover based on backend health probes.
- Priorities are assigned to backend pools.
Memory trick: Front Door routes, priorities decide, latency's quick, weights divide.