You support a production service that runs on a single Compute Engine instance. You regularly need to spend time on recreating the service by deleting the crashing instance and creating a new instance

Question

Options

• AFile a bug with the development team so they can find the root cause of the crashing instance.
• BCreate a Managed instance Group with a single instance and use health checks to determine the
• CAdd a Load Balancer in front of the Compute Engine instance and use health checks to determine
• DCreate a Stackdriver Monitoring dashboard with SMS alerts to be able to start recreating the

• A
  16% (4)
• B
  72% (18)
• C
  8% (2)
• D
  4% (1)

Explanation

A Managed Instance Group (MIG) with health checks automates exactly this recovery workflow. When a health check detects that the instance is unhealthy, the MIG automatically deletes it and recreates a new instance from the configured instance template-eliminating the manual steps entirely. This aligns with the SRE principle of eliminating toil through automation. Option A (filing a bug) is a valid long-term action but does not reduce the immediate manual toil. Option C (adding a Load Balancer) can route traffic away from an unhealthy instance but a single standalone LB does not recreate the instance automatically. Option D (Monitoring with SMS alerts) still requires a human to perform the recreation, so it does not eliminate toil.

No community discussion yet for this question.