Examkin

Question

Difficulty: MediumManaging Storage and Database Solutions

A Cloud Engineer needs to perform a Point-in-Time Recovery (PITR) for a Cloud SQL instance after a developer accidentally dropped a critical database table. What is the correct operational sequence of steps to safely restore the database state and transition application traffic to the restored instance?

  1. 1Identify the precise point-in-time timestamp (in UTC) immediately prior to the accidental table drop event.
  2. 2Execute a database clone operation using the target timestamp to restore the data state into a new Cloud SQL instance.
  3. 3Connect to the newly provisioned Cloud SQL instance to inspect and verify database schema and table integrity.
  4. 4Update application configuration connection strings to direct database traffic to the new Cloud SQL instance IP or connection name.

Answer

The correct sequence starts by identifying the exact pre-corruption timestamp, followed by cloning to a new instance at that timestamp, verifying data integrity on the new instance, and finally updating application connection strings to target the restored instance.
Point-in-Time Recovery (PITR) for Cloud SQL requires first determining the exact point in time prior to data loss. Running the recovery/clone command provisions a new Cloud SQL instance containing data up to that specified moment. Best practice requires verifying data and schema integrity on the newly created instance before updating application connection settings to complete the operational cutover.

Step-by-Step Solution

1
Identify the target recovery timestamp
Retrieved the exact UTC timestamp prior to the table drop.
PITR requires a specific timestamp boundary to roll back transactional logs.
2
Restore data to a new Cloud SQL instance using point-in-time cloning
Created a new running Cloud SQL instance with data restored up to the specified moment.
Cloud SQL PITR creates a distinct new target instance, preventing accidental overwrites of existing instance configurations.
3
Perform database integrity checks
Confirmed that the dropped table exists and contains expected records.
Validation ensures the restored instance is complete and healthy prior to cutover.
4
Update application database endpoints
Application traffic is successfully redirected to the restored instance.
Modifying connection settings points application services to the verified database endpoint.

Key Concept

Cloud SQL Point-in-Time Recovery (PITR) Operational Workflow
Estimated Time:1m 30s
Rate this question

Topics

Managing Storage and Database Solutions