A company is designing a pilot light disaster recovery (DR) strategy for a critical application. The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. The application database runs on Amazon RDS, and static assets are stored in Amazon S3. Which configuration should a SysOps administrator implement to meet these DR requirements?
- Enable versioning on both the source and destination S3 buckets to configure S3 Cross-Region Replication (CRR) for static assets, and deploy a cross-region RDS Read Replica for database replication.Answer
- BConfigure Amazon RDS Multi-AZ across regions to automatically failover the database to the secondary region within the 15-minute RTO, and enable S3 Cross-Region Replication (CRR) with versioning.
- CConfigure S3 Cross-Region Replication (CRR) for the static asset bucket to meet the RPO, keeping versioning disabled on both buckets to minimize storage costs.
- DDeploy a cross-region RDS Read Replica for database replication, and use Amazon Route 53 with a simple routing policy to automatically route user traffic to the secondary region when health checks fail.
Answer
Enable versioning on both the source and destination S3 buckets to configure S3 Cross-Region Replication (CRR) for static assets, and deploy a cross-region RDS Read Replica for database replication.
The correct configuration combines S3 Cross-Region Replication (CRR) for static assets and an RDS Read Replica for database replication. S3 CRR requires versioning to be enabled on both the source and destination buckets. An RDS Read Replica provides asynchronous replication to a secondary region and can be promoted to a standalone database during a disaster, meeting the low RTO and RPO requirements.
Step-by-Step Solution
Key Concept
Implementing cross-region disaster recovery using S3 Cross-Region Replication (requiring versioning) and RDS Read Replicas.
Estimated Time:1m 0s