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.
A DevOps team manages a large-scale, fault-tolerant data processing workload on Google Cloud. The team uses Spot Virtual Machines (VMs) to maximize FinOps cost efficiency over standard on-demand compute rates. However, regional capacity shifts in spare compute resources occasionally lead to high preemption spikes when the workload is pinned to a single machine type (n2-standard-16). The team needs to configure a regional Managed Instance Group (MIG) that leverages multiple machine families (c3-standard-16, n2-standard-16, and c2-standard-16) while minimizing workload disruption from preemptions.
How should the DevOps team configure the regional Managed Instance Group to achieve the lowest preemption rate across these machine types?
This option suggests using an ANY_SINGLE_ZONE distribution shape alongside Committed Use Discount (CUD) reservations with the goal of preventing preemption on Spot VMs.
ANY_SINGLE_ZONE shape restricts instances to a single zone that satisfies machine selection, increasing vulnerability to localized hardware shortages rather than distributing risk across the region.The organization was deploying mission-critical, stateful workloads using standard on-demand VMs and required guaranteed zonal capacity allocations backed by 1-year or 3-year financial commitments.
Instance flexibility in Managed Instance Groups (MIGs) allows administrators to specify multiple machine types and machine families (such as c3-standard-16, n2-standard-16, and c2-standard-16) within an instanceFlexibilityPolicy. When configured with Spot VMs, Compute Engine actively evaluates resource availability and preemption trends across spare compute capacity.
BALANCED or ANY_SINGLE_ZONE target distribution shapes across regional zones.Instance flexibility with native Spot VM awareness provides an automated, out-of-the-box mechanism that directly monitors and adapts to real-time preemption frequencies, delivering maximum reliability for fault-tolerant Spot workloads.
This option suggests creating separate zonal Managed Instance Groups for each individual machine type and building custom Cloud Scheduler and Cloud Functions workflows to migrate instances based on hourly on-demand pricing differentials.
BALANCED) and automated instance repairs across alternative machine types.The cloud provider utilized dynamic hourly spot auction bidding where workloads needed custom cost-arbitrage bots to track real-time price changes.
This option proposes using Cloud Dataproc secondary worker groups and dynamically adjusting the ratio between Spot VMs and non-preemptible standard VMs throughout the day to avoid preemption spikes.
The workload was specifically an Apache Spark or Hadoop big-data job, and the initial cluster architecture was designed with a fixed, immutable ratio of preemptible secondary workers.
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