easymultiple choiceObjective-mapped

A production Amazon RDS database has automated backups enabled with sufficient retention. At 10:30 UTC, a release corrupts specific rows. The issue is detected at 10:45 UTC. The team wants to restore the database state to before the corruption with minimal complexity. What should they do?

Question 1easymultiple choice
Full question →

A production Amazon RDS database has automated backups enabled with sufficient retention. At 10:30 UTC, a release corrupts specific rows. The issue is detected at 10:45 UTC. The team wants to restore the database state to before the corruption with minimal complexity. What should they do?

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

Best answer

Perform a point-in-time restore (PITR) to a timestamp just before 10:30 UTC and create a restored DB instance/cluster.

PITR uses automated backups to restore the database to a specific point in time. Selecting a timestamp just before the corruption (for example, slightly before 10:30 UTC) restores the affected data state as it existed before the bad release.

B

Distractor review

Change the VPC route tables so the database restarts in a clean state.

Network route table changes affect connectivity, not database contents. They cannot undo logical data corruption caused by application writes.

C

Distractor review

Relaunch the same DB instance in the same Availability Zone and rely on caching to revert the changes.

Restarting a DB instance does not reverse committed database writes. Server-side caches do not “revert” persisted row corruption; the corrupted data remains stored in the database.

D

Distractor review

Enable a DLQ on the database to store invalid SQL statements until the system is fixed.

Dead-letter queues apply to message-processing systems (for example, SQS consumers). RDS does not use DLQs for SQL execution or transactional writes, so this would not address row-level corruption recovery.

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 (PITR) to a timestamp just before 10:30 UTC and create a restored DB instance/cluster. — Because the corruption is logical and detected after it happens, the appropriate mechanism is backup/restore with point-in-time restore (PITR). With automated backups enabled, PITR lets you restore the database to a chosen timestamp just before the corruption (for example, just before 10:30 UTC) and create a restored DB instance/cluster. This is the most direct and low-complexity way to recover the prior data state. Multi-AZ failover targets availability of the database service, and DLQs address failed message processing, not transactional data correction. Option B changes connectivity, not data. Option C does not undo persisted writes, so corruption remains. Option D is unrelated to relational database recovery mechanisms because DLQs do not capture or roll back SQL changes.

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.