Which practice makes infrastructure changes auditable and reversible through version control and repeatable provisioning?

Which practice makes infrastructure changes auditable and reversible through version control and repeatable provisioning?

• A. Manual provisioning
• B. Infrastructure as Code (IaC)
• C. Runtime provisioning
• D. Ad-hoc scripting

Answer: (B)

Infrastructure as Code treats infrastructure as software, defining the desired environment in code that lives in version control. This approach makes changes auditable because every modification is captured as a commit with an author, timestamp, and message, providing a clear history of what changed and why. Reversibility comes from the ability to revert or roll back to a previous version of the code, or to re-apply an earlier state, effectively undoing unwanted changes. Repeatable provisioning follows because applying the code to provision resources should yield the same environment each time, assuming the tooling is idempotent and the code describes the desired state precisely. This combination—version-controlled, reproducible, and reversible infrastructure—is why Infrastructure as Code is the best fit. Manual provisioning lacks traceability and rollback; runtime provisioning happens at execution time without a reliable, versioned record; ad-hoc scripting can be versioned but often misses a unified, state-driven model and drift control that IaC provides.

Infrastructure as Code treats infrastructure as software, defining the desired environment in code that lives in version control. This approach makes changes auditable because every modification is captured as a commit with an author, timestamp, and message, providing a clear history of what changed and why. Reversibility comes from the ability to revert or roll back to a previous version of the code, or to re-apply an earlier state, effectively undoing unwanted changes. Repeatable provisioning follows because applying the code to provision resources should yield the same environment each time, assuming the tooling is idempotent and the code describes the desired state precisely. This combination—version-controlled, reproducible, and reversible infrastructure—is why Infrastructure as Code is the best fit. Manual provisioning lacks traceability and rollback; runtime provisioning happens at execution time without a reliable, versioned record; ad-hoc scripting can be versioned but often misses a unified, state-driven model and drift control that IaC provides.