ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam
Go to Exam

Exam Professional Cloud Developer topic 1 question 162 discussion

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

Your application is deployed on hundreds of Compute Engine instances in a managed instance group (MIG) in multiple zones. You need to deploy a new instance template to fix a critical vulnerability immediately but must avoid impact to your service. What setting should be made to the MIG after updating the instance template?

  • A. Set the Max Surge to 100%.
  • B. Set the Update mode to Opportunistic.
  • C. Set the Maximum Unavailable to 100%.
  • D. Set the Minimum Wait time to 0 seconds.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
by sahith24 at Dec. 14, 2022, 2:41 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
micoams
Highly Voted 2 years, 6 months ago
Selected Answer: D
You can eliminate: B. Because the MIG needs to be updated immediately, which not what Opportunistic does C. Because max unavailable at 100% will cause downtime So that leaves A, and D. If you choose A. The MIG will spin up hundreds of new machines, to replace the existing one, and shutdown the old ones. This is the fastest method, but could be costly, or you could run into quota issues. If you choose D, the MIG will spin up 3 VMs at a time (maxSurge default to 3), and then it will bring up one at a time, as soon as more surge slots are available, so it wont be really that fast. I think D is the most sensible in this case.
upvoted 10 times
...
thewalker
Most Recent 7 months, 4 weeks ago
Selected Answer: A
In a Managed Instance Group (MIG), to update instances without impacting your service, you can use rolling updates. This allows new instances to be created and brought online before the old instances are terminated, avoiding downtime. Max Surge defines the number of additional instances that can be created temporarily during the update process. By setting the Max Surge to 100%, you are allowing the MIG to create up to the same number of new instances as existing ones (effectively doubling the capacity temporarily). This helps ensure the service is not disrupted because new instances will be up and running before the old ones are terminated.
upvoted 2 times
thewalker
7 months, 4 weeks ago
Why Not the Other Options: B. Set the Update mode to Opportunistic: This would attempt updates only when instances are not busy, but it could delay the update of critical instances, which you need to avoid given the urgency of the vulnerability fix. C. Set the Maximum Unavailable to 100%: This would allow all instances to be unavailable during the update, leading to potential downtime and impact on your service, which is not acceptable. D. Set the Minimum Wait time to 0 seconds: This controls how long the MIG waits after a new instance is considered healthy before terminating the old ones. Setting it to 0 seconds may not prevent downtime, as you could risk terminating instances too quickly, before the new instances are fully stable.
upvoted 1 times
...
...
wanrltw
1 year, 6 months ago
Selected Answer: D
I vote D. There are 2 requirements: to deploy the new instance template immediately and to avoid impact. Option D matches the urgency of the issue well but it also allows to control (minimize) the level of disruption to the service. https://cloud.google.com/compute/docs/instance-groups/updating-migs#choosing_between_automated_and_selective_updates
upvoted 2 times
...
__rajan__
1 year, 8 months ago
Selected Answer: B
When you set the update mode to Opportunistic, the group will continue to serve requests from existing instances while the new instances are being created and started. Once the new instances are ready, the group will start routing requests to them. The group will continue to serve requests from both the old and new instances until all of the old instances have been terminated.
upvoted 2 times
...
purushi
1 year, 10 months ago
Selected Answer: D
The key here is fixing the vulnerability immediately which is not possible with Opportunistic mode.
upvoted 2 times
...
NewComer200
2 years, 1 month ago
Selected Answer: D
I think updating "deployed on hundreds of Compute Engine instances" is impossible with Opportunistic mode. So I agree with D.
upvoted 1 times
sbonessi
2 years ago
And also said changes immediately, so opportunistic mode is not suitable as well. Agree with D
upvoted 1 times
...
...
closer89
2 years, 1 month ago
Selected Answer: D
i go for D you've updated template and want apply changes immediately
upvoted 1 times
...
Pime13
2 years, 3 months ago
Selected Answer: D
https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#minimum_wait_time Use the minReadySec option to specify the amount of time to wait before considering a new or restarted instance as updated. Use this option to control the rate at which the automated update is deployed. The timer starts when both of the following conditions are satisfied: The instance's status is RUNNING. If health checking is enabled, when the health check returns HEALTHY. However: minReadySec is only available in the beta Compute Engine API and might be deprecated in a future release.
upvoted 1 times
...
mrvergara
2 years, 4 months ago
Selected Answer: D
Setting the "Minimum Wait time" to 0 seconds means that there is no delay in launching the new instances after the instance template is updated, allowing you to deploy the fix for the critical vulnerability immediately. On the other hand, setting the "Update mode to Opportunistic" would mean that the new instances are created at an opportune time and may result in a delay in deploying the fix. In this scenario, where a critical vulnerability needs to be fixed immediately, it's important to deploy the fix as soon as possible, making the "Minimum Wait time to 0 seconds" the better approach.
upvoted 2 times
...
TNT87
2 years, 5 months ago
Selected Answer: B
https://cloud.google.com/compute/docs/instance-groups/updating-migs#opportunistic_updates Answer B
upvoted 1 times
...
zellck
2 years, 6 months ago
Selected Answer: B
B is the answer. https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#type Alternatively, if an automated update is potentially too disruptive, you can choose to perform an opportunistic update. The MIG applies an opportunistic update only when you manually initiate the update on selected instances or when new instances are created. New instances can be created when you or another service, such as an autoscaler, resizes the MIG. Compute Engine does not actively initiate requests to apply opportunistic updates on existing instances.
upvoted 4 times
...
sahith24
2 years, 6 months ago
Answer?
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