Fail over an RDS PostgreSQL cross-Region read replica behind a Route 53 failover record
A solutions architect must implement a multi-Region architecture for an Amazon RDS for PostgreSQL database that supports a web application. The database launches from an AWS CloudFormation template that includes AWS services and features that are present in both the primary and secondary Regions. The database is configured for automated backups, and it has an RTO of 15 minutes and an RPO of 2 hours. The web application is configured to use an Amazon Route 53 record to route traffic to the database. Which combination of steps will result in a highly available architecture that meets all the requirements? (Choose two.)
Community Votes
100% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A cross-Region read replica replicates continuously rather than on a schedule, so the RPO is far tighter than the two-hour requirement, and promotion takes on the order of a minute, which is what makes the fifteen-minute RTO achievable without a restore from backup.
A web application uses an RDS for PostgreSQL database that is created from a CloudFormation template and configured with automated backups. The target is a multi-Region architecture with an RTO of fifteen minutes and an RPO of two hours, and the application resolves the database through a Route 53 record.
Satisfying the RPO with a scheduled backup copy and calling it a standby. Copying the latest automated backup every two hours leaves nothing running in the secondary Region to be promoted, so a failover would still require a restore that blows the fifteen-minute RTO.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A cross-Region read replica continuously replicates the primary's transaction log to the secondary Region, so the data loss on failover is bounded by replication lag rather than by a backup schedule, which comfortably satisfies the two-hour RPO. Promoting that replica takes on the order of a minute, which is what makes the fifteen-minute RTO reachable, and a Lambda function in the secondary Region can perform the promotion automatically when a failover event occurs. The Route 53 failover routing policy in D then supplies the client-side failover: with primary and secondary endpoints set to the records in each Region and health evaluation enabled, applications resolving the database through that record are directed to the promoted instance in the secondary Region. Together they give a highly available design meeting both objectives.Why the Other Options Are Wrong
B: Recreating the database from the latest snapshot in the secondary Region takes far longer than fifteen minutes, because it must copy snapshots, restore them, and update records, so the RTO is not met. C: Copying the latest automated backup every two hours meets the RPO only if the copy completes reliably within that window, and it does not address failover at all because there is no standby database running, so nothing exists to promote and the RTO is not achievable. E: A hot standby restored from an RDS automatic backup has the same RTO problem as B, and it also depends on automated backups having been copied to the secondary Region, which the option does not specify.Community Comment Notes
The community voted 100 to 0 for A and D, and the top-voted comment noted that this is a classic question. Commenters broke down why the others fail in the same terms: C meets the RPO but provides no standby to fail over to, B will not meet the fifteen-minute RTO, and E is incomplete because it does not say how the backups reach the secondary Region.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →