Question

Your platform team manages all Google Cloud infrastructure with Terraform, executed from a shared CI/CD pipeline. Recently, two concurrent pipeline runs triggered by near-simultaneous merges corrupted the Terraform state, leaving resources in an inconsistent condition. You need to prevent concurrent applies from corrupting state while keeping state durable and centrally accessible to the team. What should you configure?

Accepted Answer

Store the Terraform state in a Cloud Storage bucket backend, which provides built-in state locking, and enable object versioning on the bucket.

Answer

Keep the state file in the CI/CD runner's local workspace and archive it as a pipeline artifact after each run.

Answer

Store the state in a Cloud Storage bucket and add a manual approval gate before every apply so only one engineer runs Terraform at a time.

Answer

Commit the Terraform state file to the Git repository so version control history prevents concurrent modifications.