Examkin

Question

Difficulty: MediumImplementing Infrastructure as Code using Terraform and Deployment Manager

A software development company is migrating its infrastructure management from local scripts to Terraform on Google Cloud. During continuous integration runs, multiple automated build workers occasionally attempt to apply changes to the same regional infrastructure concurrently, resulting in state file race conditions and loss of state revision history. Which remote backend strategy should the cloud architect implement to ensure safe concurrent execution and historical state recovery?

  1. Configure the Terraform backend to use a Cloud Storage bucket with Object Versioning enabled to support automatic state locking and state history preservation.Answer
  2. B
    Store the Terraform state file on an ephemeral local disk inside the build container and commit updated state files to a version-controlled Git repository after each execution.
  3. C
    Grant the primitive Owner role to the pipeline service account to enable it to forcibly overwrite locked state objects whenever lock contention occurs.
  4. D
    Grant the pipeline service account the Service Account Admin role so that it can dynamically provision per-execution lock management service accounts.

Answer

Configure the Terraform backend to use a Cloud Storage bucket with Object Versioning enabled to support automatic state locking and state history preservation.
The standard GCP solution for Terraform remote state storage is a Cloud Storage (GCS) bucket. The `gcs` backend natively handles state locking using Cloud Storage strongly consistent operations and object metadata locks, preventing parallel modifications. Enabling Object Versioning on the bucket ensures that all state changes create historical revisions, allowing administrators to recover previous states if needed.

Step-by-Step Solution

1
Identify the concurrency and state retention requirements
The requirement calls for distributed state locking during concurrent pipeline runs and historical version retention for recovery.
Preventing state corruption requires atomic locks, while preserving revision history protects against accidental state loss.
2
Evaluate Google Cloud Storage native capabilities with Terraform
The standard Google Cloud Storage backend (`gcs`) automatically uses Cloud Storage object locks to prevent concurrent modifications.
Cloud Storage handles state locking natively without requiring additional external locking mechanisms like DynamoDB.
3
Enable Object Versioning on the Cloud Storage bucket
Enabling versioning on the Cloud Storage bucket ensures that every state modification creates a new object version.
Object versioning allows rollback to previous state files if a deployment corrupted or misplaced state data.

Key Concept

Terraform Remote State Management and Cloud Storage Locking
Rate this question

Topics

Implementing Infrastructure as Code using Terraform and Deployment Manager

More questions from this topic