SAA-C03 Design Resilient Architectures Practice Question
Exhibit
Amazon RDS settings DBInstanceIdentifier: prod-orders Engine: postgres MultiAZ: false BackupRetentionPeriod: 7 days Latest automated backup: 2026-04-28T08:00:00Z Incident log 2026-04-28T10:42:17Z: DELETE FROM orders WHERE order_date < '2026-01-01'; 2026-04-28T10:43:05Z: Mistake discovered Recovery objective Restore to 2026-04-28T10:35:00Z, the last safe point before the deletion.
Based on the exhibit, an administrator accidentally deleted data from Amazon RDS for PostgreSQL about 90 minutes ago. Which recovery approach best restores the database to the exact required point in time?
⚠ Common exam trap
Candidates often confuse automated snapshots with point-in-time recovery, assuming a snapshot restore can target a specific time, when in fact snapshots are point-in-time captures and cannot replay transaction logs to reach an arbitrary second.
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
✓
Restore the database to the specified point in time into a new DB instance.
Amazon RDS for PostgreSQL supports Point-in-Time Recovery (PITR), which allows you to restore a DB instance to any second within the backup retention period, up to the last five minutes. Since the deletion occurred approximately 90 minutes ago, you can restore to that exact point in time by specifying the timestamp, and RDS will create a new DB instance from automated backups and transaction logs. This is the only option that recovers the exact state before the accidental deletion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Restore the latest automated snapshot back onto the existing DB instance.
Why it's wrong here
A snapshot restore returns the database to the time the snapshot was taken, not to an exact minute before the incident. It also cannot preserve later valid changes that occurred after the snapshot and before the mistaken delete.
When this WOULD be correct
This option would be correct if the question asked to restore the database to the most recent available snapshot (e.g., after a catastrophic failure) and there was no need for point-in-time recovery.
- ✓
Restore the database to the specified point in time into a new DB instance.
Why this is correct
Point-in-time restore uses automated backups plus transaction logs to recreate the database at a specific moment. For accidental deletion, this is the correct RDS recovery method because it can recover the database to just before the bad change while preserving all legitimate data up to that point.
- ✗
Create a read replica and promote it after the deletion is noticed.
Why it's wrong here
Promoting a read replica after noticing the accidental deletion will not recover the lost data because a read replica is an asynchronously updated copy of the source database that continuously applies changes from the source's transaction logs. The same DELETE statement is replayed on the replica, so once promoted it simply becomes the new primary with the same missing rows; if promotion happens before the replica catches up, you may still see the pre-delete state temporarily, but the replica will apply the DELETE and eventually match the deleted state. Read replicas are designed for read offloading and scaling, not for point-in-time rollback, and they cannot be rewound to a specific timestamp. Therefore, promoting a read replica only perpetuates the accidental deletion rather than undoing it.
When this WOULD be correct
This option would be correct if the question asked for a way to offload read traffic from the primary database or to provide a standby for disaster recovery in a different region, without needing to recover deleted data.
- ✗
Enable Multi-AZ so the database can automatically undo application mistakes.
Why it's wrong here
Enabling Multi-AZ for an RDS database does not protect against logical corruption, application mistakes, or accidental DELETEs. Multi-AZ creates a synchronous standby replica in a different Availability Zone, used only for automatic failover during infrastructure or host-level failures; all data-modifying transactions, including the erroneous DELETE, are replicated synchronously to the standby. Because the standby is an exact live copy, it reflects the deleted state as soon as the transaction commits, and it cannot 'undo' application changes or restore data to a prior point in time. Multi-AZ is a high-availability feature, not a backup/recovery or rollback mechanism.
When this WOULD be correct
A question asks for the best approach to ensure automatic failover and minimize downtime during a planned maintenance event or an Availability Zone outage for an RDS database.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Restore the database to the specified point in time into a new DB instance.Correct answer▾
Why this is correct
Point-in-time restore uses automated backups plus transaction logs to recreate the database at a specific moment. For accidental deletion, this is the correct RDS recovery method because it can recover the database to just before the bad change while preserving all legitimate data up to that point.
✗Restore the latest automated snapshot back onto the existing DB instance.Wrong answer — click to see why▾
Why this is wrong here
Restoring the latest automated snapshot would not recover data to a specific point in time 90 minutes ago; it only restores to the snapshot creation time, which is likely much earlier.
★ When this WOULD be the correct answer
This option would be correct if the question asked to restore the database to the most recent available snapshot (e.g., after a catastrophic failure) and there was no need for point-in-time recovery.
Why candidates choose this
Candidates may think snapshots are the primary recovery mechanism and overlook that RDS supports point-in-time recovery for more granular restoration.
✗Create a read replica and promote it after the deletion is noticed.Wrong answer — click to see why▾
Why this is wrong here
Creating a read replica does not restore data; it only creates a live copy of the current database, which already has the deletion. Promoting it would not recover the deleted data from 90 minutes ago.
★ When this WOULD be the correct answer
This option would be correct if the question asked for a way to offload read traffic from the primary database or to provide a standby for disaster recovery in a different region, without needing to recover deleted data.
Why candidates choose this
Candidates may think a read replica can be used for point-in-time recovery because it is a copy of the database, but they overlook that it reflects the current state, not a past state.
✗Enable Multi-AZ so the database can automatically undo application mistakes.Wrong answer — click to see why▾
Why this is wrong here
Multi-AZ provides high availability through synchronous replication to a standby instance, but it does not enable point-in-time recovery or undo application mistakes like accidental data deletion.
★ When this WOULD be the correct answer
A question asks for the best approach to ensure automatic failover and minimize downtime during a planned maintenance event or an Availability Zone outage for an RDS database.
Why candidates choose this
Candidates may mistakenly believe that Multi-AZ includes automatic backup or rollback capabilities, confusing high availability with data recovery features.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
One of 935 original SAA-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 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 SAA-C03 exam.