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 gaming company runs a latency-sensitive leaderboard service on a 10-node Cloud Bigtable SSD cluster with autoscaling enabled (CPU utilization target of 60%, minimum 4 nodes, maximum 30 nodes). Every Saturday, a scheduled 25-minute tournament triples concurrent read requests, causing severe read latency for most of the event before performance stabilizes.
The engineering team wants to implement a horizontal scaling strategy that meets these requirements:
Which horizontal scaling strategy should the engineering team implement?
A 2x node scaling factor treats two standard Bigtable nodes as a single larger compute unit, scaling in increments of two nodes to reduce compute boundaries, improve tail latency stability, and absorb hotspots. The storage utilization target sets the compressed data threshold per node that triggers storage-based scale-out.
The team were provisioning a brand-new, large SSD cluster for sustained hotspot absorption and configured a storage utilization target below 60% alongside pre-scaled minimum nodes.
Lowering the CPU utilization target instructs Bigtable autoscaling to trigger scale-out operations earlier as load rises, while increasing the maximum number of nodes raises the upper boundary of how far the cluster can grow.
The workload experienced gradual traffic growth over several hours rather than a sudden 25-minute burst, and the minimum node count were also increased to at least 5 to satisfy the 10% minimum requirement.
With manual node allocation, administrators explicitly specify a static number of nodes in a Bigtable cluster rather than allowing Bigtable autoscaling to adjust capacity automatically based on CPU and storage metrics.
The team needed static node control, added the extra nodes at least 20 to 30 minutes before the tournament, and automated a gradual scale-down removing no more than 10% of nodes every 10 minutes.
Bigtable autoscaling dynamically adjusts cluster size based on CPU utilization, storage utilization, and configured minimum and maximum node limits. When you increase the minimum number of nodes on an autoscaled cluster, Bigtable immediately provisions additional nodes up to that new floor and begins tablet rebalancing across the expanded cluster before traffic arrives.
min_nodes can be scheduled cleanly via gcloud CLI or client libraries for recurring weekly events.Reactive autoscaling alone responds too slowly for a short 25-minute burst, while abrupt manual node removal risks severe latency spikes. Raising the minimum number of nodes ahead of a scheduled burst combines predictable peak read performance with automated, gradual, cost-efficient scale-down.
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