Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 1 question 46 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 46
Topic #: 1
[All Professional Cloud Architect Questions]

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?

  • A. Grant your colleague the IAM role of project Viewer
  • B. Perform a rolling restart on the instance group
  • C. Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys
  • D. Disable autoscaling for the instance group. Add his SSH key to the project-wide SSH Keys
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Narinder
Highly Voted 2 years, 10 months ago
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.
upvoted 91 times
twistyfries
2 years, 9 months ago
great answer
upvoted 2 times
...
AmitAr
2 years, 6 months ago
This looks best justification between A and C.. So, C should be correct answer.
upvoted 2 times
...
devjuliusoh
2 years, 3 months ago
Good explanation
upvoted 2 times
...
ashishdwi007
10 months ago
The key element in C is "Disable the Health check.", so that server wont restart automatically. But before that the actual troubleshooting step is to check Cloud console -> Instance template -> Metadata-> and see if any startup script is there, if yes review it and possibly remove it. [Consider the case, a script is causing restarting the VM, (possibly in Metadata). ]
upvoted 1 times
...
...
KouShikyou
Highly Voted 5 years, 1 month ago
C should be correct answer.
upvoted 39 times
...
Ekramy_Elnaggar
Most Recent 5 days, 1 hour ago
Selected Answer: C
1. Access for troubleshooting: Disabling the health check prevents the VMs from constantly restarting, allowing the expert to log in and investigate the root cause. 2. SSH access: Adding the expert's SSH key grants them the necessary access to the VMs. 3. Temporary measure: This is a temporary measure for troubleshooting. Once the issue is resolved, the health check should be re-enabled.
upvoted 1 times
...
wilson1005
8 months, 1 week ago
Selected Answer: C
C is correct!
upvoted 1 times
...
heretolearnazure
1 year, 3 months ago
I like C
upvoted 1 times
...
JC0926
1 year, 8 months ago
Selected Answer: 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.
upvoted 3 times
...
MestreCholas
1 year, 8 months ago
Selected Answer: C
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.
upvoted 5 times
...
urssiva
1 year, 9 months ago
Selected Answer: C
C is the answer
upvoted 1 times
...
roaming_panda
1 year, 10 months ago
C as the machines will keep restarting if hc is not disabled , and then our expert can look around for RCA
upvoted 1 times
...
omermahgoub
1 year, 11 months ago
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.
upvoted 2 times
n_nana
1 year, 10 months ago
autoscaling is already disabled. Answer D is not make sense here. i voted it wrongly instead of reply.
upvoted 1 times
...
omermahgoub
1 year, 11 months ago
Option A: Granting your colleague the IAM role of project Viewer will not allow him to access the instances in the managed instance group. The project Viewer role does not include any permissions to access Compute Engine resources. Option B: Performing a rolling restart on the instance group will not solve the issue and may even make it worse if the instances are not able to start up properly. Option C: Disabling the health check for the instance group will not solve the issue and may even make it worse if the instances are not able to start up properly. Adding his SSH key to the project-wide SSH Keys will allow him to access the instances, but it is not a sufficient solution on its own.
upvoted 2 times
...
...
surajkrishnamurthy
1 year, 11 months ago
Selected Answer: C
C is the correct answer
upvoted 1 times
...
megumin
2 years ago
Selected Answer: C
ok for C
upvoted 1 times
...
minmin2020
2 years, 1 month ago
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.
upvoted 2 times
...
holerina
2 years, 2 months ago
C should be the correct answer
upvoted 1 times
...
abirroy
2 years, 2 months ago
Selected Answer: C
Disable the health check for the instance group. Add his SSH key to the project-wide SSH Keys
upvoted 1 times
...
backhand
2 years, 3 months ago
vote C what can project viewer do without access vm by linux expert?
upvoted 1 times
...
tricky_learner
2 years, 4 months ago
Selected Answer: C
I believe that answer C is correct.
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...