Try 10 focused APM PFQ questions on Project Scope Management, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | APM PFQ |
| Topic area | Project Scope Management |
| Blueprint weight | 14% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Project Scope Management for APM PFQ. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 14% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Understand Project Scope Management
In a project’s change control process, what is the purpose of assessing a proposed change before a decision is made?
Best answer: C
What this tests: Understand Project Scope Management
Explanation: In change control, assessment is used to understand the likely impact of a proposed change before a decision is taken. This supports informed approval, rejection, or deferral rather than changing the project without understanding the consequences.
A key stage in change control is assessing the proposed change to understand what it would mean for the project. This typically includes considering effects on scope, schedule, cost, resources, risk, and benefits so that an informed decision can be made. The purpose is not simply to log the request or update records; it is to evaluate the consequences before authorising any alteration to the agreed baseline.
This differs from configuration management, which focuses on identifying, recording, and tracking the status and versions of project products. It also differs from quality control, which checks deliverables against quality criteria, and from responsibility assignment, which clarifies who does the work.
The key point is that change assessment supports controlled decision-making about proposed changes.
Assessing a proposed change helps decision-makers judge its effect on the project so they can approve, reject, or defer it on an informed basis.
Topic: Understand Project Scope Management
Which term describes a hierarchical structure that illustrates the work needed to deliver a project’s scope?
Best answer: B
What this tests: Understand Project Scope Management
Explanation: A work breakdown structure (WBS) is used to break the project scope into manageable pieces of work. It shows what work must be done, not who does it or how the organisation is arranged.
A work breakdown structure is a hierarchical decomposition of the total work required to deliver the project’s agreed scope. At PFQ level, its purpose is to make the required work visible and manageable by breaking it down into smaller elements, often to work-package level. This helps planning, estimating, assigning responsibilities, and controlling scope.
A product breakdown structure focuses on the products or outputs to be created, not the work itself. An organisational breakdown structure shows how people or teams are arranged. A responsibility assignment matrix links work to responsible roles. The key distinction is that the WBS illustrates the work needed to deliver scope.
A work breakdown structure shows the work packages and tasks needed to deliver the agreed project scope.
Topic: Understand Project Scope Management
A project manager needs a simple way to show which role is responsible for each defined work package in a project. Which artifact best meets this need?
PBS)OBS)RAM)WBS)Best answer: C
What this tests: Understand Project Scope Management
Explanation: A responsibility assignment matrix is used when the project needs to map work to accountability. It connects defined work packages or activities with the people or roles responsible for carrying them out or overseeing them.
The core concept is matching the project need to the right scope-management artifact. When the need is to show who is responsible for each work package, the correct choice is a responsibility assignment matrix (RAM). A RAM combines work information with responsibility information so the team can see clear ownership.
A WBS breaks the project work into smaller parts, but it does not by itself show responsibility. An OBS shows the organisational structure or roles involved, but not which role is assigned to each work package. A PBS focuses on the products or deliverables to be created. The key distinction is that only a RAM explicitly links work to responsibility.
A RAM links work packages or activities to the roles or people responsible for them.
Topic: Understand Project Scope Management
A project has approved scope and deliverable specifications. Which option contains the situations that should follow the agreed change control process?
Best answer: A
What this tests: Understand Project Scope Management
Explanation: Agreed change control is used for proposed changes to approved baselines or controlled items. The extra reporting feature and the changed deliverable specification both alter what has already been approved, so they need formal change control.
A change request should follow agreed change control when it proposes altering something that has already been approved, such as scope, requirements, specifications, or other controlled configuration items. In this question, adding an extra reporting feature changes the approved scope, and changing the material in an approved deliverable specification changes an approved product definition. Both should therefore be assessed through the formal change control process.
By contrast, correcting spelling in an unapproved draft is routine document improvement, and updating a risk register review date is normal administration. These actions do not change an approved baseline or controlled product definition. The key test is whether the proposal changes what has been formally agreed.
Both statements propose changes to approved scope or approved product specifications, so they should be raised through agreed change control.
Topic: Understand Project Scope Management
A project has an agreed scope baseline and a defined change control process. Which situation should be raised as a change request and taken through that process?
Best answer: C
What this tests: Understand Project Scope Management
Explanation: Change control is used when someone wants to alter what has already been agreed and baselined. Adding a feature outside the approved scope is a proposed change, so it must be assessed and approved through the project’s change control process.
A change request should follow agreed change control when it proposes altering an approved baseline, such as scope, schedule, cost, or quality criteria. In this case, adding an extra reporting feature changes the agreed scope, so it needs formal review, impact assessment, and approval or rejection.
By contrast, correcting a defect is usually part of bringing the work back into line with the existing specification, not changing that specification. Updating a configuration record is an administrative configuration-management activity, and escalating a missed delivery is issue management. The key distinction is whether the action changes what was approved or simply manages, records, or restores it.
This proposes a change to the approved scope baseline, so it should follow the agreed change control process.
Topic: Understand Project Scope Management
A project manager is comparing scope management on two projects. Project A is a linear office refurbishment, where the approved scope is defined early and changes are formally controlled. Project B is an iterative customer portal update, where users review priorities at the end of each iteration. Which statement best differentiates scope management in these two projects?
Best answer: C
What this tests: Understand Project Scope Management
Explanation: The main difference is when and how scope is defined. Linear projects usually define most scope early and control later changes against a baseline, while iterative projects develop and reorder scope as learning and feedback emerge across iterations.
Scope management varies with the life cycle. In a linear project, the scope is usually defined in more detail near the start, agreed, and then controlled through formal change control if updates are needed. That fits work such as an office refurbishment, where the deliverables are expected to be stable before delivery proceeds.
In an iterative project, the overall intent may be known early, but the detailed scope is progressively elaborated and reprioritised during delivery. Feedback from users at the end of each iteration helps decide what should be done next and in what order. The key difference is not whether scope is managed, but whether it is mostly fixed early or developed incrementally over time.
A common trap is to assume iterative work has no control; it still manages scope, but in a more adaptive way.
This matches the key difference: iterative projects refine scope over time, while linear projects usually baseline scope early and manage change formally.
Topic: Understand Project Scope Management
Proposed changes should be evaluated before approval to ______.
Best answer: C
What this tests: Understand Project Scope Management
Explanation: Proposed changes are reviewed before approval so the project can understand their likely consequences. This helps decision-makers judge whether a change should be accepted based on its impact on agreed baselines and objectives.
In project scope management, proposed changes are evaluated before approval so the project can understand what the change would affect. The main reason is to assess impact before a decision is made, such as effects on scope, schedule, cost, quality, benefits, or other agreed baselines and objectives. This supports informed change control rather than approving changes without understanding their consequences.
Some related activities may happen in the wider change or configuration process, but they are not the reason for the evaluation step itself. Evaluation comes before approval so the right people can decide whether the change is worthwhile and manageable. The key idea is impact assessment, not administration or implementation.
Changes are evaluated first so decision-makers understand the likely effect on scope, time, cost, and other agreed targets before approving them.
Topic: Understand Project Scope Management
Complete the statement.
An organisational breakdown structure shows the project’s ____.
Best answer: A
What this tests: Understand Project Scope Management
Explanation: An organisational breakdown structure (OBS) shows the project organisation by setting out roles, teams, departments, or reporting relationships. Its purpose is to clarify who is responsible, rather than what is being delivered, the work to be done, or the costs involved.
An organisational breakdown structure is a view of the project from the people and responsibility side. It shows how the project is organised, such as teams, departments, roles, or reporting relationships, so responsibility can be understood clearly. In PFQ terms, it helps show the project organisation or responsibility structure.
This is different from other breakdown structures. A product breakdown structure focuses on deliverables or product components. A work breakdown structure focuses on the work or tasks needed. A cost breakdown structure focuses on cost categories. The key idea is that an OBS is about who is involved and how responsibility is arranged, not what is produced or how much it costs.
An organisational breakdown structure represents how people, teams, or functions are arranged and where responsibility sits in the project.
Topic: Understand Project Scope Management
Which statement describes a product breakdown structure (PBS)?
Best answer: B
What this tests: Understand Project Scope Management
Explanation: A product breakdown structure is used to identify the deliverables and component parts the project will create. It is product-focused, whereas a work breakdown structure is work-focused and shows the tasks or work packages needed for delivery.
In APM PFQ terms, a product breakdown structure (PBS) is a hierarchical view of the products, deliverables, or component parts that the project is expected to produce. Its focus is on what will be delivered. This is different from a work breakdown structure (WBS), which focuses on what work needs to be done to create those outputs.
A quick way to distinguish them is:
PBS = deliverables and componentsWBS = activities and work packagesIf an option describes outputs, items, or component parts, it points to PBS. If it describes tasks, effort, or packages of work, it points to WBS.
A PBS is product-focused, so it breaks the project down into deliverables and their components.
Topic: Understand Project Scope Management
In project management, change control is the process used to ______.
Best answer: C
What this tests: Understand Project Scope Management
Explanation: Change control is the formal way a project assesses proposed changes and decides whether to approve, reject, or manage them. It helps protect approved scope and other baselines from uncontrolled change.
Change control is used when someone proposes a change to the project. The purpose is to make sure the change is assessed in a controlled way before action is taken. This usually means reviewing the proposed change, understanding its impact, and then deciding whether it should be approved, rejected, or otherwise managed through the agreed process.
This is different from related project controls. Configuration management focuses on identifying and tracking versions and status of products or configuration items. Defining work packages belongs to project breakdown and planning. Checking deliverables against standards is part of quality control.
The key idea is that change control manages proposed changes formally, rather than allowing informal changes to alter the project.
Change control is the formal process for evaluating proposed changes and deciding how they will be managed.
Use the APM PFQ Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.