C, is the correct answer. As per the requirement linux expert would need access to VM to troubleshoot the issue. With health check enabled, old VM will be terminated as soon as health-check fails for the VM and new VM will be auto-created. So, this situation will prevent linux expert to troubleshoot the issue. Had it been the case that stack-drover logging is enabled and the expert just want to view the logs from the Cloud-logs than role to project-viewer could help. But it is specifically mentioned that expert will login into VM to troubleshoot the issue and not looking at the cloud Logs. So, Option-C is the correct answer.

C should be correct answer.

C is correct!

I like C

To allow your colleague, who is a Linux expert, to access the VMs and troubleshoot the issue, you should disable the health check for the instance group. This will prevent the instance group from automatically removing and replacing unhealthy instances. You should also add your colleague's SSH key to the project-wide SSH Keys to allow him to SSH into the instances and perform troubleshooting. This can be done through the Google Cloud Console or the gcloud command-line tool.

C. Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys. Granting the IAM role of project Viewer (Option A) would allow your colleague to view the project resources but not necessarily give them access to the specific VM instances. Performing a rolling restart on the instance group (Option B) would not resolve the issue, as the instances keep restarting after 5 seconds. Disabling autoscaling for the instance group (Option D) is not relevant since autoscaling is already disabled. Disabling the health check for the instance group will prevent the managed instance group from automatically recreating the instances. Adding your colleague's SSH key to the project-wide SSH Keys will allow them to access the VMs and troubleshoot the issue. Once the issue is resolved, you can re-enable the health check for the instance group.

C is the answer

C as the machines will keep restarting if hc is not disabled , and then our expert can look around for RCA

To allow your colleague access the instances in MIG you should do option D: Disable autoscaling for the instance group. Add his SSH key to the project-wide SSH Keys. Disabling autoscaling for the instance group will prevent new instances from being created or terminated while your colleague is trying to troubleshoot the issue. This will give him a stable environment to work in and will ensure that he can access the instances that are currently in the instance group. Adding his SSH key to the project-wide SSH Keys will allow him to connect to the instances using Secure Shell (SSH) without requiring a password. This is a convenient way to give him access to the instances and can help him troubleshoot the issue more efficiently.

C is the correct answer

ok for C

C. Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys. This will allow the engineer to logon to the VM's and check the logs. Disabling health checks will prevent rebooting of the VM's.

C should be the correct answer

Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys

vote C what can project viewer do without access vm by linux expert?

I believe that answer C is correct.

About create SSH Keys to VM https://cloud.google.com/compute/docs/connect/create-ssh-keys