GCP Associate Cloud Engineer Practice Question 66: IAC Terraform Infrastructure Manager
Google Cloud Associate Cloud Engineer · Test 7 · question 6 of 10
A platform team currently creates Compute Engine VMs, VPC subnets, and Cloud SQL instances by running gcloud commands from engineers' laptops. Configurations often drift between environments because changes are not tracked anywhere. The team wants to define all of this infrastructure in version-controlled Terraform configuration files stored in a Git repository, have Google Cloud apply those configurations as managed deployments, and be able to preview changes before they are applied, without standing up and operating their own Terraform runner.
What should they do?
Show answer and explanation
Answer:
Infrastructure Manager (Infra Manager) is Google Cloud's managed service for infrastructure as code. It takes Terraform configurations stored in a Cloud Storage bucket, a Git repository, or a local directory, applies them as a tracked deployment, keeps a revision history with the state file for each revision, and can generate a preview of a change before it is applied, all without the team having to run and secure its own Terraform execution environment.
B is wrong because Cloud Deployment Manager uses its own YAML and Jinja or Python template format, not Terraform, and Google has deprecated the service and its support ended on March 31, 2026, so it is not a suitable answer for new, ongoing infrastructure management. C is wrong because scripting gcloud commands in a Cloud Build pipeline is still imperative automation: it does not give declarative state tracking, drift detection, or a change preview the way Terraform and Infra Manager do. D is wrong because manually running Terraform from a shared bastion host still leaves state handling, credentials, and execution to the team to operate themselves, which is exactly the operational burden they want to avoid.
Reference: Infrastructure Manager overview