You are running a transactional application on Cloud SQL for PostgreSQL in Google Cloud. The database is running in a high availability configuration within one region. You have encountered issues wit

Question

Options

• ACreate a clone database from a read replica database, and restore the clone in the same region.
• BCreate a clone database from a read replica database, and restore the clone into a different zone.
• CUse the Cloud SQL point-in-time recovery (PITR) feature. Restore the copy from two hours ago to
• DUse the Cloud SQL database import feature. Import last week's dump file from Cloud Storage.

• A
  18% (9)
• B
  4% (2)
• C
  71% (36)
• D
  8% (4)

Explanation

Cloud SQL Point-in-Time Recovery (PITR) lets you restore a database to any specific moment within the configured log retention window, making it ideal for recovering from data corruption or accidental changes. Restoring from two hours ago gives you the last known clean state without the data loss risk of using last week's dump. Option A and B (clone from read replica) would propagate the corrupted data because read replicas are continuously synchronized with the primary. Option D (import from a week-old dump file) causes significant data loss-you would lose an entire week of transactions. PITR is the most precise and least destructive recovery method available.

No community discussion yet for this question.