Topic: Associate Cloud Engineer topic 1 question 51

You need to create an autoscaling managed instance group for an HTTPS web application. You want to make sure that unhealthy VMs are recreated. What should you do?

A.
Create a health check on port 443 and use that when creating the Managed Instance Group.
B.
Select Multi-Zone instead of Single-Zone when creating the Managed Instance Group.
C.
In the Instance Template, add the label 'health-check'.
D.
In the Instance Template, add a startup script that sends a heartbeat to the metadata server.

Re: Associate Cloud Engineer topic 1 question 51

I'll go with A, MIGs support autohealing, load balancing, autoscaling, and auto-updating. no the Images templates, this is set up in the MIG

Re: Associate Cloud Engineer topic 1 question 51

The correct answer is A. Please, modify it.

  • XNap
  • New member
  • Offline

Re: Associate Cloud Engineer topic 1 question 51

The correct answer is A. Create a health check on port 443 and use that when creating the Managed Instance Group.

Option B is related to the availability and distribution of instances across multiple zones, but it does not directly address the requirement of recreating unhealthy VMs.
Option C is incorrect because labels are not used for configuring health checks in GCP.
Option D is an alternative method for health checking, but it is not as straightforward as using the built-in health check functionality provided by GCP for managed instance groups.

Re: Associate Cloud Engineer topic 1 question 51

Only A answer has some sense

Re: Associate Cloud Engineer topic 1 question 51

443 means http A seems more correct

Re: Associate Cloud Engineer topic 1 question 51

C is incomplete. A  all the way

Re: Associate Cloud Engineer topic 1 question 51

Option A is the correct choice because it involves creating a health check specifically on port 443, which is the standard port for HTTPS traffic. This health check will monitor the health of the instances based on their ability to respond to HTTPS requests. When creating the Managed Instance Group, you would configure it to use this health check to determine the health of the instances
Options B, C, and D are not directly related to setting up proper health checks for autoscaling and ensuring unhealthy instances are recreated

Re: Associate Cloud Engineer topic 1 question 51

A for A-Game let's goooo!

Re: Associate Cloud Engineer topic 1 question 51

C is definitely incorrect. Adding a label does not recreate unhealthy VMs.
A is CORRECT.

Re: Associate Cloud Engineer topic 1 question 51

As web application is on Https, so will set port 443 to check health of instance.

Re: Associate Cloud Engineer topic 1 question 51

A is the right answer.
ANSWER C is incorrect, adding a label to the instance template, has no direct impact on the ability to recreate unhealthy VMs.

Re: Associate Cloud Engineer topic 1 question 51

ANSWER A. Create a health check on port 443 and use that when creating the Managed Instance Group.

To ensure that unhealthy VMs are recreated, a health check should be created to monitor the instances in the managed instance group. This health check should be configured to check the appropriate endpoint for the web application, which in this case would be port 443 for HTTPS. If an instance is determined to be unhealthy, the instance group will automatically recreate it.

INCORRECT:

ANSWER B is not directly related to recreating unhealthy VMs, but instead ensures that the instance group spans multiple zones for increased availability.

ANSWER C, adding a label to the instance template, has no direct impact on the ability to recreate unhealthy VMs.

ANSWER D, adding a startup script to send a heartbeat to the metadata server, can help detect and recover from application-level failures, but it does not directly ensure that unhealthy VMs are recreated.

Re: Associate Cloud Engineer topic 1 question 51

I go with A, default port is 443 for https

Re: Associate Cloud Engineer topic 1 question 51

This shows the importance of reading exactly what it says.  The label can throw you off.   A is the answer.

Re: Associate Cloud Engineer topic 1 question 51

A obviously, port 443 for HTTPS application

Re: Associate Cloud Engineer topic 1 question 51

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

Re: Associate Cloud Engineer topic 1 question 51

Answer is A.  Just adding label doesn't do any thing