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 a suite of steady-state microservices on Google Compute Engine virtual machines (n2-standard-8 machine types with 8 vCPUs and 32 GB memory each) across a single region. The workloads run continuously 24/7 with predictable demand.
Cloud Monitoring telemetry shows that across all instances, actual average CPU utilization remains steady at 25% to 30%, while memory utilization remains consistently high at approximately 24 GB. The infrastructure team wants to eliminate resource over-provisioning and secure the highest possible continuous cost reductions over a 3-year commitment period.
Which combination of actions should the DevOps engineer implement to optimize workload efficiency and ongoing costs?
n2-standard-8 profile and purchase a 1-year flexible Committed Use Discount to cover the Spot capacity.Spot VMs are surplus Compute Engine instances available at substantial discounts (60%–91%) that Google Cloud can preempt and terminate with a 30-second warning whenever it requires the capacity back. Flexible Committed Use Discounts are spend-based commitments that apply across multiple Compute Engine machine families and regions.
The workloads were non-critical, fault-tolerant batch worker tasks that could be interrupted at any moment without impacting customer transactions.
Attempting to combine CUD commitments with Spot instances results in paying twice: paying the discounted Spot rate while leaving the purchased CUD commitment unused and wasted on the billing invoice.
Custom machine types allow you to tailor the exact number of vCPUs and amount of system memory for Compute Engine instances rather than being locked into predefined, fixed ratios (like the standard 1:4 vCPU-to-RAM ratio in n2-standard types). Resource-based Committed Use Discounts (CUDs) provide substantial cost savings (up to 55%–70% depending on machine family and term length) in exchange for committing to a minimum continuous usage of compute resources (vCPUs and memory) in a specific region for a 1-year or 3-year term.
4 vCPUs and 24 GB memory) prevents paying for 4 unneeded vCPUs that were bundled in the n2-standard-8 instance.Right-sizing the hardware configuration directly reduces the baseline resource footprint, and layering a 3-year resource-based CUD on top of that right-sized footprint yields the maximum cumulative cost reduction without risking memory starvation or performance degradation.
n2-standard-8 machine types to maximize Sustained Use Discounts (SUDs) across the billing account, and rely on automated disk snapshot schedules to reduce storage overhead.Sustained Use Discounts (SUDs) are automatic discounts applied by Google Cloud when specific Compute Engine instances run for more than 25% of a billing month. They do not require an upfront contractual commitment and scale up incrementally as instance uptime increases throughout the month.
n2-standard-8 instances leaves 4 to 5 vCPUs idle and unutilized 100% of the time, resulting in massive wasted spend despite any applied discounts.The workload was unpredictable, expected to be decommissioned in less than a year, and the organization strictly prohibited long-term contractual spending commitments.
In FinOps maturity models, relying solely on unmanaged SUDs for steady-state 24/7 enterprise production workloads represents a low-maturity practice compared to deliberate right-sizing combined with active CUD management.
e2-standard-2 machine types and enable extreme persistent disks (pd-extreme) to offload memory paging to high-IOPS storage.E2 machine types are cost-optimized virtual machines that use dynamic resource management and shared host architectures. Extreme Persistent Disks (pd-extreme) are ultra-high-performance block storage volumes designed for mission-critical database workloads requiring high IOPS and high throughput.
e2-standard-2 instance provides only 8 GB of memory. Relying on disk paging (swap space) for active in-memory working sets introduces massive latency penalties and risk of Linux OOM killer termination.pd-extreme storage introduces expensive storage provisioning costs that completely negate any compute-level savings achieved by shrinking the VM.e2-standard-2 Specs: Provides 2 vCPUs and only 8 GB memory.pd-extreme Constraints: Intended for specialized high-transaction I/O engines, requiring minimum vCPU counts and incurring premium per-GB and per-provisioned-IOPS billing.The workload was an I/O-intensive caching proxy with negligible RAM requirements and massive disk throughput demands.
Disk swap is not an acceptable architectural replacement for application heap and operational RAM in high-throughput cloud environments.
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