A company runs an application on Amazon EC2 that connects to an Amazon Aurora PostgreSQL database. A developer accidentally drops a table from the database, causing application errors. Two hours…

Question

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

• A
  3% (1)
• B
  17% (5)
• C
  73% (22)
• D
  7% (2)

Explanation

In the AWS Cloud Operations and Aurora documentation, when data loss occurs due to human error such as dropped tables, Point-in-Time Recovery (PITR) is the recommended method for restoration. PITR creates a new Aurora cluster restored to a specific time before the failure. The restored cluster has a new endpoint that must be reconfigured in the application to resume normal operations. AWS does not support performing PITR directly on an existing production database because that would overwrite current data. Aurora Backtrack (Option A) applies only to Aurora MySQL, not PostgreSQL. Option B is incorrect because PITR cannot be executed in place. Option D refers to an import process from S3, which is unrelated to time-based recovery. Hence, Option C is correct and follows the AWS CloudOps standard recovery pattern for PostgreSQL workloads.

No community discussion yet for this question.