Examkin

Soru

Zorluk: OrtaBuilding and Managing Infrastructure as Code (IaC)

An autonomous fleet management company provisions its Google Cloud infrastructure using Terraform within a automated CI/CD deployment pipeline. The engineering team needs to enforce secure, environment-isolated state management across development, staging, and production while preventing concurrent state execution conflicts and state corruption. Which architecture best adheres to Google Cloud recommendations for Terraform remote backend state governance?

  1. Store each environment's state in a separate dedicated Cloud Storage bucket with Object Versioning enabled, utilizing native state locking and fine-grained IAM controls.Cevap
  2. B
    Store state files locally on the CI/CD runner's persistent disk to avoid remote Cloud Storage network latency during pipeline execution.
  3. C
    Grant the primitive Editor role to the CI/CD service account to ensure unconstrained permission to create and manage state resources across all environments.
  4. D
    Allow administrators to perform manual updates via the Cloud Console when pipeline locks stall, then force-refresh local state files.

Cevap

Store each environment's state in a separate dedicated Cloud Storage bucket with Object Versioning enabled, utilizing native state locking and fine-grained IAM controls.
According to Google Cloud best practices for Infrastructure as Code, Terraform state for different environments should be isolated into separate Cloud Storage buckets. Object Versioning ensures state history can be restored if corrupted, while GCS natively supports state locking to prevent race conditions during concurrent CI/CD pipeline runs.

Adım Adım Çözüm

1
Identify key requirements for enterprise IaC state management
Requirements are environment isolation (dev/stage/prod), concurrency control (state locking), and state versioning/recovery.
Preventing accidental cross-environment modifications and corruption during concurrent CI/CD runs is essential.
2
Evaluate Google Cloud best practices for Terraform backends
Cloud Storage (GCS) provides remote backend functionality, built-in strong consistency, state locking, and versioning.
A separate GCS bucket per environment ensures strict logical and security boundaries using IAM permissions.
3
Compare against incorrect practices
Local storage, primitive IAM roles, and manual console edits introduce drift, security vulnerabilities, and state corruption risks.
Automation pipelines require minimal privileges and reproducible declarative execution without manual out-of-band interventions.

Anahtar Kavram

Terraform Remote Backend State Governance in Google Cloud
Bu soruyu puanla

Konular

Building and Managing Infrastructure as Code (IaC)

Bu konudan daha fazla soru