Your organization deployed a new version of a critical application that uses Cloud SQL for MySQL with high availability (HA) and binary logging enabled to store transactional information. The latest…

Question

Options

• AOpen the Google Cloud Console, navigate to SQL > Backups, and select the last version of the
• BReload the Cloud SQL for MySQL database using the LOAD DATA command to load data from
• CPerform a point-in-time recovery of your Cloud SQL for MySQL database, selecting a date and
• DFail over to the Cloud SQL for MySQL HA instance. Use that instance to recover the transactions

• A
  11% (3)
• B
  7% (2)
• C
  79% (22)
• D
  4% (1)

Explanation

Point-in-time recovery (PITR) is the correct approach because it allows you to restore the database to a specific timestamp immediately before the corruption occurred. PITR works by replaying binary logs (which are confirmed to be enabled in this scenario) from the last automated backup to the chosen recovery point, minimizing data loss to near zero. Restoring from a regular backup (A) would lose all data written since that backup was taken. LOAD DATA (B) is a data import command, not a recovery mechanism. Failing over to the HA instance (D) would not help because the HA standby continuously replicates all changes from the primary - it already contains the corrupted data.

No community discussion yet for this question.