You want to configure autohealing for network load balancing for a group of Compute Engine instances that run in multiple zones, using the fewest possible steps.
You need to configure re-creation of VMs if they are unresponsive after 3 attempts of 10 seconds each.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The correct answer is option C, "Create a managed instance group. Set the Autohealing health check to healthy (HTTP)".
Here's why:
Autohealing is a feature that automatically replaces instances that fail health checks. To use autohealing with a network load balancer for a group of Compute Engine instances that run in multiple zones, you can create a managed instance group and configure the Autohealing feature to use an HTTP health check.
A managed instance group is a collection of homogeneous instances that are managed as a single entity. It allows you to automatically create and manage groups of virtual machine instances in a Google Cloud environment. You can configure the group to automatically scale the number of instances up or down based on demand, and the group can also automatically replace instances that fail health checks.
To configure autohealing for a managed instance group, follow these steps:
Create a managed instance group that contains the Compute Engine instances that you want to use with the network load balancer.
Configure an HTTP health check for the instance group that checks if the instances are responsive. The health check should attempt to connect to each instance and verify that it returns an HTTP status code of 200 or 3xx within a certain time limit. In this case, the health check should make 3 attempts, each with a timeout of 10 seconds.
Enable the Autohealing feature for the instance group and configure it to use the HTTP health check that you created in step 2. When an instance fails the health check, the instance group will automatically create a new instance to replace it.
Option A, "Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)", is not the best answer because it doesn't use a managed instance group, which is a more powerful and flexible tool for managing groups of Compute Engine instances.
Option B, "Create an HTTP load balancer with a backend configuration that references an existing instance group. Define a balancing mode and set the maximum RPS to 10", is not the best answer because it doesn't configure autohealing or use a managed instance group.
Option D, "Create a managed instance group. Verify that the autoscaling setting is on", is not the best answer because it doesn't configure autohealing or an HTTP health check, which are necessary for the network load balancer to detect and replace unresponsive instances.