SOA-C03 · Question #129
A company runs an application on Amazon EC2 instances. The application stores and retrieves data from an Amazon Aurora PostgreSQL database. A developer accidentally drops a table from the database…
The correct answer is C. Perform a point-in-time recovery and create a new database to restore the database to a. Aurora Backtrack is not supported for Aurora PostgreSQL, so option A is not valid here. Point-in-time recovery (PITR) for Aurora always restores to a new cluster, not in place. You choose a time (e.g., just before the table was dropped, 2 hours ago), Aurora creates a new…
Question
A company runs an application on Amazon EC2 instances. The application stores and retrieves data from an Amazon Aurora PostgreSQL database. A developer accidentally drops a table from the database, which causes application errors. Two hours later, a CloudOps engineer needs to recover the data and make the application function again. Which solution will meet this requirement?
Options
- AUse the Aurora Backtrack feature to rewind the database to a specified time, 2 hours in the past.
- BPerform a point-in-time recovery on the existing database to restore the database to a specified
- CPerform a point-in-time recovery and create a new database to restore the database to a
- DCreate a new Aurora cluster. Choose the Restore data from S3 bucket option. Choose log files up
How the community answered
(38 responses)- A13% (5)
- B5% (2)
- C76% (29)
- D5% (2)
Explanation
Aurora Backtrack is not supported for Aurora PostgreSQL, so option A is not valid here. Point-in-time recovery (PITR) for Aurora always restores to a new cluster, not in place. You choose a time (e.g., just before the table was dropped, 2 hours ago), Aurora creates a new cluster at that state, and you then: - Either point the application to the new cluster endpoint, or - Copy the recovered table/data back to the original cluster.
Topics
Community Discussion
No community discussion yet for this question.