Examkin

Question

Difficulty: EasyManaging Compute Engine Resources

A Cloud Engineer needs to update an existing Compute Engine Managed Instance Group (MIG) to use a new VM configuration. In which sequence should the engineer execute the administrative steps to perform a zero-downtime rolling update?

  1. 1Create a new Compute Engine instance template containing the updated VM configuration.
  2. 2Update the Managed Instance Group configuration to reference the newly created instance template.
  3. 3Start a rolling update action on the Managed Instance Group to replace running instances.
  4. 4Monitor the update operation until all instances report as running and healthy under the new template.

Answer

The correct sequence to perform a rolling update on a Managed Instance Group is: 1) Create a new instance template, 2) Update the Managed Instance Group to point to the new template, 3) Initiate a rolling update on the group, and 4) Monitor the update process until completion.
Updating a Managed Instance Group with new software or configurations requires creating a new immutable instance template first. Once the template is created, the Managed Instance Group must be updated to reference the new template. Initiating a rolling update then systematically replaces existing running instances with new instances built from the updated template. Finally, monitoring confirms all instances are successfully updated and passing health checks.

Step-by-Step Solution

1
Create the new instance template
A new Compute Engine instance template resource with the required updates is provisioned in Google Cloud.
Compute Engine Managed Instance Groups rely on immutable templates; any change requires defining a new template.
2
Assign the template to the Managed Instance Group
The target instance template property of the Managed Instance Group is updated.
The group configuration must be updated to specify which template should be used for replacement VMs.
3
Initiate the rolling update
Compute Engine starts replacing existing VM instances with instances created from the new template.
Changing the target template does not automatically replace existing instances; an explicit rolling update must be initiated.
4
Monitor rollout progress
All instances in the group transition to the new version and pass health checks.
Monitoring verifies that the update completed successfully without causing service failure.

Key Concept

Compute Engine Managed Instance Group Rolling Updates
Estimated Time:1m 0s
Rate this question

Topics

Managing Compute Engine Resources

More questions from this topic