Question

Difficulty: MediumManaging Compute Engine Resources

A cloud operations team is configuring a compute infrastructure on Google Cloud to process stateless, fault-tolerant data transformation tasks. The architecture must minimize compute costs while ensuring high availability and automatic replacement of failed instances. Which TWO management strategies should the team implement? (Select 2 answers)

  1. Configure the Managed Instance Group (MIG) to use Spot VMs for instance provisioning to reduce compute expenses.Answer
  2. Define an HTTP health check and assign an autohealing policy to the Managed Instance Group to automatically recreate unhealthy instances.Answer
  3. C
    Deploy stateful database nodes on Spot VMs within the group to minimize database hosting costs.
  4. D
    Configure MIG autoscaling based on OS memory utilization metrics using standard Cloud Monitoring without installing the Google Cloud Ops Agent.
  5. E
    Assign the primitive Owner role to the VM service account so instances can automatically issue API calls to increase regional CPU quota when workload demand spikes.

Answer

The correct strategies are to configure the Managed Instance Group to use Spot VMs for stateless processing and to configure an autohealing policy with an HTTP health check to recreate degraded instances.
For stateless, fault-tolerant batch workloads, using Spot VMs within a Managed Instance Group delivers maximum cost savings. Pairing the MIG with an HTTP health check and an autohealing policy ensures high availability because any instance that becomes unresponsive or fails its health check is automatically terminated and recreated.

Step-by-Step Solution

1
Identify cost optimization mechanisms appropriate for stateless workloads
Spot VMs provide significant cost reductions for fault-tolerant and stateless workloads that handle preemptions gracefully.
Stateless batch transformations do not store local persistent state, so unexpected preemptions by Compute Engine will not degrade data integrity.
2
Identify health monitoring and auto-recovery configurations for Compute Engine MIGs
Attaching an explicit HTTP health check to the MIG autohealing policy ensures automatic instance recreation upon application freeze or crash.
Autohealing continuously monitors application endpoints and replaces failed VM instances automatically.

Key Concept

Compute Engine Resource Management: Managed Instance Groups (MIGs), Spot VM placement, and Autohealing Policies
Rate this question