AZ-700 Question 209
Single answerYou manage a global e-commerce platform with two Azure App Service instances: one in East US and another in West Europe. You plan to deploy Azure Front Door to provide high availability and direct users to the nearest region to meet data-residency and performance requirements. Specifically, U.S. users must remain in East US unless that region is offline, and European users must remain in West Europe unless that region is offline. Which Azure Front Door configuration best meets these requirements?
- A
Use a single backend pool with both endpoints and set a Weighted routing method split equally (50/50).
- B
Use a single backend pool with first endpoint Priority = 1 (East US) and second endpoint Priority = 2 (West Europe).
- C
Use two backend pools, each with a single endpoint (East US, West Europe), and configure geo-filtering rules plus Priority routing to fail over if a region becomes unavailable.
- D
Use a single backend pool, enable Session Affinity, and rely on health probes for regional failover.
Show answer and explanation
Correct answer: C
Explanation
To meet regional compliance and availability needs, you can create separate backend pools for each region and configure geo-filtering rules to send geographically appropriate traffic to localized endpoints. Priority routing in each pool ensures automatic failover if a region becomes unavailable. For further reference, consult the official Azure Front Door documentation: https://learn.microsoft.com/azure/frontdoor/
- A. Incorrect.
Incorrect. Weighted routing (50/50) would send half of the traffic from the U.S. to Europe and vice versa, violating the data-residency requirement and not ensuring U.S. users remain in East US by default.
- B. Incorrect.
Incorrect. Priority routing in a single pool can direct all initial traffic to East US, but it does not inherently separate or 'pin' European users to West Europe unless the primary fails. This approach doesn't meet the data-residency requirement for Europe under normal conditions.
- C. Correct.
Correct. Creating separate backend pools (one for East US and one for West Europe) and combining geo-filtering rules with Priority routing satisfies the requirement to keep traffic geographically local and allows for failover if one region goes offline.
- D. Incorrect.
Incorrect. While session affinity ensures a user remains on the same endpoint, it does not inherently route based on a user's geographic location or ensure compliance with data-residency requirements.