GCP - Cloud SQL and Databases
You have enabled autohealing on a Managed Instance Group, but unhealthy instances remain active. What configuration issue could cause this?
You have enabled autohealing on a Managed Instance Group, but unhealthy instances remain active. What configuration issue could cause this?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Verify Health Check Attachment
Autohealing depends on the health check being correctly linked to the Managed Instance Group. Without this, the group cannot detect unhealthy instances.Step 2: Check Autohealing Policy
Ensure the autohealing policy references the correct health check resource.Final Answer:
The health check is not properly attached to the Managed Instance Group -> Option BQuick Check:
Health check must be linked to autohealing policy [OK]
Quick Trick: Autohealing requires a linked health check [OK]
Common Mistakes:
- Assuming instance template settings affect autohealing
- Believing multi-zone distribution prevents replacement
- Confusing preemptible VM behavior with autohealing
Master "Cloud SQL and Databases" in GCP
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore GCP Quizzes