AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company is architecting a disaster recovery (DR) solution for its mission-critical Amazon RDS for PostgreSQL database located in the us-east-1 Region. The primary business requirements are to achieve a low Recovery Point Objective (RPO) and a low Recovery Time Objective (RTO) for the database in a DR site in the us-west-2 Region. The solution must minimize operational overhead by leveraging fully managed AWS services wherever possible. Which approach should a solutions architect recommend to configure the database replication?
Launch an EC2 instance in us-east-1, configure PostgreSQL's native logical replication to stream changes from the primary RDS instance, and then write the changes to a target RDS instance in us-west-2.
Schedule automated snapshots of the RDS instance and configure S3 Cross-Region Replication (CRR) to copy the snapshots to an S3 bucket in us-west-2. In a DR event, restore the latest snapshot to a new RDS instance.
Deploy an AWS Database Migration Service (DMS) replication instance and configure an ongoing replication task with Change Data Capture (CDC) to replicate data from the source RDS instance to a target RDS instance in us-west-2.
Configure a cross-region read replica for the RDS for PostgreSQL instance in us-west-2. In a DR event, promote the read replica to a standalone, writable primary instance.
The correct approach is to use a cross-region read replica. This is a fully managed AWS feature for RDS that provides asynchronous replication to a different region, which is ideal for disaster recovery. In the event of a disaster, the read replica in the DR region can be promoted to a standalone, writable primary instance, which provides a low RTO. Because the replication is continuous and asynchronous, it also provides a low RPO.
The option to use AWS Database Migration Service (DMS) with ongoing replication is less optimal. While it can achieve the goal, DMS is a more complex service to manage, involving replication instances, endpoints, and tasks. It introduces more operational overhead compared to the native, integrated read replica feature, which goes against the requirement to minimize overhead. The strategy of copying automated snapshots to another region using S3 Cross-Region Replication is a valid DR pattern, but it is for backup and restore, not continuous replication. This method would result in a much higher RPO (potentially hours) and RTO (time to restore the snapshot) compared to a read replica, failing to meet the low RPO/RTO requirement. Finally, setting up manual logical replication using an EC2 instance is the least desirable option. It completely contradicts the requirement to use a fully managed service and minimize operational overhead, as it requires manual configuration, management, and maintenance of the replication process on a self-managed server.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a cross-region read replica in RDS, and how does it work?
Open an interactive chat with Bash
How does promoting a read replica to a standalone instance affect operations?
Open an interactive chat with Bash
What makes AWS Database Migration Service (DMS) less suitable for DR in this case?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access