Google Associate Cloud EngineerEnsuring successful operation of a cloud solutionEasy
A company wants to ensure that their critical application running on Compute Engine instances remains highly available by automatically restarting instances that become unresponsive. They need to monitor the application's health and trigger remedial actions without manual intervention. Which feature should be configured on their Managed Instance Group (MIG)?
- AAutohealing policy
- BInstance template
- CAutoscaling policy
- DLoad balancing health checks
Show answer & explanationAnswer & explanation
Correct answer: A. Autohealing policy
Autohealing policies on a Managed Instance Group (MIG) automatically replace or restart instances that fail health checks, ensuring the application remains available and responsive.
Why the other options are wrong
- B. An instance template defines the configuration for new instances in a MIG, but it doesn't provide a mechanism for monitoring and restarting unhealthy instances.
- C. Autoscaling policies adjust the number of instances in a MIG, but they don't primarily deal with the health of individual instances to restart them.
- D. Load balancing health checks are used by load balancers to determine where to send traffic; while related, they don't directly trigger instance restarts within a MIG for autohealing.
MIG Autohealing
A feature of Managed Instance Groups (MIGs) that automatically repairs instances that fail health checks by restarting or recreating them.
- Ensures application availability and resilience.
- Requires defining health checks to monitor instance or application status.
- Works by replacing unhealthy instances with new, healthy ones.
Memory trick: Autoheal for Healthy Apps.