Question-52:You have built a non-critical upgrade for your application, which is now operating in a managed instance group. Additionally, you have generated a new instance template that contains the update, which you want to distribute. You shouldn't make any updates to any running instances of the programme since doing so might have unexpected side effects. You want for the newly updated version to be included in any new instances that are generated by the managed instance group. What is it that you ought to do?
A. Commence a brand new rolling restart procedure.
B. Commence a brand new rolling replace procedure.
C. Begin a new iteration of the rolling update. Make sure the Proactive update mode is selected.
D. Begin a fresh iteration of the rolling update. Choose the Opportunistic update mode from the drop-down menu.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 4 Explanation: Instead of option 3, which is proactive mode, the right choice is option 4, which is opportunistic mode. The need is to not update any instances that are already operating. You will need to set the mode to proactive in order to enable automatic rolling updates. You also have the option of doing what is known as an opportunistic update in the event that an automatic update may possibly be too disruptive. Only when you explicitly begin the update on chosen instances or when brand new instances are generated will the MIG apply an opportunistic update to those instances. When you or another service, such as an autoscaler, resize the MIG, the possibility exists for new instances to be produced. Option-4 Start a new rolling update. Select the Opportunistic update mode. Automatic updates and proactive updates are both supported by managed instance groups as different types of update mode. Updates chosen based on factors such as need or opportunity You will need to set the mode to proactive in order for automatic updates to be applied. You also have the option of doing what is known as an opportunistic update in the event that an automatic update may possibly be too disruptive. Only when you explicitly begin the update on chosen instances or when brand new instances are generated will the MIG apply an opportunistic update to those instances. You have the option of performing what's known as an opportunistic update in the event that an automated update might be too disruptive. Only when you explicitly begin the update on chosen instances or when brand new instances are generated will the MIG apply an opportunistic update to those instances. When you or another service, such as an autoscaler, resize the MIG, the possibility exists for new instances to be produced. Compute Engine does not actively initiate requests to apply opportunistic updates on existing instances. (You can read more about how to roll out updates to managed instance groups here: The MIG will only apply an opportunistic update in the two situations that were outlined earlier: (1) when you manually initiate the update on selected instances, and (2) when new instances are created. Those are the only two situations in which an opportunistic update will be applied. According to the supporting documentation, the correct answer is D. An opportunistic update can be helpful in certain circumstances because you typically want to avoid introducing instability into the system if it is at all possible to do so. For instance, if you have a non-critical update that can be applied whenever it is necessary without any sense of urgency and you have a MIG that is actively being autoscaled, you should perform an opportunistic update so that Compute Engine does not actively tear down your existing instances in order to apply the update. This is because an opportunistic update allows you to apply the update without Compute Engine actively tearing down your instances. When performing a downsize, the autoscaler will prioritise shutting down instances that are based on the previous template in addition to instances that are not yet in the RUNNING state.