DEVSECOPS practice question 5 of 10

Which or the following BEST describes the proper order of the main stages of continuous integration and the continuous delivery?

Full set: 39 questions
Answer options
A: Develop commit, build, lest provision release, and deploy
B: Design, develop build test, provision deploy and release Correct answer
C: Develop commit, build test provision deploy and release
D: Design develop build test provision release and deploy
Correct Answer:
B. Design, develop build test, provision deploy and release
Explanation

This option provides the most complete and logical sequence for a modern software development lifecycle incorporating CI/CD. It begins with the pre-development 'Design' phase. The CI/CD pipeline proper starts with 'Develop', 'Build', and 'Test'. 'Provision' prepares the necessary infrastructure. The sequence 'Deploy' then 'Release' reflects the modern best practice of decoupling deployment (placing code in production) from release (making features available to users), which enhances control and reduces risk.

Why Incorrect

A. This option contains a typo ("lest" for "test") and presents a less common sequence of release/deploy compared to the modern decoupled approach.
C. This option omits the critical 'Design' phase, making it a less complete description of the overall process from concept to delivery.
D. This option places 'release' before 'deploy'. While valid in a traditional sense (creating a release artifact), it doesn't reflect the modern, risk-reducing pattern of decoupling.

References

1. Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional. (Chapter 1 introduces the core concepts, and later chapters on deployment patterns discuss the separation of deploying code from releasing features to users).

2. Fowler, M. (2017). Feature Toggles (aka Feature Flags). martinfowler.com. (This article, from a highly reputable source in software engineering, explicitly details the practice of deploying code to production behind a toggle and then "releasing" it to users separately, supporting the 'deploy' then 'release' order).

Scroll to Top