You are running a Cloud SQL for PostgreSQL 13 Enterprise Edition instance. During an audit, you discovered that the write-ahead logs used for point-in-time recovery (PITR) are stored on disk. You…

Question

Options

• AClone the instance. Create a new instance with PITR retention set to 30 days.
• BChange the transaction logs (WAL) retention period.
• CUpgrade to Enterprise Plus Edition.
• DDisable PITR, then enable PITR.

• A
  10% (2)
• B
  5% (1)
• C
  86% (18)

Explanation

Upgrading to Cloud SQL Enterprise Plus Edition is the correct answer because Enterprise Plus is the only Cloud SQL tier that stores point-in-time recovery (PITR) write-ahead logs (WAL) in a Cloud Storage bucket rather than on the instance's attached disk. This directly addresses the requirement of moving WAL storage to Cloud Storage without disrupting the existing PITR capability or losing existing logs - the upgrade path preserves continuity. Cloning the instance (A) would create a new instance but the WAL/PITR logs from the original instance would not carry over to the clone, compromising recoverability. Simply changing the WAL retention period (B) only adjusts how long logs are kept, not where they are stored. Disabling and re-enabling PITR (D) would delete all existing WAL logs during the disable step, causing a gap in the version timeline and violating the requirement to not lose current PITR logs.

No community discussion yet for this question.