What option aligns to the 'traditional' workflow of a CI/CD pipeline, where 'D' in CI/CD stands for Deployment?

• A. Plan, Code, Build, Deploy
• B. Build, Testing, Release, Deployment
• C. Code, Build, Test, Deliver
• D. Design, Build, Test, Deploy

Answer: (B)

In a traditional CI/CD flow, the pipeline moves a change from building into production in a clear, automated sequence: create a build from code, verify it with tests, prepare and promote the release, and finally deploy the artifact to the target environment. This ordering emphasizes that only validated builds are promoted and eventually deployed, with Deployment as the final step in the chain.

The sequence that fits this pattern is the one that starts with building the artifact, then runs tests to ensure quality, then moves to a release phase to package and prepare the artifact, and ends with deployment to production. This aligns with the idea that the last stage is Deployment, after verification and promotion. The other options either start with non-operational planning or design activities, or swap in non-standard terms like Deliver, which don’t reflect the conventional deployment step, or place code at the start in a way that doesn’t mirror the typical automated pipeline from building to deploying.