PMPRocket
PMP Practice QuestionsScope Management
Process Domain

Scope Management PMP Practice Questions

Test yourself with 7 free, scenario-based PMP practice questions on scope management, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Question 1 of 7

Halfway through a predictive project, a stakeholder requests a significant new feature not included in the project charter. The feature would add three weeks to the schedule. What should you do FIRST?

  1. A.Submit the request through the integrated change control process for evaluation
  2. B.Add the feature now to keep the stakeholder satisfied
  3. C.Reject the request because the scope was already agreed upon
  4. D.Add the feature and compress the remaining schedule to absorb the impact
Show answer and explanation

Correct answer: A

All scope changes on a predictive project must go through integrated change control. This ensures the impact on schedule, cost, risk, and quality is formally evaluated before a decision is made. Adding without process (A, D) is scope creep. Outright rejection ignores the stakeholder's legitimate request and bypasses the proper process.

Question 2 of 7

A requirements traceability matrix links requirements to which project artifacts to ensure completeness and traceability?

  1. A.Risk register and change log only
  2. B.Stakeholder register and communication management plan
  3. C.Business needs, project objectives, WBS deliverables, test cases, and final product
  4. D.Project charter and project management plan only
Show answer and explanation

Correct answer: C

A requirements traceability matrix (RTM) provides a bidirectional link from each requirement to its source (business need, stakeholder request) through design, development, testing, and delivery. This ensures every requirement is tested and that every test case traces back to a requirement. The RTM helps prevent scope creep (tracing new requirements to approved business needs) and validates completeness (every requirement has been addressed). It is a critical quality and scope management tool.

Question 3 of 7

What is the scope baseline, and what three documents does it comprise?

  1. A.The project charter, stakeholder register, and requirements documentation — these three documents define the project's authorization, stakeholder commitments, and formally agreed deliverables.
  2. B.The project management plan, scope management plan, and requirements traceability matrix — these integrated planning documents together define how scope will be planned, managed, and verified.
  3. C.The WBS, activity list, and project schedule baseline — these three documents together define the decomposed project scope, all required activities, and the planned delivery timeline.
  4. D.The approved scope statement, WBS, and WBS dictionary — used as the reference for measuring and controlling scope performance.
Show answer and explanation

Correct answer: D

The scope baseline consists of three documents: (1) the approved project scope statement — describing what is and is not included; (2) the WBS — hierarchical decomposition of all project deliverables; and (3) the WBS dictionary — detailed descriptions of each WBS component including acceptance criteria. Together these define and control what the project will produce. Changes to the scope baseline require formal change control. The scope baseline is one of three performance baselines, along with the schedule and cost baselines.

Question 4 of 7

On an agile project, how is scope defined and managed differently compared to a predictive project?

  1. A.In agile, scope emerges progressively through the product backlog — the overall feature set is defined at a high level initially and elaborated sprint by sprint, with the product owner continuously prioritizing.
  2. B.Scope is fixed and detailed upfront in both agile and predictive projects — the difference is only in how work is sequenced and delivered, not in how comprehensively scope is defined at the outset.
  3. C.Agile projects have no formal scope management since the core principle of welcoming change means that scope boundaries are intentionally left open and any request can be prioritized at any time.
  4. D.In agile, the scope baseline is locked at the start of each sprint and cannot change mid-sprint; new requests are added to the backlog and prioritized for a future sprint by the product owner.
Show answer and explanation

Correct answer: A

Agile manages scope progressively. High-level epics and features are defined at the start, but detailed requirements (user stories) are elaborated 'just in time' through backlog refinement. The product backlog serves as the living scope document — it can grow, shrink, and reprioritize. Within a sprint, the sprint scope (selected stories) is stabilized. Agile does welcome scope changes — but through the backlog prioritization process, not without governance. The product owner actively manages scope to maximize value delivered.

Question 5 of 7

A project manager is conducting scope validation. A deliverable meets all technical specifications but the customer refuses to formally accept it. What should the project manager do FIRST?

  1. A.Invoke the contract clause requiring acceptance upon technical specification compliance — the contract terms establish the legal obligation to accept, and the customer's refusal is a contractual breach.
  2. B.Understand why the customer will not accept the deliverable — clarify expectations and determine if there is a gap between specifications and actual business needs.
  3. C.Escalate to senior management to compel the customer to accept the deliverable — executive-level intervention from the buyer's organization can override objections and enforce contractual compliance.
  4. D.Issue a formal change request to modify the deliverable to satisfy the customer — customer acceptance is the ultimate success criterion, and adjusting the deliverable to meet actual needs is the right outcome.
Show answer and explanation

Correct answer: B

Before escalating or invoking contract clauses (A, C), the project manager should understand the customer's concerns. There may be a legitimate gap: the deliverable meets technical specs but fails to meet unstated or poorly documented business needs — a classic requirements elicitation failure. Understanding the rejection reason informs the correct path forward: modify requirements, negotiate acceptance, or pursue dispute resolution. Immediately issuing a change request assumes modifications are needed before understanding the problem.

Question 6 of 7

Which of the following are components of the requirements documentation? (Select THREE)

Select all that apply.

  1. A.Business requirements — the higher-order business need being addressed
  2. B.Stakeholder requirements — needs and expectations of stakeholder groups
  3. C.Resource assignments — who will work on each requirement
  4. D.Solution requirements — functional and nonfunctional requirements for the product
  5. E.Transition requirements — what is needed to move from the current to future state
Show answer and explanation

Correct answers: A and B and D

Requirements documentation (A, B, D) includes: business requirements — the organizational need or opportunity the project addresses; stakeholder requirements — what stakeholders need from the solution; and solution requirements — both functional (what the system does) and nonfunctional (how well it does it: performance, security, usability). Transition requirements (E) describe what is needed to implement the solution (training, migration) and are sometimes included but not universally listed as a core component. Resource assignments belong to the resource management plan, not requirements documentation.

Question 7 of 7

A scope statement is being developed for a new IT infrastructure project. Which element is MOST important to include to prevent disputes later?

  1. A.A detailed resource list of who will work on the project
  2. B.Project exclusions — explicit statements of what is NOT included in the project scope
  3. C.The project sponsor's biography and decision-making authority
  4. D.A preliminary project schedule with milestone dates
Show answer and explanation

Correct answer: B

Project exclusions are one of the most valuable elements of a scope statement for preventing future disputes. By explicitly stating what is NOT in scope (e.g., 'This project does not include end-user training,' 'Network security is managed by the InfoSec team'), the project manager sets clear boundaries. Without explicit exclusions, stakeholders may assume unlisted items are included, leading to scope creep and conflicts. Exclusions document mutual agreement about boundaries — preventing scope arguments later.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

Start Interactive PracticeTry the PMP Mock Exam

More Process practice questions

Risk Management (21)Quality Management (18)Integration Management (16)Resource Management (16)Earned Value Management (12)Schedule Management (11)