The correct action is to use point-in-time restore to create a new database instance at 10:29 UTC, then switch the application to it. This works because Amazon RDS supports point-in-time recovery (PITR), which lets you restore a database to any second within your backup retention period, typically up to the last five minutes. By restoring to 10:29 UTC—one minute before the corruption at 10:30 UTC—you recover the last good state with minimal data loss, then redirect the application to the new instance. On the SAA-C03 exam, this scenario tests your understanding of RDS automated backups and PITR as a disaster recovery mechanism; a common trap is thinking you can restore in-place or that you must use a manual snapshot, but PITR is the precise tool for time-specific recovery. Remember the “one-minute rule”: always restore to the second just before the corruption event, not the event time itself.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
RDS backup configuration:
Automated backups: enabled
Backup retention: 14 days
Latest manual snapshot: 2026-04-18 02:00 UTC
Operations log:
10:30 UTC - schema migration started
10:36 UTC - application errors began
10:55 UTC - corrupted rows discovered
Requirement:
Restore to a point before the bad migration without losing the entire day of changes
Based on the exhibit, a faulty deployment corrupted production data at 10:30 UTC and the issue was discovered at 10:55 UTC. The team needs to recover the database to the last good state before the corruption. Which action should they take?
RDS backup configuration:
Automated backups: enabled
Backup retention: 14 days
Latest manual snapshot: 2026-04-18 02:00 UTC
Operations log:
10:30 UTC - schema migration started
10:36 UTC - application errors began
10:55 UTC - corrupted rows discovered
Requirement:
Restore to a point before the bad migration without losing the entire day of changes
A
Restore the latest manual snapshot and accept data loss since the snapshot was taken overnight.
Why wrong: A snapshot restore would lose all changes after the snapshot and does not meet the requirement to recover to just before the incident.
B
Use point-in-time restore to create a new database instance at 10:29 UTC, then switch the application to it.
Point-in-time restore is the correct recovery method when automated backups are enabled and the team needs the database just before a known corruption event. Restoring to 10:29 UTC brings the data back to the last safe moment before the migration began. Creating a new instance first avoids modifying the damaged database until the restored copy is validated.
C
Restart the database instance so the transaction log replays the failed migration cleanly.
Why wrong: Restarting does not roll back committed bad changes or reconstruct data to an earlier point in time.
D
Create a read replica and promote it, because replicas always contain the previous transaction state.
Why wrong: A read replica is not a time-travel recovery mechanism and may already include the corrupted changes.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use point-in-time restore to create a new database instance at 10:29 UTC, then switch the application to it.
Option B is correct because Amazon RDS for MySQL (and other engines) supports point-in-time recovery (PITR), which allows you to restore a database to any second within the backup retention period, up to the last five minutes. By restoring to 10:29 UTC (one minute before the corruption at 10:30 UTC), the team can recover the database to its last good state with minimal data loss. After restoring, the application can be pointed to the new instance, avoiding the corrupted data.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Restore the latest manual snapshot and accept data loss since the snapshot was taken overnight.
Why it's wrong here
A snapshot restore would lose all changes after the snapshot and does not meet the requirement to recover to just before the incident.
✓
Use point-in-time restore to create a new database instance at 10:29 UTC, then switch the application to it.
Why this is correct
Point-in-time restore is the correct recovery method when automated backups are enabled and the team needs the database just before a known corruption event. Restoring to 10:29 UTC brings the data back to the last safe moment before the migration began. Creating a new instance first avoids modifying the damaged database until the restored copy is validated.
Related concept
Read the scenario before looking for a memorised answer.
✗
Restart the database instance so the transaction log replays the failed migration cleanly.
Why it's wrong here
Restarting does not roll back committed bad changes or reconstruct data to an earlier point in time.
✗
Create a read replica and promote it, because replicas always contain the previous transaction state.
Why it's wrong here
A read replica is not a time-travel recovery mechanism and may already include the corrupted changes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse point-in-time restore with snapshot restore, assuming snapshots are the only recovery option, or incorrectly believe that restarting or promoting a replica can undo a logical corruption that has already been written to disk.
Detailed technical explanation
How to think about this question
Point-in-time recovery in Amazon RDS works by restoring automated backups (snapshots) and then applying transaction logs (binary logs for MySQL/MariaDB, or WAL segments for PostgreSQL) up to the specified time. The backup retention period must be set to at least 1 day for PITR to be available, and the restore creates a new DB instance with a different endpoint, requiring application connection string updates. In real-world scenarios, teams often use PITR to recover from accidental data deletion or schema changes, but they must ensure the restore time is before the corruption event, accounting for any clock skew.
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.
TExam Day Tips
→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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Resilient Architectures — This question tests Design Resilient Architectures — 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 to create a new database instance at 10:29 UTC, then switch the application to it. — Option B is correct because Amazon RDS for MySQL (and other engines) supports point-in-time recovery (PITR), which allows you to restore a database to any second within the backup retention period, up to the last five minutes. By restoring to 10:29 UTC (one minute before the corruption at 10:30 UTC), the team can recover the database to its last good state with minimal data loss. After restoring, the application can be pointed to the new instance, avoiding the corrupted data.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.