Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A retail organization hosts its production environment on Google Cloud. The environment includes a Cloud SQL relational database storing customer transactions and a Cloud Storage bucket storing product media files and receipt documents.
The database administrator needs to implement a recovery strategy that fulfills two specific requirements:
Which combination of recovery mechanisms should the organization implement?
This option combines Cloud SQL High Availability (HA), which provides regional data redundancy with automated failover to a standby instance in a different zone, with Customer-Managed Encryption Keys (CMEK), which enables customer control over encryption keys stored in Cloud KMS.
UPDATE or DELETE query runs on the primary instance, the change is synchronously replicated to the standby instance immediately.The scenario required protecting the database against sudden zonal hardware outages with minimal failover downtime while enforcing enterprise encryption compliance via customer-managed keys.
This solution pairs Cloud SQL Point-in-Time Recovery (PITR)—supported by write-ahead/transaction logging and automated backups—with Cloud Storage Object Versioning to protect structured relational data and unstructured object data against accidental loss or modification.
Point-in-time recovery is the only native Cloud SQL mechanism capable of restoring to an arbitrary minute before a human error or data corruption event. Similarly, Object Versioning is the standard Cloud Storage feature designed specifically to preserve and restore overwritten versions of objects without having to restore entire storage systems.
This option proposes executing periodic database exports (SQL dump files) from Cloud SQL into a Cloud Storage bucket, alongside deploying a Dual-Region bucket configuration for geographic object redundancy.
The organization needed to extract specific tables into portable .sql files for offline auditing and required geo-redundant bucket availability during a regional cloud outage.
This option relies on taking manual on-demand backups or final backups for Cloud SQL before deleting an instance, coupled with Object Lifecycle Management rules in Cloud Storage to automate object actions.
The team needed an ad-hoc snapshot before decommissioning a Cloud SQL instance and wanted to automatically purge Cloud Storage objects older than 365 days to reduce storage costs.
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