A Multi-AZ Amazon RDS database experiences incorrect writes at 10:15 UTC due to a buggy release. The team detects the problem at 10:25 UTC. They want to restore the data to a known-good point around 10:15 UTC, and validate the recovered data, without taking the current production instance offline during the recovery process. What is the most appropriate AWS action?

Immediately reboot the RDS instance and rely on the reboot to roll back the bad writes.

Rebooting the instance does not revert committed application transactions. It restarts the database engine; it is not a logical rollback mechanism to a prior timestamp.

Create a new Read Replica from the current primary and use it as the recovered database after applying reverse migrations.

A read replica copies the current state, including the bad writes. Reverse migrations are an application-level strategy and are not equivalent to restoring to an earlier transaction time (and may not correctly undo all effects).

Temporarily disable Multi-AZ to speed up storage rollback, then re-enable Multi-AZ.

Multi-AZ relates to high availability (failover of the standby). It does not provide point-in-time logical recovery to undo incorrect writes.

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 new DB instance using a restore time around 10:15 UTC, then test the restored instance before cutting over. — Use point-in-time restore (PITR). PITR restores an RDS/Aurora database to a specific timestamp (for example, around 10:15 UTC) by using automated backups and transaction logs when available. To keep production available for the incident and validation, restore to a new DB instance (a recovered copy), verify the data correctness on that copy, and then decide when/how to cut over to the recovered instance. A is wrong because reboot does not undo committed transactions or provide recovery to a prior timestamp. C is wrong because read replicas replicate the current incorrect state, and reverse migrations are not a substitute for PITR. D is wrong because disabling Multi-AZ does not provide logical rollback capability and reduces availability during the incident.

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.