SOA-C02 Question 106
Single answerYour company’s database team is running an Amazon RDS MySQL database instance in production. They report an accidental deletion of several critical records from the database. You are tasked with restoring the database to its state from 2 hours ago with minimal downtime. What is the best approach to resolve this issue?
- A
Perform a point-in-time restore to a new RDS instance using the automated backups created by Amazon RDS.
- B
Manually restore the deleted records by querying the database's binary logs.
- C
Promote a read replica of the database to the master instance and use it as the new production database.
- D
Restore the most recent snapshot of the database and overwrite the current database instance.
Show answer and explanation
Correct answer: A
Explanation
Point-in-time restore is a feature of Amazon RDS that allows administrators to restore their database to any specific time within the retention period of automated backups. This approach is ideal when you need to recover from accidental data loss without affecting the current database instance. Other options, like using binary logs or promoting a read replica, either require more manual intervention or do not meet the requirements of restoring to a specific point in time.
- A. Correct.
This is the correct approach. Point-in-time restore allows you to restore the database to a specific time, such as 2 hours ago, and creates a new RDS instance so the current database remains unaffected.
- B. Incorrect.
While binary logs could theoretically be used to manually restore the deleted records, this process is complex and error-prone. It is not the recommended or efficient approach for this scenario.
- C. Incorrect.
Promoting a read replica does not enable you to roll back to a specific point in time. It only creates a standalone database instance based on the current state of the replica.
- D. Incorrect.
Restoring the most recent snapshot would not help in this case, as it may not include the state of the database from exactly 2 hours ago. Additionally, overwriting the current instance could lead to further data loss.