A global retail company is deploying a new e-commerce platform that must be highly available and resilient to regional outages. The platform needs to serve customers worldwide with minimum latency. Data consistency is eventually consistent across regions. Which Azure networking and application architecture approach should be recommended?
- ASingle Azure region deployment with Availability Zones and Azure Application Gateway
- BSingle Azure region deployment with Virtual Machine Scale Sets and Azure Firewall
- CMulti-region deployment using Azure Front Door, Azure Traffic Manager, and Cosmos DB with multi-region writes
- DMulti-region deployment using Azure Load Balancer, VPN Gateway, and Azure SQL Database Geo-replication
Show answer & explanationAnswer & explanation
Correct answer: C. Multi-region deployment using Azure Front Door, Azure Traffic Manager, and Cosmos DB with multi-region writes
Azure Front Door provides global load balancing and web application firewall capabilities, routing traffic to the nearest healthy backend with low latency. Azure Traffic Manager can also distribute traffic globally. Cosmos DB with multi-region writes provides global distribution with eventual consistency, which aligns with the global retail scenario for an e-commerce platform.
Why the other options are wrong
- A. A single region, even with Availability Zones, is not resilient to regional outages. Application Gateway is regional.
- B. A single region deployment is not resilient to regional outages. Azure Firewall is for network security, not global distribution.
- D. Azure Load Balancer is regional, and VPN Gateway is for site-to-site connectivity. SQL Database Geo-replication is for read replicas, not multi-region writes with eventual consistency.
Global Distribution Architecture
Designing applications to be deployed and accessible across multiple Azure regions to achieve high availability, disaster recovery, and low latency for global users.
- Global load balancers (Front Door, Traffic Manager)
- Multi-region data replication (Cosmos DB multi-region writes)
- Regional redundancy (Availability Zones, paired regions)
Memory trick: Front Door opens globally, Traffic Manager guides, Cosmos DB spreads data.