Examkin

Soru

Zorluk: OrtaInfrastructure as Code and Environment Provisioning

A game development studio provisions isolated, short-lived game server fleets across multiple Google Cloud regions using Terraform pipelines. Multiple automated build jobs running concurrently frequently fail due to state file locking collisions and state corruption when attempting to write to the local directory before uploading state. Which approach should the cloud architecture team implement to ensure reliable, concurrent environment provisioning and state integrity?

  1. Configure a Cloud Storage remote backend with state locking and object versioning enabled.Cevap
  2. B
    Store the Terraform state locally within each ephemeral pipeline worker and upload it to a Cloud Storage bucket upon completion without versioning.
  3. C
    Grant the primitive Owner role to the pipeline service account to bypass Cloud Storage object locking restrictions.
  4. D
    Instruct developers to resolve state locking collisions by manually updating resources via Google Cloud Console and forcing state refresh.

Cevap

Configure a Cloud Storage remote backend with state locking and object versioning enabled.
Configuring a Google Cloud Storage remote backend with object locking and versioning ensures that concurrent execution jobs lock state during operations, preventing simultaneous updates and corruption while maintaining continuous environment reliability.

Adım Adım Çözüm

1
Identify the root cause of state locking collisions and state corruption during parallel pipeline executions.
Recognized that local or uncoordinated state management leads to race conditions when multiple Terraform processes execute simultaneously.
Infrastructure as Code pipelines require centralized, synchronized state management to coordinate concurrent environment provisioning.
2
Evaluate Google Cloud architecture best practices for Terraform state backends.
Selected Cloud Storage as a remote backend supporting native strong consistency and state locking.
Google Cloud Storage natively provides object locking and strong consistency to prevent parallel workers from corrupting state.
3
Enable object versioning on the designated Cloud Storage bucket.
Established point-in-time recovery capabilities for infrastructure state history.
Bucket versioning allows rollback to previous state snapshots if unintended state modifications occur.

Anahtar Kavram

Centralized remote state management with backend locking and versioning for Infrastructure as Code reliability
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Infrastructure as Code and Environment Provisioning