Mig Rolling Update Zero Downtime Capacity

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A mission-critical e-commerce application is deployed across three zones using a regional Managed Instance Group (MIG) with a target size of 30 VM instances (10 instances per zone). During operational hours, the application cannot tolerate any reduction in its baseline serving capacity, as dropping below 30 active instances will cause immediate request latency spikes and service degradation. A security patch requires updating the operating system image across the fleet by rolling out a new instance template.

Which update policy configuration should you apply to execute an automated rolling update without dropping below the required 30 serving instances?

Set the update type to proactive, configure maxSurge to 0, set maxUnavailable to 3, and allow REPLACE as the disruption action.

Set the update type to opportunistic, configure both maxSurge and maxUnavailable to 0, and execute a rolling replace command.

Set the update type to proactive, configure maxUnavailable to 0, set maxSurge to a positive value (such as 3 or 10%), and allow REPLACE as the disruption action.

Set the update type to proactive, set minimalAction to REFRESH, set mostDisruptiveAllowedAction to RESTART, and configure maxSurge to 3.

Professional Cloud DevOps Engineer

Mig Rolling Update Zero Downtime Capacity

Related questions