An enterprise is establishing an Infrastructure as Code (IaC) strategy on Google Cloud to manage multi-tier compute workloads across development, testing, and production environments. The infrastructure team has outlined the following technical requirements: Standardize and reuse compute infrastructure configurations across multiple environments using parameterized, modular templates Prevent configuration drift and avoid accidental resource destruction by maintaining a persistent mapping between configuration code and real-world Google Cloud resources Maintain an auditable history of infrastructure modifications, enforce peer reviews, and enable reliable rollbacks Which operational approach best fulfills these requirements?

Store declarative Terraform configurations in a Git repository, package standardized compute topologies into reusable Terraform modules, and maintain remote state in Cloud Storage buckets: ### What Terraform and Declarative IaC Are **HashiCorp Terraform** is a declarative Infrastructure as Code (IaC) tool that lets platform engineers define, provision, and manage Google Cloud infrastructure using **HashiCorp Configuration Language (HCL)**. Declarative configurations describe the intended end-state of infrastructure rather than sequential execution scripts. ### How It Meets the Requirements - **Modular Templates**: Terraform **modules** encapsulate collections of compute resources (such as Compute Engine VMs, Managed Instance Groups, firewalls, and VPC subnets) into reusable, parameterized building blocks. This standardizes infrastructure definitions across development, test, and production environments. - **State Management**: Terraform generates and maintains a **state file** (`terraform.tfstate`), typically stored centrally in a secure **Cloud Storage bucket backend**. The state file maps declared configuration objects to real-world cloud resources, tracks metadata, detects configuration drift, and allows Terraform to determine necessary creates, updates, and destroys during `terraform plan` and `terraform apply` operations. - **Version Control & Auditing**: Storing Terraform configurations in a **Git repository** enables formal pull-request peer reviews, comprehensive audit trails, integration with automated CI/CD pipelines (such as Cloud Build), and simplified rollbacks to known-good infrastructure states. ### Key Advantages - **Execution Plan Review**: The `terraform plan` command provides visibility into pending infrastructure changes before modifications are applied to live environments. - **Consistency & Reusability**: Parameterized modules eliminate configuration duplication across multi-environment deployments. - **Drift Detection**: Automatic reconciliation between local manifests, the remote state file, and deployed resources. - **Team Collaboration**: Remote state backends support state locking to avoid concurrent execution conflicts across distributed teams. ### Why This Is Optimal This approach combines reusable architectural templates, strict state tracking, and source control governance, providing the highest level of repeatability, security, and lifecycle management for Google Cloud infrastructure.

StudyCerts

Iac Terraform Modules State Management Version Control | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Iac Terraform Modules State Management Version Control

Section: Infrastructure orchestration, resource configuration, and patch management

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise is establishing an Infrastructure as Code (IaC) strategy on Google Cloud to manage multi-tier compute workloads across development, testing, and production environments.

The infrastructure team has outlined the following technical requirements:

Standardize and reuse compute infrastructure configurations across multiple environments using parameterized, modular templates
Prevent configuration drift and avoid accidental resource destruction by maintaining a persistent mapping between configuration code and real-world Google Cloud resources
Maintain an auditable history of infrastructure modifications, enforce peer reviews, and enable reliable rollbacks

Which operational approach best fulfills these requirements?

Use configuration management tools like Ansible or Puppet to imperatively build VM instances, without external state files or cloud provider plugins

Store declarative Terraform configurations in a Git repository, package standardized compute topologies into reusable Terraform modules, and maintain remote state in Cloud Storage buckets

Author shell scripts utilizing the Google Cloud CLI (gcloud) committed to Git, and run imperative scripts directly against each target environment

Manually create golden machine images in the Google Cloud console for each environment and deploy Compute Engine instances from the console UI

Professional Cloud Architect

Iac Terraform Modules State Management Version Control

Related questions