mediummultiple choiceObjective-mapped

A developer accidentally deletes important rows in an RDS database. The mistake is discovered 45 minutes later. The database has automated backups enabled with a retention period of 7 days. What is the best way to restore the database to a point just before the deletion?

Question 1mediummultiple choice
Full question →

A developer accidentally deletes important rows in an RDS database. The mistake is discovered 45 minutes later. The database has automated backups enabled with a retention period of 7 days. What is the best way to restore the database to a point just before the deletion?

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 manual snapshot and then run SQL scripts to revert the deletion.

Manual snapshots may not be close to the deletion time, which can lead to restoring data that is too far back. Reversion scripts are also error-prone and may be difficult to apply safely without additional data consistency checks.

B

Best answer

Use point-in-time restore (PITR) to restore the database to a specific timestamp before the deletion, based on automated backups.

With automated backups enabled, RDS supports PITR within the retention window. PITR lets you restore to any second within that window, so you can select a timestamp just before the destructive deletion occurred. This avoids restoring a potentially stale snapshot and eliminates the need for risky manual compensating scripts.

C

Distractor review

Promote an existing read replica to be the primary and then copy the missing rows from logs.

If the replica is an active read replica, it generally replicates changes from the source, including the delete operation. Promoting the replica would typically preserve the deleted state, not recover the missing rows. Also, relying on “logs” is not a standard RDS row-level recovery mechanism.

D

Distractor review

Recreate the instance using the most recent CloudWatch metric alarm snapshot of storage metrics.

CloudWatch metric alarms store metrics/threshold evaluations, not database contents or row data snapshots. Metrics are not sufficient to reconstruct deleted rows.

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: Use point-in-time restore (PITR) to restore the database to a specific timestamp before the deletion, based on automated backups. — With automated backups enabled and sufficient retention coverage, point-in-time restore (PITR) is the best approach to recover to a consistent state just before the deletion. PITR uses automated backups to restore the database to a chosen timestamp within the retention window, including a point immediately prior to the destructive action. This is more precise than restoring a snapshot and avoids manual, potentially unsafe data-reversion steps. A depends on manual snapshots that may not align with the deletion time and requires manual scripts that can introduce consistency and safety issues. C is typically ineffective because read replicas replicate the delete as well, and there is no supported mechanism to “copy missing rows from logs” as described. D confuses monitoring metrics with backup data; CloudWatch metrics cannot recreate database contents.

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.