SOA-C03 · Question #82
A company is using an Amazon Aurora MySQL DB cluster that has point-in-time recovery, backtracking, and automatic backup enabled. A CloudOps engineer needs to be able to roll back the DB cluster to…
The correct answer is C. Use backtracking to rewind the existing DB cluster to the desired recovery point. Aurora MySQL backtracking lets you “rewind” the existing DB cluster to a previous point in time (within the configured backtrack window, such as 72 hours) without creating a new cluster. Point- in-time recovery and automatic backups create a new cluster, which does not meet the…
Question
A company is using an Amazon Aurora MySQL DB cluster that has point-in-time recovery, backtracking, and automatic backup enabled. A CloudOps engineer needs to be able to roll back the DB cluster to a specific recovery point within the previous 72 hours. Restores must be completed in the same production DB cluster. Which solution will meet these requirements?
Options
- ACreate an Aurora Replica. Promote the replica to replace the primary DB instance.
- BCreate an AWS Lambda function to restore an automatic backup to the existing DB cluster.
- CUse backtracking to rewind the existing DB cluster to the desired recovery point.
- DUse point-in-time recovery to restore the existing DB duster to the desired recovery point.
How the community answered
(31 responses)- A3% (1)
- B10% (3)
- C71% (22)
- D16% (5)
Explanation
Aurora MySQL backtracking lets you “rewind” the existing DB cluster to a previous point in time (within the configured backtrack window, such as 72 hours) without creating a new cluster. Point- in-time recovery and automatic backups create a new cluster, which does not meet the requirement to restore in the same production DB cluster, whereas backtracking does.
Topics
Community Discussion
No community discussion yet for this question.