Troubleshooting Compute Engine Managed Instance Group Outage

Troubleshooting Compute Engine Managed Instance Group Outage

Question

You have an outage in your Compute Engine managed instance group: all instances keep restarting after 5 seconds.

You have a health check configured, but autoscaling is disabled.

Your colleague, who is a Linux expert, offered to look into the issue.

You need to make sure that he can access the VMs.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

In this scenario, the Compute Engine managed instance group is facing an outage where all instances are restarting after every 5 seconds. To troubleshoot the issue, a Linux expert colleague needs access to the VMs. Here are the details of the answer options:

Option A: Grant your colleague the IAM role of project Viewer This option is not a suitable solution as granting project Viewer access is not enough to troubleshoot the issue. The project Viewer role only provides read-only access to resources, which is not sufficient for fixing the issue.

Option B: Perform a rolling restart on the instance group Performing a rolling restart is a good practice to apply updates or changes to instances gradually, but it won't help to solve the current issue as all instances are facing the same problem and will continue to do so even after a restart.

Option C: Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys This option is the correct answer as it provides the necessary access to the Linux expert colleague while also disabling the health check that may be causing the restart issue. Disabling the health check allows the instances to remain running and available for SSH access. Adding the colleague's SSH key to the project-wide SSH Keys enables the colleague to access the VMs using SSH.

Option D: Disable autoscaling for the instance group. Add his SSH key to the project-wide SSH Keys. This option only disables autoscaling for the instance group and does not provide access to the Linux expert colleague to troubleshoot the issue.

Therefore, the best answer to this question is Option C: Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys.