300-435 · Question #52
What should a CI/CD pipeline aim to achieve?
The correct answer is B. to require minimal manual interaction. A CI/CD pipeline's primary aim is to automate the software delivery process, requiring minimal manual interaction from development through deployment to increase speed, efficiency, and reliability.
Question
Exhibits
Options
- Ato allow manual testing before deployment
- Bto require minimal manual interaction
- Cto support new deployments on a fixed monthly schedule
- Dto provide a documented process for feedback
How the community answered
(41 responses)- A5% (2)
- B93% (38)
- D2% (1)
Why each option
A CI/CD pipeline's primary aim is to automate the software delivery process, requiring minimal manual interaction from development through deployment to increase speed, efficiency, and reliability.
While testing is crucial, CI/CD pipelines prioritize automated testing to ensure rapid feedback and consistency, aiming to minimize rather than simply allow manual testing before deployment.
A fundamental goal of a CI/CD pipeline is to automate the various stages of software delivery, from code integration and testing to deployment, thereby significantly reducing the need for manual interaction and potential human errors.
CI/CD pipelines are designed to enable frequent and often on-demand deployments, facilitating continuous delivery and rapid iteration, rather than being restricted to fixed or infrequent deployment schedules.
While providing a feedback loop is an important aspect of a healthy development process, the core aim of the CI/CD pipeline itself is the automation and continuous flow of software delivery, not merely documenting feedback.
Concept tested: CI/CD pipeline goals
Source: https://learn.microsoft.com/en-us/devops/develop/what-is-cicd
Topics
Community Discussion
No community discussion yet for this question.



