Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An operations team manages a production Cloud SQL instance supporting a critical web service. At 2:15 PM, an operator accidentally runs a query that corrupts table data. The team needs to restore the database state to 2:14 PM—one minute prior to the corruption—with minimal data loss.
Automated daily backups run every midnight.
Which strategy should the team implement to restore the database to the specified timestamp?
Promoting a read replica converts an asynchronous read-only database replica into an independent, read-write primary instance. It is primarily used during regional failovers, database migrations, or for testing.
The primary database suffered a catastrophic hardware or zone outage and the goal was to achieve quick failover to an uncorrupted secondary replica.
Restoring from an automated backup rolls the database state back to the exact moment that specific snapshot was taken—in this case, midnight (00:00 AM).
The goal was simply to revert the database to the start of the business day, or if transaction logging had been disabled and the midnight snapshot was the only existing recovery point.
Point-in-Time Recovery (PITR) is a database recovery feature that allows administrators to restore an instance to an exact target time, down to the second. It relies on a combination of regular database backups and continuous transaction logs (such as binary logs in MySQL or write-ahead logs in PostgreSQL) to replay changes up to the specified moment.

PITR is the only native mechanism designed to recover from intra-day human error without forfeiting hours of intermediate data modifications. Restoring a standard snapshot or midnight backup causes massive data loss, whereas PITR restores exact database state up to the second before failure.
Exporting database schemas captures table definitions (DDL) to Cloud Storage, and repair scripts attempt to reconstruct lost data or fix broken indexes directly in place.
The table structure itself were corrupted at the storage layer and needed recreation from DDL scripts without restoring historical transaction data.
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