CAPM Agile Frameworks and Methodologies Practice Question
An agile team is adopting Extreme Programming (XP). A developer asks how the practice of continuous integration differs from simply building the software nightly. Which statement best describes the XP practice of continuous integration?
⚠ Common exam trap
The trap here is equating continuous integration with nightly builds or end-of-iteration integration, which are far less frequent than the XP practice requires.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Code is integrated and tested multiple times per day, often with each commit.
XP continuous integration involves integrating and testing code many times a day, often with each commit. This provides rapid feedback and minimizes integration issues. The other options describe less frequent integration practices that do not align with XP's emphasis on continuous feedback and small batches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Code is integrated at the end of each iteration after a code freeze.
Why it's wrong here
A code freeze at the end of an iteration is a traditional practice, not XP continuous integration. XP advocates for continuous integration to avoid code freezes and long integration phases. This approach reduces the feedback loop and increases risk.
- ✗
Code is integrated only after all unit tests pass on the developer's machine.
Why it's wrong here
While passing unit tests locally is important, XP continuous integration requires integration into a shared repository frequently, not just local testing. Delaying integration until all tests pass locally can still lead to integration issues when multiple developers work in parallel.
- ✓
Code is integrated and tested multiple times per day, often with each commit.
Why this is correct
Continuous integration in XP means integrating and testing code many times a day, typically with every commit. This practice reduces integration problems and provides rapid feedback. Nightly builds are not frequent enough to catch issues early, which is a core XP value.
- ✗
Code is integrated once per sprint during the Sprint Review.
Why it's wrong here
Integrating only once per sprint is too infrequent and contradicts XP principles. XP emphasizes frequent integration to avoid long integration phases. Waiting until the Sprint Review would delay feedback and increase risk of conflicts, making this option incorrect.
Go deeper
Related to this question
About these practice questions
One of 451 original CAPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.