Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise organization operates multiple Google Cloud projects attached to a single Cloud Billing account. The infrastructure architecture includes the following workload profiles:
us-central1).As a DevOps and FinOps engineer, you need to implement a commitment strategy that maximizes cost savings for the predictable baseline, provides flexible coverage for dynamic multi-service compute spend, and prevents commitment underutilization across projects.
Which strategy should you implement?
Sustained Use Discounts (SUDs) are automatic discounts applied to Compute Engine instances that run for a significant portion of a billing month (e.g., more than 25% of the month). They require no upfront commitment or contract signature and accrue incrementally as continuous runtime increases.
The organization had completely unpredictable, short-term project lifecycles under 30 days where long-term capacity planning is impossible and zero financial commitment is required.
This approach purchases resource-based CUDs tied directly to specific Google Cloud projects without enabling billing-level discount sharing. It sizes the commitment to cover the highest anticipated peak load rather than baseline utilization.
A single project had static, unyielding 24/7 peak load that never fluctuated, and regulatory or legal boundaries strictly prohibited cross-subsidizing discounts with other business units.
Resource-based Committed Use Discounts (CUDs) provide the deepest discounts (up to 55–70%) in exchange for committing to a specific amount of vCPUs, memory, GPUs, or local SSDs in a single region and specific machine series. Spend-based (Flexible) CUDs offer a predictable dollar-per-hour discount across multiple compute services (including Compute Engine, Google Kubernetes Engine, and Cloud Run) regardless of machine series or region. Discount sharing at the Cloud Billing account level aggregates eligible usage across all linked projects so commitments apply wherever matching resources run.
us-central1 captures the highest percentage discount for hardware configurations that will not change.Layering rigid resource-based CUDs for well-understood, single-region baselines under flexible spend-based CUDs for containerized/serverless components—backed by centralized billing discount sharing—delivers the optimal balance between maximum percentage discount and low financial risk.
This strategy assigns spend-based (flexible) CUDs to steady-state N2 Compute Engine instances in a single region, while attempting to apply resource-based CUDs to distributed containerized and serverless environments like GKE and Cloud Run.
Resource-based CUDs supported native serverless abstractions and spend-based CUDs yielded higher discount percentages than resource-based commitments.
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