Infrastructure as Code (IaC) can be stored in a version control system along with application code.

Infrastructure as Code (IaC) can be stored in a version control system along with application code.

• A. False
• B. True
• C. Sometimes, depending on policy
• D. Not recommended

Answer: (B)

Storing Infrastructure as Code in a version control system alongside application code is a best practice because IaC is code that defines infrastructure and benefits from the same governance and collaboration processes as application code. Version control provides a history of changes, clear authorship, and the ability to review and approve modifications before they are applied. It enables reproducible environments: you can checkout a specific commit to provision infrastructure that matches a particular app version, which is essential for reliable deployments and consistent staging, testing, and production environments. Branching and pull requests allow safe experimentation and feature-driven infrastructure changes, while integration with CI/CD pipelines makes provisioning part of automated deployment workflows. Text-based IaC files are easily diffed, merged, and audited, supporting traceability and rollback if needed. While some policies might influence how repositories are organized, the practical approach is to keep IaC under version control to ensure alignment with application lifecycles and governance.

Storing Infrastructure as Code in a version control system alongside application code is a best practice because IaC is code that defines infrastructure and benefits from the same governance and collaboration processes as application code. Version control provides a history of changes, clear authorship, and the ability to review and approve modifications before they are applied. It enables reproducible environments: you can checkout a specific commit to provision infrastructure that matches a particular app version, which is essential for reliable deployments and consistent staging, testing, and production environments. Branching and pull requests allow safe experimentation and feature-driven infrastructure changes, while integration with CI/CD pipelines makes provisioning part of automated deployment workflows. Text-based IaC files are easily diffed, merged, and audited, supporting traceability and rollback if needed. While some policies might influence how repositories are organized, the practical approach is to keep IaC under version control to ensure alignment with application lifecycles and governance.