DOP-C02 Multi-Region Deployment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Deploy the application in multiple AWS Regions using an active-active or active-passive pattern

  Why this is correct

  Running the application in multiple AWS Regions using an active-active or active-passive pattern is the foundational disaster recovery strategy for a regional outage. Active-active routes live traffic across Regions for automatic failover, while active-passive keeps a warm standby in another Region that can be promoted via Route 53 health checks and failover policies. This approach directly addresses the failure domain of an entire Region.

• ✗

  Deploy the application across multiple Availability Zones in a single Region

  Why it's wrong here

  Deploying across multiple Availability Zones within a single Region offers high availability against individual AZ or component failures, but every AZ is still dependent on the parent Region's control plane and network. If the Region experiences a widespread outage, all AZs become unavailable simultaneously. This does not satisfy a Region-failure recovery objective.

• ✓

  Replicate data across Regions using services like DynamoDB global tables or RDS cross-Region replication

  Why this is correct

  Replicating data across Regions is a critical enabler for disaster recovery: DynamoDB global tables give multi-Region eventually consistent active-active copies, and RDS Cross-Region Read Replicas provide a promotable standby in another Region. This ensures that data is durable and accessible in the secondary Region, allowing application failover with minimized RPO. It complements compute failover but alone does not provide full application availability without corresponding compute.

• ✗

  Use a single CloudFront distribution with multiple origins in the same Region

  Why it's wrong here

  A single CloudFront distribution with multiple origins confined to the same Region does nothing to survive a regional failure, because CloudFront is an edge caching service, not a failover orchestration layer. Even if CloudFront itself is global, its origins are the actual compute and storage, and if they all live in one Region, they can all fail together. This setup only provides edge caching and latency optimization, not disaster recovery.

• ✗

  Configure RDS read replicas in the same Region

  Why it's wrong here

  Configuring RDS read replicas in the same Region improves read scalability and can help with immediate read traffic during heavy load, but they are not a disaster recovery mechanism for regional loss. If the core Region is destroyed, the primary and same-Region replicas fail together, and there is no standby in another Region to promote. For cross-Region DR, RDS read replicas must be placed in a different Region, where they can be promoted to a primary.

Go deeper

Related to this question