Examkin

Question

Difficulty: MediumRelease Management and Deployment Strategies

A logistics organization is updating its regional fleet tracking API service, which runs on Compute Engine Managed Instance Groups (MIGs) managed by an automated Infrastructure as Code (IaC) continuous delivery pipeline. The team needs to ensure zero-downtime rolling updates while maintaining release reliability, state consistency, and security. Which deployment and pipeline configuration should the team implement?

  1. Configure a dedicated shallow HTTP health check endpoint for the load balancer, maintain Terraform state in a centralized versioned Cloud Storage bucket, and assign least-privilege IAM roles to the CI/CD service account.Answer
  2. B
    Configure load balancer health checks to perform deep database query checks on backend instances, maintain Terraform state in a centralized versioned Cloud Storage bucket, and assign least-privilege IAM roles to the CI/CD service account.
  3. C
    Configure a dedicated shallow HTTP health check endpoint for the load balancer, maintain Terraform state on the ephemeral local runner disk of the CI/CD host, and assign least-privilege IAM roles to the CI/CD service account.
  4. D
    Configure a dedicated shallow HTTP health check endpoint for the load balancer, maintain Terraform state in a centralized versioned Cloud Storage bucket, and grant the primitive Owner role to the CI/CD service account to eliminate deployment failures.

Answer

Configure a dedicated shallow HTTP health check endpoint for the load balancer, maintain Terraform state in a centralized versioned Cloud Storage bucket, and assign least-privilege IAM roles to the CI/CD service account.
The combination of shallow HTTP health checks, a centralized versioned Cloud Storage backend for Terraform state, and least-privilege IAM roles ensures zero-downtime rolling updates, protects infrastructural state integrity, and complies with enterprise security controls.

Step-by-Step Solution

1
Evaluate load balancer health check configuration for MIG rolling deployments.
Using a shallow endpoint (e.g., /healthz returning 200 OK without deep database queries) ensures the load balancer accurately measures web server process responsiveness without triggering false-positive instance reinstantiations during database load spikes.
Deep health checks create cascading operational failures across backend instances when downstream dependencies experience transient latency.
2
Assess state file management for automated IaC deployment pipelines.
Persisting Terraform state in Cloud Storage with object versioning and locking ensures concurrent deployment safety and prevents state corruption.
Local disk storage is ephemeral and leads to state drift or loss in automated CI/CD runners.
3
Determine appropriate Identity and Access Management permissions for the release pipeline.
Granting specific predefined or custom roles (such as Compute Instance Admin and Storage Object Admin) enforces security governance.
Primitive roles like Owner grant excessive permissions, violating organizational security controls.

Key Concept

Reliable deployment release engineering combining shallow health checks, secure IaC state management, and least-privilege access controls.
Rate this question

Topics

Release Management and Deployment Strategies

More questions from this topic