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?
Answer choices
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
Restore the current DB instance in place by overwriting it with only the latest automated backup.
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.
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.
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.
Manual snapshots restore to the snapshot time, not to an arbitrary timestamp with the precision required. Requiring the snapshot date to match “today” is overly restrictive and does not satisfy point-in-time recovery needs.
Perform a database-level rollback using transaction logs from the application server without using RDS restore features.
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.
Common exam trap
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Technical deep dive
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SAA-C03 questions linked to SAA-C03 VPC.
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practise SAA-C03 questions linked to SAA-C03 Auto Scaling.
Practise SAA-C03 questions linked to SAA-C03 disaster recovery questions.
Practise SAA-C03 questions linked to SAA-C03 high availability questions.
Practise SAA-C03 questions linked to SAA-C03 cost optimization questions.
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
Question 2
Question 3
Question 4
Question 5
Question 6
FAQ
Read the scenario before looking for a memorised answer.
The correct answer is: 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) is designed for scenarios like restoring after accidental deletes. With automated backups enabled, PITR can restore the database to a precise timestamp within the retention window. The best practice for minimal disruption is to create a new restored DB instance to validate recovery, and then switch application traffic to the restored instance instead of overwriting the existing production instance immediately. Why others are wrong: Latest-backup restore does not provide the required timestamp precision and increases disruption by overwriting production. Manual snapshot restore is not intended for arbitrary time precision and the “date matches today” condition is not a point-in-time solution. Rolling back using application-server transaction logs is not a dependable managed-recovery approach and does not ensure the correct, consistent DB state at the target time.
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Sign in to join the discussion.