Configure Autohealing for Managed Instance Groups

Planning and implementing compute resources.

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?

Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)
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.
Create a managed instance group. Set the Autohealing health check to healthy (HTTP) Correct Answer
Create a managed instance group. Verify that the autoscaling setting is on.

Answer Correct answer: C — Create a managed instance group and set the Autohealing health check to healthy (HTTP) to enable automatic VM recreation upon failure detection.

Community Insight

The core trap is confusing load balancing health checks (which route traffic away from bad instances) with autohealing health checks (which actually delete and recreate unhealthy instances).

This question tests the distinction between load balancer health checks and managed instance group (MIG) autohealing in Google Cloud. The correct configuration requires setting up an HTTP health check within the MIG to trigger VM recreation, not just traffic routing.

Many learners select Option A because it mentions a health check, but they miss that load balancer health checks do not automatically recreate VMs; they only stop sending traffic to them.

Community Discussion (136 comments)

chamundi 👍 1 Selected: C

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

Vroy123 👍 1 Selected: C

C is the correct answer: • Re-creating VMs = Autohealing. Only Managed Instance Groups (MIGs) have the actual power to delete a frozen or broken VM and spin up a brand-new one to replace it. • Why not Load Balancers (A & B)? Load balancers only ignore broken VMs by routing traffic away from them. They cannot recreate them. • Why not Autoscaling (D)? Autoscaling adds extra VMs when your app gets busy. It does not monitor for or replace unresponsive VMs.

BhawanaV 👍 1 Selected: C

Option C is correct.

kewgard 👍 1 Selected: C

Definately C. this is the only way to create such autohealing. you create an instance group and then you choose the option for autohealing. When you do you can set a url to send a health check to and set a check interval time and timout

toasty 👍 1 Selected: C

C, agree with you

SaiSaiA 👍 2

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.

Buruguduystunstugudunstuy 👍 2 Selected: C

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

Shivangi30 👍 1

The link url is invalid

YourCloudGuru 👍 1

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.

harsh5kalsait 👍 1

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.

ReyBan 👍 98

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.

ashrafh 👍 29

I also vote for C go to gcp console create a httpa load balancer and in the health check settings take your mouse to question mark it says """Ensures that requests are sent only to instances that are up and running""" so its not recreating, if the vm not working it redirect to one which work. go to gpc console create MIG and check the questions mark of Autohealing health check settings it says """Autohealing allows recreating VM instances when needed. You can use a health check to recreate a VM instance if the health check finds it unresponsive. If you don't select a health check, Compute Engine will recreate VM instances only when they're not running.""" hope this help :)

errorfetch 👍 1 Selected: C

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

boydocarta 👍 1

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.

Aravind1996 👍 1 Selected: D

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

subha.elumalai 👍 1

Correct Answer is D

Ele24 👍 1 Selected: C

C is Correct

Arnaud92 👍 1 Selected: C

C is correct.

MiscoMove 👍 1 Selected: C

C is Correct!

thewalker 👍 1 Selected: C

C is correct

BAofBK 👍 1

The answer is C

Evan7557 👍 1

C is Correct Answer

Captain1212 👍 1

C is the right answer

Mogamat 👍 1

Answe C

rosh199 👍 1

I also vote for C

Partha117 👍 3 Selected: C

That is the only option with autohealing which will recreate instance, just doing health check using http load balancer will not help to recreate, that can only redirect traffic

Jackey0117 👍 2 Selected: C

A.B.D all don't enable Autohealing to recreate unresponsive VMs, so answer should be C.

nikila99 👍 1

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 a valid solution but requires more steps to be performed to configure autohealing. 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," does not configure autohealing for unresponsive instances. Option D, "Create a managed instance group. Verify that the autoscaling setting is on," is not relevant to the autohealing of unresponsive instances.

sutharson4u 👍 1 Selected: C

C is right answer

Suresh290587 👍 2

A is the right answer

lov75 👍 1 Selected: C

it voted for C

anirban7172 👍 1

The correct Answer is C;

eledu1985 👍 1 Selected: C

The correct answer is C as the autoscalling is on by default but if you want to recreate an instance you will need in any case a Health check, for every other option.

Sgegmund 👍 1

C is correct

gcp_world123 👍 1

C is correct

imperadoor 👍 1 Selected: C

The Answer correct is C, is the only one with the AUTOHEALING option

AzureDP900 👍 1

C is the correct answer

Himadhar1997 👍 1

C is correct option

haroldbenites 👍 2

go for C. https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing

kiemkhach 👍 1

C is correct. Autohealing is not from Load Balancer. D is for autoscaling which when memory, cpu, etc get to a certain level and create new or drop instances.

Tx4free 👍 1 Selected: C

Is the correct option

JohnPi 👍 1 Selected: C

it should be C

Eminenza22 👍 1

C is correct https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs

Eminenza22 👍 1

Create a health check for autohealing that is more conservative than a load balancing health check.

Williehk 👍 1

A, not C Question stats "for network load balancing for a group of Compute Engine instances"

pranavdhopey 👍 2 Selected: C

C is correct

Raz0r 👍 3 Selected: C

C, Agreed reference : https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing

uganeshku 👍 1

C is correct because an auto-healing health check with a managed instance group is required to perform auto-healing. D is incorrect enabling auto-scaling on a managed instance group does not enable auto-healing. Links: Auto-healing: https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing Unmanaged instance group: https://cloud.google.com/compute/docs/instance-groups#unmanaged_instance_groups

jaffarali 👍 1 Selected: C

C is the right option.

pnVino27 👍 1 Selected: C

Correct Answer: C

jabrrJ68w02ond1 👍 2

It must be C. Answer A indeed does a health check, but a failing LB health check only results in the unhealthy machine not getting any traffic. We want it to be auto-healed (restarted), so we must use a MIG + health check --> C

koxow74213 👍 1 Selected: C

for re creation of vms

shawnkkk 👍 1

C is correct,

vishnukumartr 👍 1

C. Create a managed instance group. Set the Autohealing health check to healthy (HTTP)

Jaira1256 👍 1 Selected: C

Ans - C

test157 👍 1

C should be the correct answer based on the documentation: ' managed instance group health checks proactively signal to delete and recreate instances that become UNHEALTHY.' https://cloud.google.com/compute/docs/instance-groups

lxs 👍 2

C because there is no single word mentioning the app is HTTP(s). We have NLB running. Autohealing for this scenario is just to enable autoscaling.

wress 👍 2

C is the correct answer

Shruti_Pal 👍 1

I go for C

shubjha 👍 1

C is the right answer, While creating the MIG, we need to set Auto-healing setup with HEALTH CHECK policy.

mcaromit 👍 1

C is the correct option as autohealing would recreate an unhealthy instance unlike a health-check configured with a lb

mcaromit 👍 2

C is the correct option as using a health-check with a lb (option A) would only probe if the backend instances are receiving traffic, but won't recreate unhealthy instances which is a specific ask in the question.

viswanand 👍 1

It has to be C only

ri_unhou119 👍 1

C https://cloud.google.com/compute/docs/instance-groups

tavva_prudhvi 👍 2

https://www.youtube.com/watch?v=dT7xDEtALPQ&list=PLIivdWyY5sqIij_cgINUHZDMnGjVx3rxi&index=36 I request everyone to watch this video, as in the question we have a few conditions like, the re-creation of VMs if they are unresponsive after 3 attempts of 10 seconds each. we can configure in the instanced group by setting the health check on!!!! I'm sorry if I misled anyone the correct answer is C.

ozeross 👍 1

Correct answer is C. Ites explained in the Compute engine section on Google documentation

tavva_prudhvi 👍 1

I think it's C, To configure the recreation of VMs, you need Autohealing. So not B and D. A: Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances. C: Application-based autohealing improves application availability by relying on a health checking signal that detects application-specific issues such as freezing, crashing, or overloading. If a health check determines that an application has failed on an instance, the group automatically recreates that instance. So the answer is C.

tavva_prudhvi 👍 1

Changing my answer to A. This link states that LB detect and automatically removes unhealthy VM instances using health checks. Instances that become healthy again are automatically re-added. https://cloud.google.com/compute/docs/load-balancing-and-autoscaling

pondai 👍 1

Load Balancer's "health check" just check instance health ,if it not health then load balancer doesn't transmission to the bad instance. No help to recreate instance ,so I vote C.

Fidget_ 👍 4

https://cloud.google.com/compute/docs/instance-groups#autohealing "Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances. On the other hand, managed instance group health checks proactively signal to delete and recreate instances that become UNHEALTHY"

EABDAJA 👍 1

Answer is A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)

DickDastardly 👍 2

From https://cloud.google.com/compute/docs/instance-groups Health checking The health checks used to monitor MIGs are similar to the health checks used for load balancing, with some differences in behavior. Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances. On the other hand, managed instance group health checks proactively signal to delete and recreate instances that become UNHEALTHY Health checks for load balancers do NOT re-create the instance, as per the requirement, they merely direct traffic away from the sick instance. A does not solve this requirement therefore it has to be C

navsaru 👍 1

C is correct answer

ShakthiGCP 👍 1

Answer is A: Don't get confused with other things.. just verified.

ShakthiGCP 👍 3

I was wrong. A & B are wrong because it should by NetworkLoad Balancer and not HTTP Load balancer. Ans: C is correct .

Sarin 👍 1

It should be C. Option D is for autoscaling and Autoscaling helps if there is an increase or decrease in load, not if the system is unresponsive.

GCP_Student1 👍 2

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? Pay attention to the phrases in parenthesis in the question, it will make it easy to choose the answer.

GCP_Student1 👍 2

A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)

Ramyak 👍 2

Correct Answer is C. Autohealing should be at instance group level not at LB level. Check the explanation below. Use separate health checks for load balancing and for autohealing. Health checks for load balancing can and should be more aggressive because these health checks determine whether a VM receives user traffic. You want to catch non-responsive VMs quickly, so you can redirect traffic if necessary. In contrast, health checking for autohealing causes Compute Engine to proactively replace failing VMs, so this health check should be more conservative than a load balancing health check.

Gohs 👍 1

If C is the answer, it implies that autohealing can also be called autohealing health check.

Joh3o8an 👍 2

How will one know the correct answer with all these different answers?

INASR 👍 1

Sure it is C, A &B are sure wrong , load balancer health check will not mark VM down and spin a new one, it only redirect traffic to healthy VMs. B is definitely wrong is RPS is request per seconds to the VM for balancing and has nothing to do with healing. D is wrong since autoscaling is irrelevant. C is right since heling on VM level is defined on MIB groups.

aviassu 👍 1

Answer is C. Option A is incorrect as Network Load balancer is a regional, pass-through load balancer. A network load balancer distributes TCP or UDP traffic among virtual machine (VM) instances in the same region. Option A here is talking about HTTP load balancer and hence ruled out

EABDAJA 👍 1

Answer is A

chitrranshi 👍 1

it is A

nherrerab 👍 1

Correct is C.

Number12 👍 1

Option A and B talks about existing instance groups , but where in the question we have this mentioned. D is ruled out fur to auto-scaling text. What left is C.

mani6 👍 1

It is C, the supports are given by google during creation of managed instance group are. 1.autohealing,autoscaling,auto-updating 2.multi-zone deployment 3.Load balancing So the instance group works as load balancer and auto healing.

Conjoinix 👍 3

Correct Answer is C https://cloud.google.com/compute/docs/instance-groups#health_checking The health checks used to monitor MIGs are similar to the health checks used for load balancing, with some differences in behavior. Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances. On the other hand, managed instance group health checks proactively signal to delete and recreate instances that become UNHEALTHY.

vara3dk 👍 1

Correct Ans C

adedj99 👍 3

Then answer is A . https://www.youtube.com/watch?v=FtLhVvSFi84

tavva_prudhvi 👍 1

The video only stated how to create a load balancer w.r.t MIG but did not discuss recreating the VM's instead in the beginning of the video it says, "distribute traffic"

robor97 👍 1

I will go with C. I am assuming the load balancing is configured and we just want to configure autohealing. So we create an MIG and a health check. Creating the health check, ensure the HTTP protocol is selected, set your check interval and timeout as per question. Set your Unhealthy Threshold as 3 so a new VM will be created if returned unsuccessfully 3 consecutive times. Again, the wording of the question is tricky so i am assuming load balancer is already created. This may be an incorrect assumption. https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs

magistrum 👍 1

I would say that is an incorrect assumption, if the LB were already created, the backend would have already been confitured

soukumar369 👍 1

A. This is a possible answer. This answer assumes that the existing backend is configured correctly. B. 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. This is only a partial solution. The default configuration is auto scaling enabled. You still need to create the HTTP Load Balancer. D. 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. Answer is A

tavva_prudhvi 👍 8

https://www.youtube.com/watch?v=dT7xDEtALPQ&list=PLIivdWyY5sqIij_cgINUHZDMnGjVx3rxi&index=36 step-1: go to the instance group step-2: click edit step-3: scroll down you will see auto-healing off by default change to ON step-4: create a health check saying 10 seconds as CHECK INTERVAL and UNHEALTHY THRESHOLD=3

Ozymandiax 👍 1

B & D are not options, so: A: Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances. C: Application-based autohealing improves application availability by relying on a health checking signal that detects application-specific issues such as freezing, crashing, or overloading. If a health check determines that an application has failed on an instance, the group automatically recreates that instance.

gcper 👍 1

I find myself still coming back to this question as it was one of the hardest of questions in my opinion. Previously I leaned on C, but upon yet further review I would like to change my answer to A. Why A? The reason is that network load balancing is for TCP/UDP, sure, but if we have a backend HTTP web server for example, we can still use a layer 4 load balancer to route requests to it. The only thing throwing me off now is that the question mentions an existing instance group even though they are called target pools in the documentation but that is minor. source: https://cloud.google.com/load-balancing/docs/network/setting-up-network

swatititame 👍 1

• A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)

JohnnyS20 👍 2

Feels like most people are trapped by option C because it has the keyword 'autoheal' But I have to side to the few who chose A. You really have to read the question slowly and analyze what the requirement is and what are the given. After going over the many points raised in this discussion, I'm inclined to eliminate C and D. This is because while C and D shows minimal steps, they are still missing the essential part which is the load balancer. The question also states that there's already a set of instances that are running on different zones. From there it clearly explains that there's no need to create new managed instance groups.

JohnnyS20 👍 2

Now, between A and B, A has the fewest steps. However, it should still meet the requirements. The only questionable part about the health check is that it is much accurate if there is a separate health check for http and a separate health check for autoheal. Setting aside, A still meets the requirement. Remember that the question is if the option meets the requirement, regardless if there are better ways to solve it. We must stick with the options that are given.

nmohapatra87 👍 1

correct answer is C ... Create a managed instance group. Set the Autohealing health check to healthy (HTTP)

gcper 👍 1

After coming back to this question, I agree that it is C.

JCGO 👍 1

I suppose thats multiple answer question. And we should select C) and A)

gcper 👍 2

I'd like to add that this question is about Network Load balancing Autohealing. Network load balancers require legacy health checks. Quote: "Network Load Balancing requires legacy health checks that use the HTTP protocol." source: https://cloud.google.com/load-balancing/docs/health-check-concepts Second, the answers that want you to "set a check as healthy" don't make sense, considering that there is no such option! If you look at the gcloud or console, you will not find such parameters. The closest thing to such a parameter is the HEALTHY_THRESHOLD. source: https://cloud.google.com/load-balancing/docs/health-checks#gcloud_5 C and D don't create a load balancer and the question is about network load balancer health checks so those are ruled out. A and B create HTTP load balancers but network load balancers only support TCP/UDP traffic, so neither of them would work either. Layer 7 vs layer 4. source: https://cloud.google.com/load-balancing/docs/network Is this a trick question?

glam 👍 2

C. Create a managed instance group. Set the Autohealing health check to healthy (HTTP)

glam 👍 1

Changing to A.. A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP)

99Abhi99 👍 2

C is correct. The question asks for network load balancing. HTTP load balancer (option A nd B) out of question

GopinathM 👍 1

https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs C is Correct Create a health check for autohealing that is more conservative than a load balancing health check. For example, create a health check that looks for a response on port 80 and that can tolerate some failure before it marks VMs as UNHEALTHY and causes them to be recreated. In this example, a VM is marked as healthy if it returns successfully once. It is marked as unhealthy if it returns unsuccessfully 3 consecutive times.

anony1234567 👍 1

C is correct, A and B is incorrect as the ask is for NLB. D is incorrect as it is about autoscaling and the ask is not to autoscale but to rerun the unresponsive instances which is autoheal.

SSPC 👍 2

C is correct I think

yas_cloud 👍 3

C is the right answer. Autohealing allows recreating VM instances when needed. If you don't select a health check, Compute Engine will recreate VM instances only when they're not running. In this case, we need to re-create VMs for a specific health criteria of the HTTP.

MohammedGhouse 👍 2

"C" is the answer, Autoheeling configured on Group of instance and later configure Load Balancer for frontend.

baudrual 👍 1

They are asking about network LB auto-healing so from my point of view that should be A

evangelist 👍 2

The answer is D. this is because by being ambiguous enough. C implies you just set the health check protocol being HTTP and nothing else as an action taken. but D "verify that the autoscaling setting is on" implies a multi-steps actions including setting the health check protocol to HTTP, set the interval to be 10 and attempts to be 3 and so on. I am shocked GCP test is being such a play of word games, but this is it.

samvegas 👍 1

Answer A - with Managed Instance Group - AutoScaling is set by Default. You need Health Check (which is not default), we need to to set it up.

rambest 👍 2

It is C for sure, if we see the question carefully, there are 1 trigger point is there "You need to configure re-creation of VMs if they are unresponsive after 3 attempts of 10 seconds each." This can be done only at create health check section of auto healing.

qafro 👍 2

A is my solution.

DarioFama23 👍 1

For me is A health check can be done with LB

manu202020 👍 3

D. First statement says "what you want". Second statement actually tells about the action required.

professor 👍 2

Load balancing health checks help direct traffic away from non-responsive instances and toward healthy instances; these health checks do not cause Compute Engine to recreate instances.

professor 👍 2

Ans is C managed instance group health checks proactively signal to delete and recreate instances that become UNHEALTHY.

cloudenthu01 👍 1

C is Correct D is autoscaling we do not want to create a new VM but recreate existing VM

saurabh1805 👍 1

Correct answer is C as it has auto healing.

zukko78 👍 1

C is correct

sadatus212 👍 5

Hello everyone! Can anyone of you please confirm if the GCP-ACE exam dump questions do infact appear on the real exam. Thank you in advance....

dummyken 👍 5

I took the exam just now. I can confirm I saw at least 7 questions from this dump. Do keep in mind that I only went up to page 10 so there might be more questions that appeared in both here and the exam.

ankit89 👍 2

C is right

Nischay 👍 2

Surely, it is C as auto-healing is mentioned

bryanchew 👍 23

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.

THutch 👍 2

It can't be A or B. Question clearly states, "using the fewest possible steps" and setting up an HTTP load balancer is a long, drawn out process that requires quite a few steps and is never mentioned as part of the requirement.

Ridhanya 👍 3

it cannot be option A because as you said, load balancer with the health check is already present and now the problem is simply auto healing. so we need to focus only on recreation which can happen only if option C is correct

pYWORLD 👍 4

I hope you saw that in the questions is stated: "network load balancing"

DickDastardly 👍 6

It can't be A as a load balancer does not re-create unhealthy instances, as per the requirement. Has to be C https://cloud.google.com/compute/docs/instance-groups

koniec 👍 1

It's A. Managed group already exists so create a LB with health checks. If you go for C, you will have to create a LB anyway so it's more steps to achieve the goal

googlelearning 👍 7

Surely it is C, auto-healing, as that is what it mentions in the question. It does not mention autoscaling.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option C is the correct answer because autohealing is a feature of Managed Instance Groups (MIGs), not load balancers. To configure autohealing, you must attach a health check to the MIG. When the health check detects an instance as UNHEALTHY, the MIG controller deletes the instance and creates a new one based on the template. The prompt specifies '3 attempts of 10 seconds each,' which corresponds to configuring the health check's interval and threshold settings within the MIG context.

Why the Other Options Are Wrong

Option A describes configuring a load balancer backend. As noted by community members like DickDastardly and Fidget_, load balancer health checks 'help direct traffic away from non-responsive instances' but do not cause Compute Engine to recreate instances. Options B and D are incorrect because balancing modes (B) and autoscaling (D) do not inherently provide the autohealing mechanism required to replace failed VMs. Autoscaling handles capacity changes, while autohealing handles failure recovery.

Community Comment Notes

The community consensus strongly favors C. ReyBan highlighted that 'Health checks for autohealing detect and recreate failed instances,' distinguishing them from LB health checks. ashrafh confirmed that LB health checks only redirect traffic ('redirect to one which work') rather than recreating VMs. Fidget_ quoted official documentation stating that MIG health checks 'proactively signal to delete and recreate instances.' Tavva_prudhvi provided a step-by-step console guide confirming that autohealing is toggled ON within the instance group settings.

Official Reference

https://cloud.google.com/compute/docs/instance-groups#autohealing

Exam Strategy

Always distinguish between 'traffic management' (Load Balancing) and 'infrastructure repair' (Autohealing/MIG). If the question asks to 'recreate' or 'repair' instances, look for Managed Instance Group configurations. If it asks to 'distribute' or 'route' traffic, look at Load Balancer backends.

Frequently Asked Questions

Why can't I use a Network Load Balancer health check for autohealing?

Network Load Balancer health checks only determine if an instance receives traffic. They do not trigger the deletion and recreation of the VM instance itself.

Does enabling autoscaling automatically heal broken VMs?

No. Autoscaling adjusts the number of instances based on load metrics. Autohealing is a separate setting within the MIG that monitors health and replaces unhealthy instances.

More ACE FAQ →

Related Analysis

Practice All ACE Questions

Access 84 questions with complete answers and detailed explanations.

View Full ACE Practice Test →

← Back to ACE Study Guide

Configure Autohealing for Managed Instance Groups

Community Insight

Community Discussion (136 comments)

Comments & Corrections

Expert Analysis

Why the Answer Is Correct

Why the Other Options Are Wrong

Community Comment Notes

Official Reference

Exam Strategy

Frequently Asked Questions

Why can't I use a Network Load Balancer health check for autohealing?

Does enabling autoscaling automatically heal broken VMs?

Related Analysis

You need to monitor resources that are distributed over diff

You are building an application that will run in your data c

You need to configure IAM access audit logging in BigQuery f

Practice All ACE Questions