Which statement correctly describes the intended order of the package development lifecycle?

Which statement correctly describes the intended order of the package development lifecycle?

• A. Code, Continuous integration, Continuous delivery, Continuous delivery release
• B. Code, Continuous delivery, Continuous integration, Release
• C. Code, Continuous integration, Continuous delivery, Continuous delivery release
• D. Code, Release, Continuous integration, Continuous Delivery

Answer: (C)

The sequence being tested is how changes progress from development to production. Start with coding and submitting those changes. Continuous integration then builds and runs automated tests for every change to catch integration issues early. After that, continuous delivery takes over, packaging and preparing the code so it’s in a deployable state and can be released to a staging or pre-production environment. Finally, release moves the validated, packaged software into production, which can be automated or controlled. This ordering—Code, Continuous Integration, Continuous Delivery, Release—reflects a logical flow where each stage relies on the previous one having verified and prepared changes. The other options either try to release or deploy before proper integration and validation, or duplicate stages, which would undermine reliability and quality.

The sequence being tested is how changes progress from development to production. Start with coding and submitting those changes. Continuous integration then builds and runs automated tests for every change to catch integration issues early. After that, continuous delivery takes over, packaging and preparing the code so it’s in a deployable state and can be released to a staging or pre-production environment. Finally, release moves the validated, packaged software into production, which can be automated or controlled.

This ordering—Code, Continuous Integration, Continuous Delivery, Release—reflects a logical flow where each stage relies on the previous one having verified and prepared changes. The other options either try to release or deploy before proper integration and validation, or duplicate stages, which would undermine reliability and quality.