SAA-C03 Design Resilient Architectures Practice Question
Exhibit
RDS backup status: - Automated backups: Enabled - Backup retention period: 14 days - Latest automated snapshot: 2026-04-27 09:00 UTC - Latest restorable time: 2026-04-27 15:14 UTC Incident timeline: - 2026-04-27 15:11 UTC: deployment script accidentally deleted critical rows - 2026-04-27 15:12 UTC: application detected missing data - Required restore point: 2026-04-27 15:10 UTC Operations note: The business wants to recover to a new database first, verify data, and then cut over the application.
Based on the exhibit, the team must restore an Amazon RDS for PostgreSQL database to the exact state just before a bad delete happened. What is the best recovery approach?
⚠ Common exam trap
A common mix-up: candidates confuse read replicas or Multi-AZ as solutions for logical data corruption, when in fact they only protect against infrastructure failures, not user errors like a bad delete.
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
✓
Perform a point-in-time restore to 2026-04-27 15:10 UTC into a new DB instance, then cut over after validation.
Point-in-time recovery (PITR) allows you to restore an Amazon RDS for PostgreSQL database to any second within the backup retention period, using automated backups and transaction logs. By restoring to 2026-04-27 15:10 UTC, just before the bad delete occurred, you can recover the exact state without data loss, then cut over after validation.
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 and accept data loss from the last backup window.
Why it's wrong here
Restoring the latest automated snapshot would bring the database back to the exact point in time when that snapshot was captured, not to the target time of 2026-04-27 15:10 UTC. Since automated snapshots are taken daily (and manual snapshots only when you take them), if the incident occurred after the last snapshot, all transactions committed since that snapshot—including the valid rows that should be preserved—would be lost. While a snapshot restore is a valid recovery option, it cannot provide fine-grained point-in-time recovery, so it would not meet the requirement to restore to the specific pre-delete moment and would leave you short of the desired recovery point objective.
When this WOULD be correct
This option would be correct if the question asked for the fastest recovery method to minimize downtime and the RPO allowed data loss up to the last backup window (e.g., a non-critical test database where losing recent changes is acceptable).
- ✓
Perform a point-in-time restore to 2026-04-27 15:10 UTC into a new DB instance, then cut over after validation.
Why this is correct
Point-in-time restore uses the automated backups and transaction logs to rebuild the database to an exact time before the bad change. The exhibit confirms the requested restore time is within the restorable window, and the business wants to validate the restored copy before switching traffic. Restoring to a new instance first is the safest way to recover without risking the current production database.
- ✗
Promote a read replica because it will contain the deleted rows and can replace the primary immediately.
Why it's wrong here
A read replica operates asynchronously, meaning it continually applies the same changes that reach the primary database after a brief replication lag. The accidental DELETE is a committed transactional change, so it will replicate to the replica just like any other statement; the replica will contain deleted rows only if it is frozen at a point before the delete replicated, which is not guaranteed and cannot be precisely controlled. Promoting the replica gives you a live database at whatever its current, post-delete state is, not a point-in-time pre-incident copy, so it cannot satisfy the requirement to restore to exactly 2026-04-27 15:10 UTC.
When this WOULD be correct
When the question asks for the fastest way to reduce read load on the primary database with minimal downtime, and the replica is already in sync and can be promoted to become the new primary.
- ✗
Enable Multi-AZ on the current database and wait for automatic failover to reverse the delete.
Why it's wrong here
Multi-AZ on Amazon RDS provides high availability by maintaining a synchronous standby replica in a different Availability Zone that is automatically promoted during failover caused by infrastructure failures or maintenance. It is a physical copy of the database, not a logical undo log: any committed DELETE on the primary is also committed on the standby, so a failover would fail over to a database that already has the rows deleted. Enabling Multi-AZ and waiting for failover cannot roll back a logical data modification; it only restores service availability after a loss of the primary instance, not after an application error.
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.
✓Perform a point-in-time restore to 2026-04-27 15:10 UTC into a new DB instance, then cut over after validation.Correct answer▾
Why this is correct
Point-in-time restore uses the automated backups and transaction logs to rebuild the database to an exact time before the bad change. The exhibit confirms the requested restore time is within the restorable window, and the business wants to validate the restored copy before switching traffic. Restoring to a new instance first is the safest way to recover without risking the current production database.
✗Restore the latest automated snapshot and accept data loss from the last backup window.Wrong answer — click to see why▾
Why this is wrong here
Restoring the latest automated snapshot would not recover to the exact state just before the bad delete at 2026-04-27 15:10 UTC; it would only restore to the last snapshot time, which could be hours earlier, causing data loss beyond the deleted rows.
★ When this WOULD be the correct answer
This option would be correct if the question asked for the fastest recovery method to minimize downtime and the RPO allowed data loss up to the last backup window (e.g., a non-critical test database where losing recent changes is acceptable).
Why candidates choose this
Candidates may think restoring a snapshot is the simplest recovery method and overlook the need for precise point-in-time recovery, or they may not realize that automated snapshots are taken periodically and do not capture every transaction.
✗Promote a read replica because it will contain the deleted rows and can replace the primary immediately.Wrong answer — click to see why▾
Why this is wrong here
A read replica is asynchronous and may not contain the exact state before the delete; it cannot be promoted to reverse a specific point-in-time deletion without data loss or inconsistency.
★ When this WOULD be the correct answer
When the question asks for the fastest way to reduce read load on the primary database with minimal downtime, and the replica is already in sync and can be promoted to become the new primary.
Why candidates choose this
Candidates may think a read replica has the same data as the primary at all times and can be used for disaster recovery, overlooking replication lag and the need for point-in-time precision.
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.