Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company runs a mission-critical database on AlloyDB for PostgreSQL in us-central1 with a customer-managed encryption key (CMEK) configured for backups. To establish cross-region disaster recovery (DR) in us-east1, the team must satisfy the following requirements:
Which configuration and DR protocol should the team implement?
Synchronous replication requires the primary database to wait until a secondary replica confirms receipt of every transaction before committing to the client. Switchover is a controlled, planned role-reversal operation that coordinates between healthy primary and secondary clusters to achieve zero data loss.
us-central1 to us-east1) introduces significant network round-trip latency on every write transaction, severely degrading primary cluster performance.The requirement were intraregional high availability across nearby zones where synchronous writes incur minimal latency and the primary cluster remains reachable for coordinated maintenance.
A backup-and-restore approach (often called a no standby model) avoids running standby compute or storage resources in the secondary region. Instead, periodic full and incremental backups are stored in durable multi-region storage and used to provision a brand-new cluster only when a disaster or drill occurs.
The company ran a non-critical development or archival workload with a strict cost-minimization mandate and could tolerate hours of RTO and a non-zero RPO.
Persistent Disk Asynchronous Replication provides infrastructure-level, block-based asynchronous storage replication between primary and secondary disks in two regions within the same continent. Consistency groups align replication or cloning points across multiple disks attached to a workload.
us-east1, validating the database, and updating network routing. Furthermore, restarting replication later requires creating brand-new blank secondary disks rather than automatically recreating the topology.The workload were a legacy self-managed database or stateful application running on Compute Engine VMs that needed storage-level DR with a roughly one-minute RPO tolerance.
AlloyDB cross-region replication uses an asynchronously replicated secondary cluster in a separate Google Cloud region to protect workloads against regional outages. It provides two distinct role-reversal mechanisms tailored to different scenarios: switchover for planned operations and cross-region failover for unplanned disasters.
us-central1 commits transactions locally without waiting for cross-continental network acknowledgments from us-east1.us-central1 recovers, the team can use a zero-data-loss switchover to fail back.This approach pairs asynchronous cross-region replication for normal performance with the exact managed AlloyDB operations designed for planned zero-loss drills (switchover) and automated topology recovery (cross-region failover).
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