Question

Difficulty: EasyManaging Compute Engine Resources

Your organization runs a web application on Compute Engine instances within a Managed Instance Group (MIG). You need to deploy an updated version of your software to all instances in the group while maintaining zero downtime. Which TWO actions should you perform?

  1. Create a new instance template that specifies the updated application configuration.Answer
  2. Start a rolling update on the Managed Instance Group using the newly created instance template.Answer
  3. C
    Assign the primitive Owner role to the Managed Instance Group service account to bypass deployment constraints.
  4. D
    Reconfigure the Managed Instance Group to use Spot VMs to guarantee zero downtime during updates.
  5. E
    Submit a GCP quota increase request for Compute Engine CPU cores before modifying instance configurations.

Answer

The two correct actions are creating a new instance template containing the updated configuration and initiating a rolling update on the Managed Instance Group with that new template.
Because Compute Engine instance templates are immutable, updating a Managed Instance Group requires creating a new instance template with the updated configuration, followed by a rolling update on the group to replace instances gradually without downtime.

Step-by-Step Solution

1
Create a new Compute Engine instance template specifying the updated software version or startup script.
A new instance template resource is defined in the project.
Instance templates are immutable; any configuration update requires generating a new template.
2
Execute a rolling update on the target Managed Instance Group referencing the newly created template.
The MIG automatically replaces instances in batches according to update policy parameters.
Rolling updates replace instances incrementally, avoiding service downtime.

Key Concept

Updating Managed Instance Groups via new instance templates and rolling updates
Rate this question