Examkin

Soru

Zorluk: OrtaRelease Management and Deployment Strategies

An enterprise operations team is preparing to update a stateless web application running on a Compute Engine Managed Instance Group (MIG) positioned behind an Internal Application Load Balancer. During previous release cycles, updating the instance template caused service disruption because existing instances were terminated before new instances became fully operational. The team needs to configure a rolling update strategy that guarantees maximum available capacity is preserved throughout the release without incurring service downtime. Which configuration strategy should the cloud architect recommend?

  1. Configure the MIG rolling update policy with maxSurge set to a value greater than zero and maxUnavailable set to zero, while ensuring load balancer health checks verify instance readiness.Cevap
  2. B
    Configure the load balancer health check endpoint to query the deep backend database connection pool directly to determine when new MIG instances are ready for traffic.
  3. C
    Maintain the MIG update parameters and deployment automation state within unversioned local state storage on the deployment worker node to speed up execution.
  4. D
    Grant the deployment service account the primitive Owner IAM role on the project to override instance creation delays and force immediate MIG instance termination.

Cevap

Configure the MIG rolling update policy with maxSurge set to a value greater than zero and maxUnavailable set to zero, while ensuring load balancer health checks verify instance readiness.
Configuring a Compute Engine Managed Instance Group rolling update with maxSurge set above zero and maxUnavailable set to zero ensures that new instances with the updated template are brought online and verified healthy before any existing instances are removed. This guarantees that total active serving capacity never drops below the required baseline during deployment.

Adım Adım Çözüm

1
Analyze capacity requirements during rolling updates for Compute Engine MIGs.
Identified that capacity must not drop below 100% of the target size during the release window.
Setting maxUnavailable to 0 prevents the MIG manager from deleting active instances before replacement instances are healthy.
2
Determine the surge capacity mechanism for replacement instances.
Setting maxSurge > 0 permits the MIG to temporarily create extra instances above the target size.
Surging creates replacement instances first, allowing them to pass health checks before older instances are drained and deleted.
3
Evaluate health check configuration best practices for load balancing and deployment verification.
Health checks should test application endpoint readiness locally rather than deep backend database dependencies.
Deep dependency checks risk cascading instance unhealthy status across the entire pool during database load spikes.

Anahtar Kavram

MIG Rolling Update Capacity Preservation (maxSurge vs maxUnavailable)
Bu soruyu puanla

Konular

Release Management and Deployment Strategies

Bu konudan daha fazla soru