CAPM Practice Question: Project Management Fundamentals and Core Concepts
A project manager is leading a software development project. During a team meeting, a team member suggests adding a new feature that was not in the original scope. The project manager wants to evaluate the impact of this change on the project constraints. Which document should the project manager consult first to understand the baseline scope?
⚠ Common exam trap
The trap here is selecting the WBS because it breaks down work, but it lacks the narrative scope description needed for change impact analysis.
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
✓
Project scope statement
The project scope statement is the correct document because it defines what is included in the project and what is excluded, along with assumptions and constraints. It serves as the baseline for scope and is essential for evaluating proposed changes. Other documents like the WBS, requirements management plan, or project charter do not provide the same level of detail for scope baseline evaluation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Project charter
Why it's wrong here
The project charter formally authorizes the project and provides high-level information, but it does not contain the detailed scope baseline. While it may list high-level requirements, it is not the document to consult for evaluating a change's impact on scope. The project scope statement is more appropriate for this purpose.
- ✗
Work breakdown structure
Why it's wrong here
The work breakdown structure (WBS) is a hierarchical decomposition of the total scope of work. While it helps identify deliverables and work packages, it does not provide the detailed scope description, assumptions, and constraints that the project scope statement does. The project manager needs the scope statement to evaluate the change's impact on scope, not just the WBS.
- ✓
Project scope statement
Why this is correct
The project scope statement describes the project scope, major deliverables, assumptions, and constraints. It provides the baseline for evaluating changes. In this scenario, the project manager should consult the project scope statement first to understand what is included and excluded, and to assess the impact of the proposed new feature on the project constraints.
- ✗
Requirements management plan
Why it's wrong here
The requirements management plan describes how requirements will be analyzed, documented, and managed. It is a component of the project management plan but does not define the baseline scope. In this scenario, the project manager needs to understand the current scope baseline, which is best found in the project scope statement, not the requirements management plan.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.