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

Question

Options

• AContinuous integration
• BContinuous delivery
• CContinuous deployment
• DContinual improvement

• A
  79% (15)
• B
  5% (1)
• C
  11% (2)
• D
  5% (1)

Explanation

Continuous Integration (CI) directly addresses the problem of developers working in isolated repositories. CI is the practice of frequently merging all developers' code changes into a single shared repository, where automated builds and tests run - eliminating the costly "integration hell" that occurs when siloed code is finally combined.

Why the distractors are wrong:

• B (Continuous Delivery) ensures software is always in a releasable state after CI has occurred - it's a downstream step, not the fix for isolated repos.
• C (Continuous Deployment) goes further by automatically pushing every passing change to production - again, it assumes integration has already happened.
• D (Continual Improvement) is a broad management philosophy (common in ITIL) about incrementally improving processes over time - not a specific development practice for merging code.

Memory tip: Focus on the keyword in the problem - developers are not integrating their code. Match the pain point to the word: no integration → need Continuous Integration. If the question describes a deployment or release delay after code is already merged, then look at B or C instead.

No community discussion yet for this question.