SAA-C03 Design Resilient Architectures Practice Question
A production team accidentally deletes critical rows in an Amazon RDS for PostgreSQL database. The deletion occurred about 6 hours ago. The team wants to recover to a specific point in time with minimal disruption.
Assuming automated backups are enabled, which approach provides the best resilience outcome?
⚠ Common exam trap
Watch out — candidates often think restoring in place (Option A) is faster or simpler, but they overlook that PITR provides granular recovery without overwriting the production instance, which is the key to minimal disruption.
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
✓
Use point-in-time recovery (PITR) to restore a new DB instance to a timestamp shortly before the deletion, then switch application traffic to the restored instance.
Point-in-time recovery (PITR) allows you to restore a new DB instance to any second within the automated backup retention period, which includes transaction logs. By restoring to a timestamp just before the deletion, you recover the lost rows without affecting the current production instance, then switch traffic to the new instance for minimal disruption.
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 current DB instance in place by overwriting it with only the latest automated backup.
Why it's wrong here
Restoring only the latest automated backup typically returns the database to the backup time, not to an exact time before the deletion. It also overwrites the running environment immediately, which increases disruption risk and reduces the ability to verify before cutover.
When this WOULD be correct
This option would be correct if the question stated that the database was completely corrupted or lost, and the goal was to restore to the most recent consistent state with minimal downtime, without needing to recover to a specific point in time.
- ✓
Use point-in-time recovery (PITR) to restore a new DB instance to a timestamp shortly before the deletion, then switch application traffic to the restored instance.
Why this is correct
With automated backups enabled, PITR allows restoring to a precise timestamp within the retention window. Creating a new DB instance (rather than overwriting production) enables verification of data correctness and then a controlled cutover, minimizing disruption while meeting the “specific point in time” requirement.
- ✗
Create a manual snapshot and restore from it only if the snapshot date exactly matches today.
Why it's wrong here
Creating a manual snapshot only captures the database state at the exact moment the snapshot is initiated, so restoring from it cannot target a specific point in time other than that snapshot time. The condition that the snapshot date 'exactly matches today' is arbitrary and irrelevant to the recovery requirement, which demands restoration to a timestamp shortly before the deletion, not merely to a snapshot taken on the same calendar day. Even if a manual snapshot exists from today, it would only be usable if its creation time aligns precisely with the desired recovery point, which is practically impossible unless the snapshot was taken at that exact second. Manual snapshots are intended for backups, not for granular point-in-time recovery; that capability is exclusively provided by automated backups and PITR.
When this WOULD be correct
If the question asked for a strategy to create a backup for future recovery without relying on automated backups, and the snapshot date matched the required recovery point, then creating a manual snapshot and restoring from it would be correct.
- ✗
Perform a database-level rollback using transaction logs from the application server without using RDS restore features.
Why it's wrong here
RDS transaction logs on the application server are not a reliable mechanism for managed point-in-time recovery of RDS storage. Additionally, you cannot assume the necessary log retention, ordering, and consistency guarantees to reconstruct the exact DB state at the target time.
When this WOULD be correct
If the question specified that the application server maintains its own transaction logs and the database is a self-managed PostgreSQL instance (not RDS), then performing a database-level rollback using those logs would be a valid recovery approach.
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.
✓Use point-in-time recovery (PITR) to restore a new DB instance to a timestamp shortly before the deletion, then switch application traffic to the restored instance.Correct answer▾
Why this is correct
With automated backups enabled, PITR allows restoring to a precise timestamp within the retention window. Creating a new DB instance (rather than overwriting production) enables verification of data correctness and then a controlled cutover, minimizing disruption while meeting the “specific point in time” requirement.
✗Restore the current DB instance in place by overwriting it with only the latest automated backup.Wrong answer — click to see why▾
Why this is wrong here
Restoring the current DB instance in place by overwriting it with the latest automated backup would revert all data to the backup time, losing all changes made in the last 6 hours, including the critical rows that were deleted. It does not allow recovery to a specific point in time before the deletion.
★ When this WOULD be the correct answer
This option would be correct if the question stated that the database was completely corrupted or lost, and the goal was to restore to the most recent consistent state with minimal downtime, without needing to recover to a specific point in time.
Why candidates choose this
Candidates may think that restoring the latest backup is the simplest and fastest way to recover, overlooking the need for point-in-time recovery to avoid losing recent data changes.
✗Create a manual snapshot and restore from it only if the snapshot date exactly matches today.Wrong answer — click to see why▾
Why this is wrong here
Creating a manual snapshot today and restoring from it would not recover data from 6 hours ago; it would only restore to the snapshot creation time, which is after the deletion.
★ When this WOULD be the correct answer
If the question asked for a strategy to create a backup for future recovery without relying on automated backups, and the snapshot date matched the required recovery point, then creating a manual snapshot and restoring from it would be correct.
Why candidates choose this
Candidates may think manual snapshots are more reliable or controllable than automated backups, or they may misunderstand that manual snapshots capture a point in time at creation, not retroactively.
✗Perform a database-level rollback using transaction logs from the application server without using RDS restore features.Wrong answer — click to see why▾
Why this is wrong here
RDS does not expose transaction logs for direct database-level rollback; point-in-time recovery is the only supported method to restore to a specific time using automated backups and transaction logs stored by AWS.
★ When this WOULD be the correct answer
If the question specified that the application server maintains its own transaction logs and the database is a self-managed PostgreSQL instance (not RDS), then performing a database-level rollback using those logs would be a valid recovery approach.
Why candidates choose this
Candidates may assume that because PostgreSQL supports transaction log replay, they can bypass RDS restore features and directly manipulate logs, underestimating the managed nature of RDS where logs are not directly accessible for manual recovery.
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
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.