An organization's Chief Technical Officer is concerned that changes to the network using IaC are causing unscheduled outages. Which of the following best mitigates this risk?
A.
Making code changes to the master branch
B.
Enforcing code review of the change by the author
C.
Forking the code repository before making changes
D.
Adding review/approval steps to the CI/CD pipelines
Comprehensive and Detailed Explanation From Exact Extract:
The best way to prevent unscheduled outages caused by Infrastructure as Code (IaC) changes is to implement automated review and approval gates in the CI/CD pipeline. This ensures that all changes undergo validation, peer review, testing, and possibly approval from stakeholders before being deployed, thus reducing the likelihood of production-impacting issues.
Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “CI/CD Security and IaC Controls”:
“Incorporating approval gates and automated validation into CI/CD pipelines helps detect misconfigurations and unauthorized changes before deployment, reducing the risk of outages.”
Other options:
A. Making changes directly to the master branch violates best practices.
B. Self-review (by the author) lacks objectivity and fails peer validation.
C. Forking creates a copy but does not introduce formal validation processes.
================================================
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit