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 organization is optimizing database and application hosting costs in Google Cloud (us-central1) for three workloads with distinct usage patterns:
Which billing and commitment strategy minimizes total cost without sacrificing performance?
This hybrid approach aligns each workload's billing model with its actual runtime predictability and traffic pattern. By combining regional Cloud SQL spend-based committed use discounts (CUDs) for continuous baseline capacity, on-demand pricing for intermittent workloads and bursts, and request-based serverless billing for spiky HTTP traffic, you avoid paying for idle capacity while locking in deep commitment discounts where utilization is guaranteed.
us-central1 and automatically apply to Cloud SQL Enterprise Plus instances. Covering only the 16 vCPUs and 64 GB RAM baseline ensures 100% commitment utilization 24/7.100% - 25% = 75%), making on-demand pricing significantly cheaper than paying an unused hourly commitment fee.Committing strictly to predictable, steady-state capacity while leaving variable, intermittent, and bursty workloads on pay-as-you-go or request-based models maximizes net Total Cost of Ownership (TCO) savings without introducing lock-in penalties for unused hours.
This approach leaves all Cloud SQL databases on standard pay-as-you-go (on-demand) billing while purchasing a 3-year Compute flexible CUD to cover a Cloud Run service configured with request-based billing.
The production database workload were short-lived or highly unpredictable, and the Cloud Run service had a predictable baseline spend using instance-based billing (which qualifies for the 46% 3-year discount).
This strategy attempts to apply Compute Engine resource-based CUDs (commitments to specific quantities of VM vCPUs and memory) and Sustained Use Discounts (SUDs) to managed Cloud SQL databases while using Cloud Run instance-based billing for the API.
The databases were self-managed on eligible Compute Engine VMs (like N2) with the staging server running well above 25% of the month, and the Cloud Run service experienced steady, continuous traffic.
This configuration purchases a Cloud SQL spend-based CUD sized to cover maximum peak demand across both production and staging environments—including non-compute components—while configuring Cloud Run instance-based billing with minimum instances always running.
Both the staging database and seasonal load ran continuously above the 75% monthly utilization threshold, and the Cloud Run API handled steady, high-concurrency traffic or required persistent background processing between requests.
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