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.
Your e-commerce company is migrating its core order and catalog database to AlloyDB for PostgreSQL in us-central1. Current workload metrics show steady baseline usage, but you must finalize a long-term sizing model that accounts for the following requirements:
us-east4 for regional outages.Which sizing and capacity planning strategy should you implement?
Proactive capacity planning for AlloyDB for PostgreSQL combines rightsized baseline compute, regional high availability (HA), schedule-based read pool autoscaling, and an appropriately sized cross-region disaster recovery (DR) secondary cluster. Instead of sizing solely for today's steady state, this model builds anticipated growth, predictable traffic bursts, and failover overhead directly into the database architecture.
us-east4 sized with full production vCPU and memory capacity ensures you can switch over immediately without needing an emergency scaling operation.N2, C4A, C4, or Z3) independently of the primary instance.This strategy balances performance, cost, and resilience across every layer of the sizing model. Unlike reactive-only scaling, vertical-only sizing, or undersized standby clusters, it guarantees capacity for both predictable peaks and regional failovers while keeping normal operating costs aligned with actual baseline demand.
Compute Engine reservations assure VM capacity for self-managed Compute Engine instances in a specific zone, while deploying a secondary cluster in a different zone within the same region (us-central1) provides only zonal redundancy rather than geographic isolation.
us-central1 only protects against a zonal failure. If an entire region becomes unavailable, both clusters are affected, failing the regional DR requirement for us-east4.us-east4.You were managing self-hosted PostgreSQL databases on Compute Engine VMs where zonal VM reservations apply and your availability requirements only covered single-zone failures.
Understanding the boundary between Google-managed tenant infrastructure and customer-managed Compute Engine resources is essential for AlloyDB sizing, as is distinguishing intra-region HA from cross-region DR.
Vertical scaling (scaling up) increases the CPU and memory of a single database instance rather than adding horizontal read nodes. Pairing a single-zone instance with cross-region backups in Cloud Storage represents a cold standby recovery pattern with no active redundant compute.
The system was a development, testing, or archival workload with strict cost constraints, low availability expectations, and an acceptable RTO of several hours or days.
Modern cloud database architectures separate horizontal read scaling (using elastic read pools) from HA/DR replication so that seasonal read surges do not force expensive, permanent vertical upgrades on the primary node.
This approach sizes the database exclusively for present-day baseline traffic, relies on reactive autoscaling triggered only after utilization thresholds are breached, and provisions a minimal standby cluster in the DR region to lower ongoing compute expenses.
us-east4 cannot immediately serve full e-commerce production traffic upon switchover. Attempting to scale up the secondary instance during a regional outage risks running into resource contention in the target region.The workload was a non-critical internal application with flat year-over-year usage, unpredictable but gradual traffic changes, and a high Recovery Time Objective (RTO) where spending extra time scaling up the DR cluster after a disaster was acceptable.
For predictable seasonal peaks, schedule-based scaling ahead of the event window is preferred because it validates hardware availability early and allows switching read pools to alternative machine series if needed.
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