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 organization runs fault-tolerant batch data processing and CI/CD build tasks on Google Cloud Compute Engine. The DevOps team needs to optimize compute expenses using Spot VMs while satisfying the following operational criteria:
Which configuration strategy should the DevOps team implement?
This option suggests using the Flex-start provisioning model within a stateful Managed Instance Group and relying on an internal in-guest cron job to poll Compute Engine metadata for preemption signals.
The scenario required guaranteed short-term allocation of specialized GPU machine types for small model fine-tuning or simulations where interruptions cannot be tolerated.
This configuration attempts to configure an instance template using the Spot VM provisioning model while simultaneously enabling automatic restart (automatic_restart = true) and live migration (on_host_maintenance = "MIGRATE") availability policies.
provisioningModel: SPOT alongside live migration policies results in an API validation error.automaticRestart = false and onHostMaintenance = TERMINATE.The workload was running on Standard on-demand VMs where high availability across host maintenance infrastructure events is required and live migration is fully supported.
This option proposes provisioning Standard on-demand instances in an unmanaged instance group, using Cloud Scheduler to pause/suspend VMs, and executing external deployment scripts to change their provisioning model to Spot dynamically.
STANDARD vs. SPOT) is immutable; a running or stopped VM cannot be dynamically converted to a Spot VM without deleting and recreating it.The environment required load balancing across existing, differently configured legacy VMs that could not be standardized into an instance template.
Spot Virtual Machines (VMs) provide excess Compute Engine capacity at discounts of up to 60–91% compared to standard on-demand pricing. Managed Instance Groups (MIGs) manage pools of homogeneous VM instances created from a shared instance template, providing automated lifecycle management, autohealing, and scaling capabilities.
provisioningModel: SPOT (or --provisioning-model=SPOT) in the instance template configures all provisioned worker nodes as Spot VMs, maximizing cost efficiency for batch computing.Combining Spot VM provisioning with stateless MIG orchestration and shutdown script checkpointing delivers the ideal balance between high fault tolerance, automated recovery, platform compliance, and optimal cost reduction.
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