An organization experiences delays when creating and changing products and services. This is largely because software developers store code in their individual repositories. Which approach would…

Question

Options

• AContinuous integration
• BContinuous delivery
• CContinuous deployment
• DChange enablement

• A
  89% (25)
• C
  4% (1)
• D
  7% (2)

Explanation

Continuous Integration (CI) directly solves this problem because it requires developers to merge code into a shared central repository frequently - often multiple times per day - with automated builds and tests validating each merge. This eliminates the "integration hell" that occurs when isolated individual repositories diverge over time, causing costly conflicts and delays when teams eventually try to combine their work.

Why the distractors are wrong:

• B (Continuous Delivery) assumes integration has already happened - it focuses on keeping code in a releasable state, not on merging isolated repositories together.
• C (Continuous Deployment) goes one step further than CD by automating production releases; it's also downstream of the integration problem, not a solution to it.
• D (Change Enablement) is an ITIL governance practice for managing risk around changes to live services - it's a process/approval framework, not a developer workflow practice.

Memory tip: Think of the word "Integration" - CI is literally about integrating (combining) code from many developers into one shared place. If the problem mentions siloed/individual repositories or merge conflicts, CI is your answer.

No community discussion yet for this question.