What is the primary benefit of using a provisioning pipeline with version control and code reviews?

What is the primary benefit of using a provisioning pipeline with version control and code reviews?

• A. Manual ticketing only
• B. Provisioning pipeline with version control and code reviews
• C. Checklist-based configuration
• D. Replacing instances with larger types

Answer: (B)

A provisioning pipeline with version control and code reviews provides a controlled, auditable, and repeatable way to change infrastructure. When infrastructure as code lives in version control, every change has a documented history and reasoning, and a reviewer can catch issues before anything is deployed. The pipeline automates validation, planning, and applying changes, ensuring consistent deployments across environments and reducing drift and manual errors. It also makes rollback straightforward by re-applying a previous version. Manual ticketing lacks automated traceability; checklist-based configuration can be error-prone and hard to enforce consistently; and replacing instances with larger types doesn’t address governance or reproducibility.

A provisioning pipeline with version control and code reviews provides a controlled, auditable, and repeatable way to change infrastructure. When infrastructure as code lives in version control, every change has a documented history and reasoning, and a reviewer can catch issues before anything is deployed. The pipeline automates validation, planning, and applying changes, ensuring consistent deployments across environments and reducing drift and manual errors. It also makes rollback straightforward by re-applying a previous version.

Manual ticketing lacks automated traceability; checklist-based configuration can be error-prone and hard to enforce consistently; and replacing instances with larger types doesn’t address governance or reproducibility.