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 runs three distinct workloads on Google Cloud Compute Engine:
Which combination of instance configurations and purchasing models should the DevOps engineer implement to minimize total infrastructure costs while maintaining reliability?
This strategy combines custom machine types, resource-based Committed Use Discounts (CUDs), stateless Managed Instance Groups (MIGs) with autoscaling, and Spot VMs to align infrastructure purchase models precisely with workload profiles and utilization metrics.
n1-standard or n2-standard) enforce standard resource ratios of 1 vCPU to 4 GB RAM. For a workload requiring 24 vCPUs and 48 GB RAM (1:2 ratio), predefined sizing would force provisioning a standard 24 vCPU / 96 GB RAM instance or an oversized machine, creating 48 GB of unutilized, paid RAM. Provisioning a custom machine type aligns allocation directly to the 1:2 ratio. Backing this steady-state baseline with a 1-year or 3-year resource-based Committed Use Discount cuts baseline compute costs by up to 55% without incurring waste.This architecture adheres to core FinOps principles by pairing predictable, non-standard footprints with custom sizing and commitments, while utilizing elasticity and deeply discounted preemptible capacity where architectural fault tolerance permits.
This option applies standard memory-optimized machine types (m1 series) backed uniformly by a 3-year spend-based Committed Use Discount across all three application tiers.
All three application tiers consisted of massive, predictable, steady-state in-memory databases with extreme memory demands exceeding general-purpose specifications.
This option standardizes all workloads onto a single predefined machine type (n2-standard-32), relies exclusively on sustained use discounts (SUDs), and disables horizontal autoscaling across the fleet.
n2-standard-32 instance provides 32 vCPUs and 128 GB of RAM. For the backend workload needing 24 vCPUs and 48 GB RAM, this results in significant over-provisioning (8 unused vCPUs and 80 GB of unused memory). Custom machine types would eliminate this excess footprint.The organization had zero capability to forecast compute usage beyond a single billing cycle, prohibited contractual term commitments, and required identical hardware images across all hosts regardless of utilization.
This configuration deploys both the mission-critical backend service and the batch processing pipeline on Spot VMs, while purchasing resource-based CUDs sized for peak autoscaling capacity on the frontend.
The backend service were fully stateless, distributed, and completely tolerant of frequent and simultaneous node preemptions, and if frontend traffic remained completely flat 24/7 at peak levels.
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