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 is deploying a mission-critical relational database on Google Cloud using Cloud SQL for MySQL. The database design must meet the following disaster recovery and availability requirements:
Which database architecture should you implement?
This approach relies on standard single-zone database hosting combined with periodic automated database dumps or disk snapshots stored in Cloud Storage. In the event of a failure, a new instance is created and populated from the last available backup.
The workload was a non-critical development or batch-processing environment where several hours of data loss and downtime were acceptable in exchange for lower infrastructure costs.
Cloud SQL High Availability (HA) uses synchronous data replication across two zones within the same region (a primary instance and a standby instance). A cross-region read replica replicates data asynchronously from the primary instance to a distinct secondary Google Cloud region, where it serves read traffic during normal operations and can be manually or programmatically promoted to a standalone read-write primary database during a catastrophic regional disaster.
This architecture pairs synchronous zonal replication for continuous high availability with asynchronous cross-region replication for disaster recovery, perfectly balancing performance, cost, and stringent RTO/RPO objectives.
An external replica setup configures a non-Google Cloud MySQL instance (such as a server in an on-premises data center) to replicate changes from a primary Cloud SQL instance using standard MySQL binary logging (binlog) and Global Transaction Identifiers (GTID).
The primary business requirement was hybrid data migration or maintaining a synchronized reporting replica inside an existing private corporate data center.
Application-level dual writing is a pattern where application services directly execute identical SQL insert, update, and delete statements against two independent, unlinked database instances simultaneously across different regions.
The application tier utilized a globally distributed consensus database engine like Cloud Spanner, which natively handles multi-region synchronous writes and consistency guarantees automatically.
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