Aurora Backtrack rewinds an Aurora MySQL cluster to a previous point in time in seconds, without restoring from a backup — a fast way to undo a bad change like an accidental mass delete.
Backtrack vs restore
A traditional restore creates a new cluster from a snapshot (slow). Backtrack rewinds the existing cluster to a recent time almost instantly, ideal for quickly undoing a mistake. The tell is “quickly undo/rewind a recent erroneous change” on Aurora MySQL.
Test yourself
A developer accidentally ran a bad UPDATE on an Aurora MySQL database and needs to undo it in seconds without spinning up a new cluster. What’s the best option?
- Restore from a snapshot to a new cluster
- Aurora Backtrack to just before the change
- Enable Multi-AZ
- Create a Read Replica
👉 Click to reveal the answer & explanation
Correct answer: B. Backtrack rewinds the existing Aurora MySQL cluster to a point just before the mistake in seconds, no new cluster needed. Snapshot restore (A) is slower and creates a new cluster; Multi-AZ (C) is failover; a Read Replica (D) scales reads, it doesn’t undo changes.
Related topics
Amazon Aurora · Aurora Global Database · Amazon RDS
Ready to pass the AWS Solutions Architect Associate (SAA-C03)?
Stop guessing whether you’re ready. Our full-length, exam-realistic practice exams put you through the exact question style you’ll face — with a detailed explanation behind every answer, so you learn why, not just what.
- ✓ 6 full-length practice exams
- ✓ A detailed explanation for every single question
- ✓ Realistic, scenario-based questions — not memory dumps
- ✓ Lifetime access, kept current for 2026
Get the SAA-C03 Practice Exams →or try 25 free questions first