In software projects/engineering, CI/CD is a name that is often mentioned. In the following description about CI/CD, which one is wrong?

Question

Options

• AContinuous Deployment: Continuous Deployment extends Continuous Documentation so that a
• BContinuous Delivery: Continuous delivery can release verified code to a repository (such as
• CContinuous Integration: With continuous integration, developers are able to make multiple
• DContinuous integration Through continuous integration, developers need to submit content

• A
  6% (2)
• B
  3% (1)
• C
  12% (4)
• D
  79% (27)

Explanation

Option D is wrong because it misrepresents what Continuous Integration requires of developers. CI is a practice that enables developers to integrate code changes into a shared repository frequently and automatically - it does not impose a restrictive obligation about submitting content in any particular or limiting way. The core principle is that frequent, small integrations trigger automated builds and tests, catching issues early.

Option A is correct: Continuous Deployment extends Continuous Delivery (not "Documentation" - that appears to be a typo in the question) by automatically deploying every passing build to production without manual intervention. Option B is correct: Continuous Delivery ensures that verified code is always in a releasable state and can be pushed to a repository or staging environment on demand. Option C is correct: CI allows and encourages developers to make multiple small code integrations throughout the day rather than merging large, infrequent changes.

Memory tip: Remember the pipeline order - Integration feeds Delivery feeds Deployment. CI is about removing barriers to frequent merging, not adding them. Any answer that says developers "must" or "need to" do something restrictive under CI is a red flag for a wrong answer.

No community discussion yet for this question.