Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A financial data enterprise runs an OLTP database on Cloud SQL Enterprise Plus with high availability (HA) enabled in its primary region. To meet regulatory compliance, the architecture requires cross-region disaster recovery (DR) capabilities with minimal impact on production write latency during normal operations, routine zero-data-loss DR drill testing, and automated routing via a DNS write endpoint.
Which replication and failover topology should the data engineering team configure?
This option describes standard legacy disaster recovery: manually detaching a cross-region read replica to promote it to a standalone primary database, then executing custom manual scripts to reconstruct replication topologies.
The database instance were running on Cloud SQL Enterprise edition (which lacks Advanced DR) and the business only planned to promote secondary instances during catastrophic permanent region loss without requirement for fast fallback.
This option proposes extending Cloud SQL regional high availability (HA) synchronously across distinct geographic Google Cloud regions to eliminate data loss during failover testing.
The workload required sub-minute zone-level automated failover within a single cloud region with zero data loss (RPO = 0) and could tolerate standard intra-region network latency.
In Cloud SQL Enterprise Plus, advanced disaster recovery relies on designating a cross-region read replica as a designated disaster recovery (DR) replica (configured with the cascadable-replica flag). This architecture uses asynchronous replication across regions to decouple cross-region network latency from production transactions while supporting seamless switchover and failover workflows.
This configuration balances low write latency during everyday operations with strict RPO compliance during planned maintenance and drill testing, while offering rapid RTO during actual regional failure events.
This option attempts to run concurrent active-active primary Cloud SQL instances across two regions and synchronize their write states using continuous bi-directional Change Data Capture (CDC).
The workload was being migrated between heterogeneous database engines or platforms where dual writes and gradual cutover with reverse replication were needed for migration safety.
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