An analytics firm processes asynchronous, fault-tolerant batch workloads on Google Cloud. To minimize infrastructure costs, the engineering team decides to deploy the worker nodes on Spot Virtual Machines (VMs) managed by a regional Managed Instance Group (MIG). The architecture must satisfy the following operational requirements: The worker instances must gracefully save intermediate checkpoint data to a central Cloud Storage bucket upon receiving a preemption notice. The checkpoint process must complete within the 30-second termination notification window. The infrastructure must automatically replenish capacity across available zones without manual intervention when instances are preempted. Which strategy should you implement to handle preemption and maintain workload resilience?

Implement a shutdown script or monitor the metadata server for preemption notices to save checkpoint data, and configure the regional Managed Instance Group to automatically recreate preempted instances across zones.: ### What Spot VM Preemption and MIG Resilience Is **Spot VMs** (and preemptible VMs) provide excess compute capacity at significant discounts compared to standard VM instances. However, Compute Engine can reclaim this capacity at any time when resources are needed elsewhere. When preemption occurs, Compute Engine issues a **preemption notification** via the metadata server and sends an **ACPI power-off signal**, providing a 30-second grace period before forcibly terminating the instance. ### How It Meets the Requirements - **Graceful Checkpointing within 30 Seconds**: By implementing a **shutdown script** (via metadata keys such as `shutdown-script`) or having a daemon poll `http://metadata.google.internal/computeMetadata/v1/instance/preempted`, the worker process is immediately notified of impending termination. It can flush state, commit progress, and upload checkpoints to Cloud Storage within the 30-second window. - **Automatic Capacity Replenishment**: A **regional Managed Instance Group (MIG)** maintains target capacity across multiple zones in a region. When a Spot VM is reclaimed, the MIG automatically attempts to launch replacement instances in available zones based on capacity distribution policies. ### Key Advantages and Capabilities - **Cost Efficiency**: Enables substantial savings (60-91% discount) for fault-tolerant and batch processing workloads. - **Automated Lifecycle Management**: Regional MIGs handle self-healing, instance replacement, and dynamic multi-zone capacity balancing without operational overhead. - **Data Integrity**: Cleanly checkpointing state prevents lost computation and ensures replacement instances resume processing seamlessly. - **Proactive Notification**: Polling the instance metadata server or utilizing shutdown scripts ensures guaranteed execution before compute resources are halted. ### Why This Is Optimal Combining automated shutdown handlers with a multi-zone regional MIG provides high availability, cost optimization, and resilience against sudden compute volatility.

StudyCerts

Manage Spot Vm Preemption Resilience Mig | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Manage Spot Vm Preemption Resilience Mig

Section: Compute volatility configuration (spot vs. standard)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An analytics firm processes asynchronous, fault-tolerant batch workloads on Google Cloud. To minimize infrastructure costs, the engineering team decides to deploy the worker nodes on Spot Virtual Machines (VMs) managed by a regional Managed Instance Group (MIG).

The architecture must satisfy the following operational requirements:

The worker instances must gracefully save intermediate checkpoint data to a central Cloud Storage bucket upon receiving a preemption notice.
The checkpoint process must complete within the 30-second termination notification window.
The infrastructure must automatically replenish capacity across available zones without manual intervention when instances are preempted.

Which strategy should you implement to handle preemption and maintain workload resilience?

Configure VM instances to reject ACPI shutdown signals, and use an automated Cloud Function to invoke compute.instances.resume on preempted instances.

Enable deletion protection on the VM instances, and configure a startup script to capture checkpoint data when receiving a diagnostic interrupt signal.

Deploy the instances in a single-zone unmanaged instance group, and set the instance scheduling policy to live migrate during host maintenance events.

Implement a shutdown script or monitor the metadata server for preemption notices to save checkpoint data, and configure the regional Managed Instance Group to automatically recreate preempted instances across zones.

Professional Cloud Architect

Manage Spot Vm Preemption Resilience Mig

Related questions