Google Professional Cloud Developer

Get started today

Ultimate access to all questions.

Explanation:

To deploy a new instance template without service impact, the MIG should prioritize maintaining capacity during the update. Setting Max Surge to 100% (Option A) allows the MIG to temporarily create up to 100% more instances than the target size. This ensures new instances are fully provisioned before old ones are terminated, preventing downtime.

Option B (Opportunistic Update mode) does not guarantee immediate or automated replacement of instances, making it unsuitable for urgent fixes.
Option C (Maximum Unavailable 100%) would cause all instances to be taken down simultaneously, leading to service disruption.
Option D (Minimum Wait time 0) speeds up the update but does not inherently prevent capacity loss if other parameters (like Max Surge) are not configured correctly.

Explanation:

Option B (Opportunistic Update mode) does not guarantee immediate or automated replacement of instances, making it unsuitable for urgent fixes.
Option C (Maximum Unavailable 100%) would cause all instances to be taken down simultaneously, leading to service disruption.
Option D (Minimum Wait time 0) speeds up the update but does not inherently prevent capacity loss if other parameters (like Max Surge) are not configured correctly.

Comments (0)

No comments yet.

When deploying a new instance template to address a critical vulnerability across hundreds of Compute Engine instances in a multi-zone managed instance group (MIG), which MIG setting should be configured to ensure zero service disruption during the update?

Exam-Like

Last updated: January 1, 2026 at 14:03

Set the Max Surge to 100%.

68.2%

Set the Update mode to Opportunistic.

16.7%

Set the Maximum Unavailable to 100%.

7.6%

Set the Minimum Wait time to 0 seconds.

7.6%