CAPM Predictive Plan-Based Methodologies Practice Question
During the planning phase of a predictive project, the project manager wants to define the project scope more precisely. Which process should be used to develop a detailed description of the project and product?
⚠ Common exam trap
The trap is confusing Define Scope with Collect Requirements: candidates see 'detailed description of the project and product' and think of requirements gathering, but the key output of Define Scope is the project scope statement, which precisely defines boundaries.
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
✓
Define Scope
Define Scope is the process of developing a detailed description of the project and product, producing the project scope statement. It takes the requirements documentation and project charter as inputs and defines what is included and excluded from the project. This is exactly what the project manager needs to precisely define scope during planning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Define Scope
Why this is correct
Define Scope produces the detailed project and product description, plus the scope statement, by elaborating on the deliverables and boundaries recorded during initiation. It directly satisfies the stem's demand for a more precise scope during planning, distinguishing it from Collect Requirements, which gathers stakeholder needs rather than documenting the project and product description itself.
- ✗
Collect Requirements
Why it's wrong here
Collect Requirements elicits and documents stakeholder needs, producing requirements documentation rather than the detailed project and product description the stem requests. It is tempting because requirements feed that description, but the process that formally develops the project scope statement and product description is Define Scope.
- ✗
Create WBS
Why it's wrong here
Create WBS decomposes the already-defined scope into deliverables and work packages; it does not produce the detailed project and product description. It is tempting because the WBS sits in the Scope Management knowledge area, but the process that generates the scope statement and requirements documentation is Collect Requirements.
- ✗
Validate Scope
Why it's wrong here
Validate Scope occurs in Monitoring and Controlling, formalising acceptance of completed deliverables; it cannot define scope during planning. It is tempting because its name suggests scope definition, but the process producing the detailed project and product description during planning is Define Scope.
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.