- A
Restore only the affected table from the latest snapshot and keep the current cluster online.
Why wrong: Aurora recovery is not normally done by selectively merging a single table back into the live cluster. That approach is risky, slow, and difficult to validate after a schema-level or data-level corruption event.
- B
Perform a point-in-time restore to a new DB cluster or instance using automated backups.
Point-in-time restore is the supported mechanism for recovering to a specific timestamp before the corruption occurred. It uses automated backups and transaction logs to recreate a clean copy of the database state.
- C
Reboot the writer so Aurora automatically rolls back the bad migration.
Why wrong: A reboot does not undo committed database changes. Once the migration is written, restarting the writer will not reverse the corruption.
- D
Validate the restored database, then repoint the application or DNS name to the restored endpoint.
A PITR restore creates a new cluster or instance, so the application must be cut over to the recovered endpoint after validation. Repointing the application or DNS completes the recovery workflow and returns traffic to the clean database.
- E
Promote a read replica from the same cluster without restoring from backup.
Why wrong: Promoting a replica changes the primary writer, but it does not rewind the data to a point in time before the bad migration. It would promote the same corrupted data set unless a restore is performed first.
Quick Answer
The answer is to restore the database using Aurora point-in-time recovery to a time just before the corruption occurred, then validate the restored database and repoint the application or DNS name to the new endpoint. This is correct because Aurora’s point-in-time recovery (PITR) allows you to restore to any second within the backup retention window, creating a new, independent DB cluster from automated backups. For the SAA-C03 exam, this scenario tests your understanding that PITR is the minimal-effort recovery method for logical corruption like a bad migration, as opposed to restoring from a manual snapshot which is slower and less granular. A common trap is forgetting that you must validate the restored data before switching traffic, as the restore process does not automatically verify data integrity. Memory tip: PITR = “Pinpoint In Time Recovery” — you pick the exact second before the disaster, not after.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
A production Amazon Aurora MySQL database is corrupted by a bad migration at 10:30 UTC, and the problem is discovered at 10:45 UTC. The team wants to recover to the state just before the migration with minimal manual effort. Which two actions should they take? Select two.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Perform a point-in-time restore to a new DB cluster or instance using automated backups.
Option B is correct because Amazon Aurora supports point-in-time recovery (PITR) to any point within the backup retention window, allowing you to restore the database to a state just before the migration (e.g., 10:29 UTC). This uses automated backups and requires minimal manual effort, as you simply specify the target time and a new DB cluster is created.
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 only the affected table from the latest snapshot and keep the current cluster online.
Why it's wrong here
Aurora recovery is not normally done by selectively merging a single table back into the live cluster. That approach is risky, slow, and difficult to validate after a schema-level or data-level corruption event.
- ✓
Perform a point-in-time restore to a new DB cluster or instance using automated backups.
Why this is correct
Point-in-time restore is the supported mechanism for recovering to a specific timestamp before the corruption occurred. It uses automated backups and transaction logs to recreate a clean copy of the database state.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Reboot the writer so Aurora automatically rolls back the bad migration.
Why it's wrong here
A reboot does not undo committed database changes. Once the migration is written, restarting the writer will not reverse the corruption.
- ✓
Validate the restored database, then repoint the application or DNS name to the restored endpoint.
Why this is correct
A PITR restore creates a new cluster or instance, so the application must be cut over to the recovered endpoint after validation. Repointing the application or DNS completes the recovery workflow and returns traffic to the clean database.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Promote a read replica from the same cluster without restoring from backup.
Why it's wrong here
Promoting a replica changes the primary writer, but it does not rewind the data to a point in time before the bad migration. It would promote the same corrupted data set unless a restore is performed first.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think rebooting or promoting a replica can undo data changes, but these actions do not affect committed transactions; only a point-in-time restore can recover to a pre-migration state.
Detailed technical explanation
How to think about this question
Aurora's point-in-time restore works by replaying redo logs from automated backups to the specified timestamp, creating a new, independent cluster. The backup retention window defaults to 1 day but can be configured up to 35 days, and the restore operation is fully managed by AWS, requiring no manual log shipping. In a real-world scenario, you would also need to validate the restored data (Option D) before redirecting traffic to avoid serving corrupted data.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Design Resilient Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
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: Perform a point-in-time restore to a new DB cluster or instance using automated backups. — Option B is correct because Amazon Aurora supports point-in-time recovery (PITR) to any point within the backup retention window, allowing you to restore the database to a state just before the migration (e.g., 10:29 UTC). This uses automated backups and requires minimal manual effort, as you simply specify the target time and a new DB cluster is created.
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 →
Same concept, more angles
4 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses Amazon RDS with automated backups enabled (retention period: 7 days). At 10:30 UTC, a bad release corrupts specific rows in a production table. The team detects the issue at 11:10 UTC. They need to revert the database state to what it was from 10:00–10:30 UTC, recover quickly, and minimize risk to the currently running workload. What is the best option?
medium- A.Reboot the DB instance and rely on the corrupted data being overwritten by storage-level changes.
- ✓ B.Perform a point-in-time restore to a new DB instance using a timestamp before the corruption (for example, a time within 10:00–10:30 UTC).
- C.Restore only the most recent automated backup snapshot, even if it is after the corruption timestamp.
- D.Create a read replica of the current DB instance and overwrite the corrupted table using SELECT queries from the replica.
Why B: Amazon RDS automated backups enable point-in-time recovery (PITR) to any second within the retention window. By restoring to a timestamp between 10:00 and 10:30 UTC, you recover the database to a state before the corruption occurred, without affecting the current production instance. This minimizes risk to the running workload because the restore creates a new DB instance, leaving the original untouched until you are ready to switch.
Variation 2. A production Amazon RDS database has automated backups enabled. At 10:45 UTC, an issue is discovered. The team needs to restore the database to its state as of 10:30 UTC. Which capability should they use?
easy- ✓ A.Point-in-time restore (PITR) using automated backups to a specific timestamp.
- B.Perform a Multi-AZ manual failover of the standby to recover to the earlier timestamp.
- C.Promote a cross-region replication target to replace the current database with the last-known good copy.
- D.Switch to a read replica to access an older view of data without restoring.
Why A: Amazon RDS automated backups enable point-in-time recovery (PITR) to any second within the backup retention period, restoring to a new DB instance. Since the issue was discovered at 10:45 UTC and the desired recovery point is 10:30 UTC, PITR can restore the database to that exact timestamp, provided it falls within the automated backup window and retention period.
Variation 3. 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?
easy- ✓ A.Perform a point-in-time restore (PITR) to a timestamp just before 10:30 UTC and create a restored DB instance/cluster.
- B.Change the VPC route tables so the database restarts in a clean state.
- C.Relaunch the same DB instance in the same Availability Zone and rely on caching to revert the changes.
- D.Enable a DLQ on the database to store invalid SQL statements until the system is fixed.
Why A: Option A is correct because Amazon RDS Point-in-Time Restore (PITR) allows you to restore the database to any second within the backup retention period, using automated backups and transaction logs. By restoring to a timestamp just before 10:30 UTC, you can recover the database to a state before the corruption occurred, creating a new DB instance/cluster with minimal complexity and no data loss from the uncorrupted period.
Variation 4. 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?
hard- A.Restore the latest automated snapshot and accept data loss from the last backup window.
- ✓ B.Perform a point-in-time restore to 2026-04-27 15:10 UTC into a new DB instance, then cut over after validation.
- C.Promote a read replica because it will contain the deleted rows and can replace the primary immediately.
- D.Enable Multi-AZ on the current database and wait for automatic failover to reverse the delete.
Why B: Point-in-time recovery (PITR) allows you to restore an Amazon RDS for PostgreSQL database to any second within the backup retention period, using automated backups and transaction logs. By restoring to 2026-04-27 15:10 UTC, just before the bad delete occurred, you can recover the exact state without data loss, then cut over after validation.
Last reviewed: Jun 11, 2026
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.