An enterprise financial service runs a critical stateless application deployed inside a regional Managed Instance Group (MIG) in `us-central1`. The team needs to deploy a newly created instance template (`finapp-v2`) to the MIG with zero application downtime. Additionally, operational monitoring alerts reveal that during peak traffic events, the MIG attempts to autoscale beyond its current capacity but fails because the project has reached its regional N2 CPU quota limit. Which TWO actions should you perform to execute the update seamlessly and resolve the operational bottleneck?
- Perform a rolling update on the MIG referencing the new instance template while setting the maximum unavailable instances to zero.Answer
- Request a quota increase for N2 CPUs in the target region through the Google Cloud Console or gcloud Quotas API.Answer
- CModify the existing instance template directly using gcloud compute instance-templates edit to update the image and machine type.
- DDeploy a duplicate Managed Instance Group in a separate zone within the same region to automatically bypass regional N2 CPU quotas.
- EGrant the deployment service account the Owner primitive role to automatically bypass regional quota restrictions during autoscaling events.
Answer
To update the Managed Instance Group without downtime and resolve the autoscaling quota bottleneck, you must perform a rolling update specifying zero maximum unavailable instances and submit a formal request for an N2 CPU quota increase in the target region.
Updating a Managed Instance Group requires creating a new instance template and starting a rolling update configured with zero maximum unavailable instances so that application availability is maintained throughout the rollout. When instance capacity is bounded by project limits, the correct operational procedure is to request a regional quota increase via the GCP Console or Quotas API.
Step-by-Step Solution
Key Concept
Compute Engine MIG rolling update strategy and GCP regional quota management workflows.