What is multi-region, multi-AZ architecture and its benefits?

• A. Centralizing resources in one region to minimize costs.
• B. Deploying identical resources across regions and zones to improve resilience, reduce latency, and enable local failover.
• C. Spreading resources randomly to avoid predictability.
• D. Limiting resources to a single availability zone.

Answer: (B)

This approach means running identical resources in more than one geographic region and across multiple Availability Zones within each region. The idea is to avoid a single point of failure: if one region or one AZ goes down, the others continue serving users. It also brings lower latency because users can be served from the closest region, and enables fast local failover to a healthy region or AZ without long outages. In practice, you’d set up global routing to direct traffic to the nearest or healthiest location and use replication strategies so data stays consistent across regions, with trade-offs to manage like higher cost and complexity. Centralizing everything in one region reduces resilience, spreading resources randomly doesn’t guarantee reliability, and limiting to a single AZ defeats redundancy.