mediummulti selectObjective-mapped

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.

Question 1mediummulti select
Full question →

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

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 only the affected table from the latest snapshot and keep the current cluster online.

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

Best answer

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

Distractor review

Reboot the writer so Aurora automatically rolls back the bad migration.

A reboot does not undo committed database changes. Once the migration is written, restarting the writer will not reverse the corruption.

D

Best answer

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

Distractor review

Promote a read replica from the same cluster without restoring from backup.

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 trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

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. — Point-in-time restore lets the team recreate the database state from just before the bad migration, which is the fastest supported way to recover to a specific timestamp. Because the restore creates a new cluster or instance, the application must then be pointed to the recovered endpoint after validation. Those two steps provide the cleanest recovery path with the least manual data surgery. You cannot reliably recover a corrupted production database by rebooting or by selectively restoring a table into the live cluster. Promoting a replica only changes which node is primary; it does not rewind the data to an earlier point in time. The correct recovery workflow is restore first, then redirect the application.

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.