Explanation:
The correct approach for implementing code versioning and sharing Terraform code with a growing team involves using a system that supports collaboration, version history, and controlled access. Option A is the best solution because it leverages a version-control system (like Git) which inherently handles versioning, branching, merging, and collaboration. Establishing procedures for pushing new versions and merging ensures consistency and reduces conflicts. In contrast:
Ultimate access to all questions.
How can your Infrastructure DevOps team implement version control and share Terraform code effectively as the team grows?
A
Store the Terraform code in a version-control system. Establish procedures for pushing new versions and merging with the master.
B
Store the Terraform code in a network shared folder with child folders for each version release. Ensure that everyone works on different files.
C
Store the Terraform code in a Cloud Storage bucket using object versioning. Give access to the bucket to every team member so they can download the files.
D
Store the Terraform code in a shared Google Drive folder so it syncs automatically to every team member's computer. Organize files with a naming convention that identifies each new version.
No comments yet.