Examkin

Question

Difficulty: MediumRelease Management and Deployment Strategies

A financial technology organization hosts a mission-critical payment processing backend on Compute Engine Regional Managed Instance Groups (MIGs) behind an Internal Application Load Balancer. The operations team needs to automate application deployment releases to achieve zero downtime, support progressive instance replacement, and preserve infrastructure state consistency across continuous delivery runs without introducing security vulnerabilities. Which deployment and release management strategy should the Cloud Architect recommend?

  1. Configure an automated rolling update on the Managed Instance Group with maximum surge capacity while managing all infrastructure definitions through Terraform using a Cloud Storage backend with object versioning enabled.Answer
  2. B
    Perform application releases by manually updating instance template configurations directly in the Google Cloud Console during deployment windows to bypass automated build pipeline checks.
  3. C
    Deploy application updates using a CI/CD pipeline service account that is granted the primitive Owner role to ensure uninterrupted resource management permissions.
  4. D
    Provision a parallel instance group for releases while persisting Terraform state files in local runner disk storage to speed up build execution times.

Answer

Configure an automated rolling update on the Managed Instance Group with maximum surge capacity while managing all infrastructure definitions through Terraform using a Cloud Storage backend with object versioning enabled.
The option recommending an automated rolling update on the Managed Instance Group combined with Terraform using a versioned Cloud Storage backend follows GCP reliability best practices. MIG rolling updates systematically cycle instances to guarantee zero downtime, while remote versioned state storage ensures safe, concurrent, and recoverable infrastructure automation.

Step-by-Step Solution

1
Evaluate application deployment and rollback requirements.
Identify that Compute Engine Regional Managed Instance Groups natively support rolling updates with max surge and max unavailable parameters to ensure zero-downtime releases.
MIG rolling updates replace instances progressively while maintaining total service capacity.
2
Establish Infrastructure as Code state management best practices.
Configure Terraform to use a Cloud Storage remote backend with object versioning and state locking.
Remote state backends prevent local state loss, concurrency race conditions, and drift.
3
Enforce security and operational automation controls.
Utilize fine-grained IAM roles for deployment pipelines instead of primitive roles, avoiding manual console interventions.
Adheres to security compliance and eliminates configuration drift.

Key Concept

Managed Instance Group Rolling Updates and IaC State Reliability
Rate this question

Topics

Release Management and Deployment Strategies

More questions from this topic