Exam Associate Cloud Engineer topic 1 question 4 discussion

C, Agreed reference : https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing Pro Tip: Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users.

A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy(HTTP) This is a possible answer. This answer assumes that the existing backend is configured correctly. 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. This is a possible answer. This answer assumes that the existing backend is configured correctly. This answer adds an additional step over answer A. C. Create a managed instance group. Set the Autohealing health check to healthy(HTTP) This is only a partial solution. The default configuration is auto scaling enabled. You still need to create the HTTP Load Balancer. D. Create a managed instance group. Verify that the auto scaling setting is on. This is only a partial solution. Creating a Managed Instance Group with Auto Scaling is required, but you still need to create the HTTP Load Balancer. Therefore the best answer is A in my opinion.

C, agree with you

C is the only one with the AUTOHEALING option, but it is not really correct. Remember, the GIVEN information are "a NETWORK load balancer and a group of Compute Engine Instances that run in multiple zones" which gives us an idea that the existing configuration is a target pool-based network lb. If we are to use the existing group of VMs, we need to choose UNMANAGED Instance Group, UNMANAGED Instance Group does not have Autohealing, only a health check. Health check only checks if VMs are responsive or not but does not re-create instances as what Autohealing and Autoscaling do. You can also try re-creating the scenario or check this https://cloud.google.com/load-balancing/docs/network/transition-to-backend-services#console So, if a MANAGED INSTANCE group is to be used, then you need to create an instance template and use it for your MIG. Ofc, you cannot use the existing VMs, then you create a new load balancer. Ofc, the existing group of VMs mentioned in the question will no longer be used but rather a new set of VMs based on the instance template will be created. The choices should be updated.

Option C is correct because creating a managed instance group allows you to use autohealing to automatically recreate VMs that are unresponsive after 3 attempts of 10 seconds each. You can set the Autohealing health check to healthy (HTTP) to specify the health check that determines whether the instances are considered healthy or not. If an instance becomes unresponsive, Autohealing will recreate the instance and attach it to the managed instance group. https://cloud.google.com/compute/docs/instance-groups/autohealing-instance-groups

The correct answer is C. Managed instance groups are groups of homogeneous Compute Engine instances that are managed as a single entity. They can be used to distribute traffic across multiple instances and to provide high availability. Autohealing is a feature of managed instance groups that automatically replaces instances that fail health checks. You can configure autohealing to recreate instances if they are unresponsive after a certain number of attempts. To configure autohealing for network load balancing, you need to create a managed instance group and set the Autohealing health check to healthy (HTTP). The health check will periodically probe the instances in the group to see if they are responding. If an instance fails the health check, autohealing will recreate it.

Option C correct C. Create a managed instance group. Set the Autohealing health check to healthy (HTTP) Explanation: * Managed Instance Groups (MIGs) are specifically designed for managing and scaling groups of instances. They offer features like autohealing, load balancing, and autoscaling. * Autohealing is a key feature of MIGs that allows you to automatically recreate unhealthy instances based on health checks. Why other options are incorrect: * A and B involve creating an HTTP load balancer, which is not directly related to autohealing. Load balancers distribute traffic but do not handle instance health checks and recreation. * D only creates a managed instance group and verifies autoscaling, which is not sufficient for autohealing. Autohealing requires a health check configuration. By choosing option C, you directly address the requirements of configuring autohealing for a group of Compute Engine instances with the fewest possible steps.

here we clearly need auto healing capability so C is correct.

C, Agreed Pro Tip: Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users.

A,B,C are regarding http whereas question is about network Lb. So Option D is correct

Correct Answer is D

C is Correct

C is correct.

C is Correct!

C is correct

The answer is C

C is Correct Answer