A collaborative document editing platform has a global user base and is deployed across virtual machines in the East US and West US regions. You are designing an application delivery and load balancing solution for the platform. The solution must meet the following requirements:
- Route users to the region that offers the lowest latency.
- Implement path-based routing within each region, directing requests for `/edit/*` and `/view/*` to separate backend pools.
- Support SSL/TLS termination at the regional entry point.
- Align with availability zone designs and use Standard SKU resources.
Which two of the following Azure resources should you include in the architectural design to meet these requirements?
- Azure Front Door configured with latency-based routingAnswer
- Azure Application Gateway (Standard v2) in each regionAnswer
- CAzure Traffic Manager profile configured with performance routing
- DAzure Load Balancer (Basic SKU) in each region
Answer
Azure Front Door and Azure Application Gateway (Standard v2) in each region
Azure Front Door is selected to provide global latency-based routing for the web application, directing global users to the closest region. Inside each region, Azure Application Gateway (Standard v2) is deployed to handle the Layer 7 requirements, specifically path-based routing (for `/edit/*` and `/view/*`) and SSL/TLS termination, while satisfying the requirement for Standard SKU alignment and availability zones.
Step-by-Step Solution
Key Concept
Combining global latency-based routing with regional path-based application load balancing using Standard SKU resources.
Estimated Time:1m 30s