Examkin

Soru

Zorluk: OrtaManaging Storage and Database Solutions

An operator accidentally deleted a critical customer table from a production Cloud SQL for PostgreSQL instance at 14:15 UTC. Automated daily backups and transaction logging (point-in-time recovery) are enabled on the instance. You must restore the database to a new instance to recover the missing data and resume normal operations. Sequence the correct order of steps to complete this recovery process.

  1. 1Identify the exact UTC timestamp immediately preceding the accidental table deletion from Cloud Audit Logs or database logs.
  2. 2Run the point-in-time restore command specifying the source instance, a new target instance name, and the selected timestamp.
  3. 3Connect to the newly created target Cloud SQL instance to verify table schema and data integrity.
  4. 4Update the application connection settings or Secret Manager configuration to direct database traffic to the new instance.

Cevap

The correct operational sequence is: 1) Identify the exact timestamp prior to deletion, 2) Execute the point-in-time restore to a new Cloud SQL instance, 3) Verify data integrity on the restored instance, and 4) Update application connection parameters to point to the new instance.
The proper administrative workflow begins by determining the target timestamp immediately prior to data corruption. Next, a point-in-time restoration is executed targeting a new instance. Once provisioned, the database contents are validated for completeness, and finally the application connection parameters are updated to route traffic to the restored instance.

Adım Adım Çözüm

1
Locate the precise restore target timestamp.
Obtained a timestamp (e.g., 14:14 UTC) immediately prior to the table drop event.
Restoring to a timestamp after the drop event would still result in missing data.
2
Provision and populate a new Cloud SQL instance using point-in-time recovery.
A new Cloud SQL instance is created containing the state of the database up to the designated timestamp.
Cloud SQL PITR requires specifying a target instance to prevent accidental overwrites of live production instances.
3
Inspect the restored database instance.
Confirmed that the deleted table exists and all data is present and uncorrupted.
Operational best practices require verification before switching application connections.
4
Reconfigure application connection endpoints.
Application workloads now communicate with the newly verified Cloud SQL instance.
Updating connection strings or Secret Manager references directs live traffic to the recovered instance.

Anahtar Kavram

Cloud SQL Point-in-Time Recovery (PITR) and Instance Management
Bu soruyu puanla

Konular

Managing Storage and Database Solutions