GCP Associate Cloud Engineer Practice Question

Your platform team uses Terraform to provision multiple Google Cloud projects. You need a shared Terraform state solution that

  • keeps a full history so you can roll back to any previous version,
  • prevents two engineers from accidentally updating the same state file at the same time, and
  • relies only on Google-managed services you already use. Which approach should you recommend?
  • Migrate to Terraform Cloud and use its remote backend to obtain state versioning and locking features.

  • Configure the gcs backend to store state in a Cloud Storage bucket that has object versioning enabled; the backend uses Cloud Storage generation numbers to lock the state during Terraform operations.

  • Keep the default local backend and commit the terraform.tfstate file to Cloud Source Repositories, relying on Git history for version control.

  • Use the s3 backend pointed at an interoperability-enabled Cloud Storage bucket and add a DynamoDB table to provide state locking.

GCP Associate Cloud Engineer
Planning and implementing a cloud solution
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot