The Development team recently executed a database script containing several data definition language (DDL) and data manipulation language (DML) statements on an Amazon Aurora MySQL DB cluster. The release accidentally deleted thousands of rows from an important table and broke some application functionality. This was discovered 4 hours after the release. Upon investigation, a Database Specialist tracked the issue to a DELETE command in the script with an incorrect WHERE clause filtering the wrong set of rows. The Aurora DB cluster has Backtrack enabled with an 8-hour backtrack window. The Database Administrator also took a manual snapshot of the DB cluster before the release started. The database needs to be returned to the correct state as quickly as possible to resume full application functionality. Data loss must be minimal. How can the Database Specialist accomplish this?
Show Answer & Explanation
Correct Answer: A. Quickly rewind the DB cluster to a point in time before the release using Backtrack.
Why A is correct: Aurora Backtrack allows you to quickly rewind the database to a specific point in time (within the 8-hour window) without restoring from backups. This is the fastest method with minimal data loss - you simply backtrack to before the DELETE statement (4 hours ago, well within the 8-hour window). Backtrack typically completes in minutes and doesn't require creating new clusters or copying data. Why other options are wrong: B: PITR works but requires restoration to a new cluster and manual data copying, taking much longer than Backtrack. C: Restoring from snapshot loses 4 hours of data (all changes since the snapshot) and requires application reconfiguration. D: Cloning and copying data is unnecessarily complex when Backtrack can directly rewind the cluster.