Designing Cross-Region DR for EC2 and RDS with RPO 15 min, RTO 1 hour
A company is designing a disaster recovery (DR) strategy for a critical application that runs on EC2 instances with an RDS database. The DR site must be in a different AWS Region. The Recovery Point Objective (RPO) is 15 minutes, and Recovery Time Objective (RTO) is 1 hour. Which TWO actions should the company take to meet these objectives? (Choose TWO.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure Amazon Route 53 with health checks and failover routing to the DR region.
Options C and D are correct. D: Creating an RDS cross-Region read replica in the DR region allows the replica to be promoted to the primary database with minimal data loss, meeting the 15-minute RPO. C: Configuring Amazon Route 53 with health checks and failover routing enables automatic traffic redirection to the DR region within the 1-hour RTO. Option A is wrong because copying AMIs and RDS snapshots every 15 minutes would require launching EC2 instances and restoring the database from snapshots, which can exceed the 1-hour RTO. Option B is wrong because manually pre-provisioning resources with CloudFormation does not provide the automated failover needed to meet the RTO. Option E is wrong because S3 cross-Region replication does not address the EC2 and RDS components of the application.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use AWS Backup to copy EC2 AMIs and RDS snapshots to the DR region every 15 minutes.
Why it's wrong here
AWS Backup's scheduled AMI and RDS snapshots are point-in-time copies, not continuous replication. Creating an AMI or snapshot takes time to complete, and then copying it to the DR region adds additional latency; reaching a true 15-minute RPO is not feasible because the actual data loss window spans from when the snapshot was initiated through when the copy finishes. Even after the snapshot arrives, recovery requires restoring EC2 instances and RDS databases from the snapshots, which can easily exceed the 1-hour RTO depending on volume size and instance type. This approach is better suited for periodic, lower-frequency backup compliance rather than real-time disaster recovery.
- ✗
Use AWS CloudFormation to pre-provision resources in the DR region manually.
Why it's wrong here
CloudFormation templates help you codify your infrastructure, but 'manually' pre-provisioning resources in the DR region means a human must take action after a disaster is declared. That manual runbook step adds unpredictable delay to recovery, so it cannot meet a strict 1-hour RTO. Even if templates are ready to run, stack creation and resource initialization take time, and the plan does not include any automated health detection or traffic rerouting. Without automation, CloudFormation is an enablement tool, not a DR failover mechanism, and pre-provisioning alone does not address the RPO or recover application data.
- ✓
Configure Amazon Route 53 with health checks and failover routing to the DR region.
Why this is correct
Amazon Route 53 health checks monitor the primary endpoint (e.g., an Application Load Balancer or an IP address) and automatically detect when it becomes unhealthy. With failover routing, Route 53 stops returning the primary resource's DNS answer and instead returns the DR region's endpoint, effectively steering user traffic within minutes. This directly supports the RTO by eliminating the need for manual DNS changes, and it works with any application architecture as long as the endpoint can be health-checked. However, Route 53 only handles traffic redirection—it does not replicate data or pre-warm compute, so it must be paired with a data replication strategy to also meet the RPO.
- ✓
Create an RDS cross-Region read replica in the DR region.
Why this is correct
An RDS cross-Region read replica uses asynchronous replication to maintain a continuously updated copy of the database in the DR region, giving a very low RPO—typically seconds to minutes—because transactions are replayed as they are committed on the primary. In a disaster, the read replica can be promoted to a standalone primary DB instance via a single API call or console action, which can be scripted and executed in minutes to meet the 1-hour RTO. This approach is superior to snapshot-based copying for the database tier because it does not require a full restore; the data is already hydrated and available for promotion. Remember that the replica is read-only before promotion, so any application writes to the DR database are only possible after promotion completes.
- ✗
Configure S3 cross-Region replication for application data stored in S3.
Why it's wrong here
S3 Cross-Region Replication (CRR) copies only objects in S3 buckets to the destination region, and it is asynchronous and eventually consistent, so it does not provide a defined RPO guarantee for the moment of a disaster. More importantly, CRR does nothing for EC2 instances, VPC configuration, or the RDS database, so the application stack itself still has no compute or data tier in the DR region. Even if the S3 data arrives, you would need separate compute and database resources to serve traffic, and the application may have dependencies on state outside S3. This option could be part of a broader strategy, but by itself it cannot recover the application or meet the required RTO/RPO.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This DOP-C02 question is part of Courseiva's 1,298-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DOP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is designing a disaster recovery strategy for a critical application that requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 hour. The application runs on EC2 with data stored in Amazon RDS Multi-AZ. Which approach meets these requirements?
medium- ✓ A.Use a pilot light strategy with RDS cross-Region read replicas and automated backups
- B.Use backup and restore with daily snapshots to another Region
- C.Use a warm standby with a scaled-down production environment in another Region
- D.Use a Multi-AZ deployment in the same Region for DR
Why A: A pilot light strategy with RDS cross-Region read replicas and automated backups meets the RTO of 15 minutes and RPO of 1 hour. The cross-Region read replica provides near-synchronous replication with an RPO typically under 5 seconds, and automated backups enable point-in-time recovery within the 1-hour RPO. The pilot light approach allows rapid promotion of the replica to a primary instance, achieving the 15-minute RTO by keeping minimal core services running in the DR Region.
You might also like
Similar DOP-C02 questions
- A company is designing a disaster recovery strategy for its application. The application runs on EC2 instances and uses…
- A company runs a microservices architecture on Amazon ECS with Fargate. Each service is deployed in its own ECS service.…
- A company runs a critical application on Amazon EC2 instances in an Auto Scaling group. To ensure high availability, the…
- A company is designing a highly available architecture for a web application using AWS services. The application must be…
- A company is deploying a web application on Amazon ECS with Fargate. The application consists of a frontend service and…
Written by Johnson Ajibi, MSc IT Security
Security Systems Architect · founder of Courseiva
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DOP-C02 exam.