nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #15

Your team of Infrastructure DevOps Engineers is growing, and you are starting to use Terraform to manage infrastructure. You need a way to implement code versioning and to share code with other team…

The correct answer is A. Store the Terraform code in a version-control system. Establish procedures for pushing new. For a growing team using Terraform, storing the code in a version-control system like Git and establishing push procedures is the best way to implement versioning and sharing.

Submitted by kevin_r· Apr 18, 2026Building and implementing CI/CD pipelines for a service

Question

Your team of Infrastructure DevOps Engineers is growing, and you are starting to use Terraform to manage infrastructure. You need a way to implement code versioning and to share code with other team members. What should you do?

Options

  • AStore the Terraform code in a version-control system. Establish procedures for pushing new
  • BStore the Terraform code in a network shared folder with child folders for each version release.
  • CStore the Terraform code in a Cloud Storage bucket using object versioning. Give access to the
  • DStore the Terraform code in a shared Google Drive folder so it syncs automatically to every team

How the community answered

(31 responses)
  • A
    71% (22)
  • B
    3% (1)
  • C
    10% (3)
  • D
    16% (5)

Why each option

For a growing team using Terraform, storing the code in a version-control system like Git and establishing push procedures is the best way to implement versioning and sharing.

AStore the Terraform code in a version-control system. Establish procedures for pushing newCorrect

A version-control system (VCS) like Git is the industry standard for collaborative code management, providing essential features for Infrastructure as Code (IaC) with Terraform, including tracking changes, enabling multiple team members to work concurrently, merging changes, creating branches, and maintaining a complete history for auditing and rollbacks.

BStore the Terraform code in a network shared folder with child folders for each version release.

A network shared folder with child folders for versions lacks the robust collaboration features of a VCS, such as granular change tracking, merging, branching, and conflict resolution, making it unsuitable for a growing team.

CStore the Terraform code in a Cloud Storage bucket using object versioning. Give access to the

While Cloud Storage with object versioning can store files and track changes, it doesn't offer the collaborative capabilities (like branching, merging, pull requests, diffing) that a VCS provides, which are critical for team-based code development.

DStore the Terraform code in a shared Google Drive folder so it syncs automatically to every team

A shared Google Drive folder, while offering syncing, also lacks the specific code versioning and collaboration features (like proper branching, merging, diffing, and conflict resolution mechanisms) that a VCS is designed for.

Concept tested: Infrastructure as Code, version control, collaborative development

Source: https://developer.hashicorp.com/terraform/tutorials/git/git-get-started

Topics

#Terraform#Version Control System#Infrastructure as Code#Code Collaboration

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice