hardmultiple choiceObjective-mapped

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?

Question 1hardmultiple choice
Full question →

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?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Restore the latest automated snapshot and accept data loss from the last backup window.

A snapshot restore goes back to the snapshot time, which is not the exact pre-incident state requested here.

B

Best answer

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 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.

C

Distractor review

Promote a read replica because it will contain the deleted rows and can replace the primary immediately.

A read replica is asynchronous and reflects the source state, including the delete once it replicates. It is not an exact-time recovery method.

D

Distractor review

Enable Multi-AZ on the current database and wait for automatic failover to reverse the delete.

Multi-AZ improves availability, but it does not roll back logical data changes such as accidental deletes.

Common exam trap

Common exam trap: answer the scenario, not the keyword

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

How to think about this question

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.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Perform a point-in-time restore to 2026-04-27 15:10 UTC into a new DB instance, then cut over after validation. — The incident is a logical data-loss event, not an instance failure. The required recovery time is a specific timestamp before the delete, and the exhibit shows that time is within the available restorable window. Point-in-time restore is the correct AWS mechanism because it replays backups and logs to a precise moment. Restoring to a new instance first allows verification before the application is redirected to the recovered database. Why others are wrong: Restoring a snapshot only returns the database to the snapshot time, which may still include the bad delete or lose more recent valid data. A read replica is not a recovery point for exact-time rollback because it follows source changes. Multi-AZ is for availability and failover, not undoing accidental updates or deletes.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.