mediummultiple choiceObjective-mapped

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?

Question 1mediummultiple choice
Full question →

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?

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 back onto the existing DB instance.

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.

B

Best answer

Restore the database to the specified point in time into a new DB instance.

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.

C

Distractor review

Create a read replica and promote it after the deletion is noticed.

A read replica continuously applies changes from the source database, including the accidental delete. Promoting it would not roll the data back and would simply make the deleted state the new primary.

D

Distractor review

Enable Multi-AZ so the database can automatically undo application mistakes.

Multi-AZ improves availability during infrastructure failure, but it does not protect against logical corruption or user error. The same bad DELETE would be replicated to the standby.

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: Restore the database to the specified point in time into a new DB instance. — For accidental data deletion, the correct recovery approach is RDS point-in-time restore. AWS can combine automated backups with transaction logs to create a new DB instance that represents the database exactly at 10:35 UTC, which is before the erroneous delete occurred. That is the standard way to recover logical data loss without depending on a full manual rebuild. Why others are wrong: Restoring the latest snapshot is too coarse and may lose valid data changes. A read replica is not a backup because it faithfully reproduces the bad change. Multi-AZ protects against instance or AZ failure, but it does not roll back user mistakes.

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.