Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise organization runs a mission-critical transactional application on a Google Cloud SQL instance. At 14:15 UTC, an administrator accidentally executes an erroneous batch update script that corrupts several production tables.
The database has daily automated backups configured at 02:00 UTC, and Point-in-Time Recovery (PITR) with continuous transaction logging is enabled. The technical recovery team establishes an objective to restore the database to its exact valid state at 14:14 UTC with minimal data loss (lowest possible RPO).
Which recovery procedure should the cloud architect execute?
This option attempts to perform an in-place temporal restore directly onto the existing, running Cloud SQL instance using command-line administration tools.
In Google Cloud SQL, point-in-time recovery cannot be performed in-place on an existing instance. The platform architecture mandates that a PITR operation always creates a new clone instance. Attempting to execute a PITR command targeting the existing instance name directly as the destination will result in an operation error.
Cloud SQL supported in-place rollback to arbitrary log coordinates on live instances, but managed Cloud SQL deliberately separates PITR into new instance provisioning to preserve data safety and auditing integrity.
To restore production while preserving existing DNS endpoints or names, administrators must provision the PITR clone under a temporary name, verify the data, delete or rename the damaged instance, and rename or repoint the application to the recovered instance.
Point-in-time recovery (PITR) is a continuous data protection mechanism in Cloud SQL that enables you to restore a database instance to an arbitrary historical second within your retention window. PITR leverages a combination of base automated backups and continuous transaction logs (such as binary logs for MySQL or write-ahead logs for PostgreSQL) to reconstruct the database state prior to an incident.
14:14 UTC (one minute prior to the corrupting script execution), Cloud SQL restores the base backup taken at 02:00 UTC and replays all committed transaction logs up to 14:14 UTC. This avoids losing the 12+ hours of valid business transactions executed between 02:00 UTC and 14:14 UTC.Performing a timestamp-based PITR clone is the standard Google Cloud architecture pattern for recovering from logical data corruption without sacrificing hours of intervening valid database transactions.
This option executes a standard Cloud SQL backup restoration using the most recent daily automated snapshot taken at 02:00 UTC, overwriting the data on the target instance.
Continuous transaction logging (PITR) was disabled, or if the entire instance suffered corruption immediately after 02:00 UTC such that no subsequent valid transactions existed.
This approach uses Cloud SQL serverless export/import mechanisms to dump the existing instance data into Cloud Storage (SQL/CSV/Avro dump), manually parse and edit the file to remove corrupted data, and then re-import the file into the primary database.
You needed to selectively extract an isolated, uncorrupted archival table or single entity for historical auditing without modifying or provisioning database instances.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated