An Amazon RDS for PostgreSQL DB cluster has automated backups turned on with a 7-day retention period. A SysOps administrator needs to create a new RDS DB cluster by using data that is no more than…

The correct answer is A. Identify the most recent automated snapshot. Restore the snapshot to a new RDS DB cluster. C. Create a read replica instance in the original RDS DB cluster. Promote the read replica to a. RDS PostgreSQL DB Cluster Recovery Option A is correct because RDS automated backups include daily snapshots, so the most recent snapshot is guaranteed to be within 24 hours old. Restoring it to a new cluster is a native, fully managed RDS operation requiring only a few console…

Submitted by manish99· Mar 30, 2026Reliability and Business Continuity

Question

An Amazon RDS for PostgreSQL DB cluster has automated backups turned on with a 7-day retention period. A SysOps administrator needs to create a new RDS DB cluster by using data that is no more than 24 hours old from the original DB cluster. Which solutions will meet these requirements with the LEAST operational overhead? (Choose two.)

Options

AIdentify the most recent automated snapshot. Restore the snapshot to a new RDS DB cluster.
BBack up the database to Amazon S3 by using native database backup tools. Create a new RDS
CCreate a read replica instance in the original RDS DB cluster. Promote the read replica to a
DCreate a new RDS DB cluster. Use AWS Database Migration Service (AWS DMS) to migrate
EUse the pg_dump utility to export data from the original RDS DB cluster to an Amazon EC2

How the community answered

(36 responses)

A
69% (25)
B
19% (7)
D
8% (3)
E
3% (1)

Explanation

RDS PostgreSQL DB Cluster Recovery

Option A is correct because RDS automated backups include daily snapshots, so the most recent snapshot is guaranteed to be within 24 hours old. Restoring it to a new cluster is a native, fully managed RDS operation requiring only a few console clicks or a single CLI command - minimal overhead.

Option C is correct because a read replica continuously replicates data from the primary cluster in near-real-time (seconds behind, not hours), so it always satisfies the "no more than 24 hours old" requirement. Promoting it to a standalone cluster is also a single built-in RDS operation.

Why the distractors fail:

B requires manually running native PostgreSQL backup tools and uploading to S3, then restoring - multiple manual steps add overhead.
D involves provisioning a DMS replication instance, configuring source/target endpoints, and running a migration task - significant setup overhead for what is a simple data copy.
E uses pg_dump which requires connecting to EC2, executing the export, then importing - a fully manual multi-step process with high operational overhead.

Memory tip: On AWS exams, least operational overhead almost always means using a managed, built-in AWS feature over manual tools. Snapshots and read replicas are native to RDS - anything requiring EC2, DMS setup, or manual exports is a red flag for added overhead.

Topics

#RDS Backup#RDS Restore#RDS Read Replicas#Business Continuity

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice