Browse Certification Practice Tests by Exam Family

PMI-CP: Strategy and Scope Management

Try 10 focused PMI-CP questions on Strategy and Scope Management, with answers and explanations, then continue with PM Mastery.

On this page

Open the matching PM Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Topic snapshot

FieldDetail
Exam routePMI-CP
Topic areaStrategy and Scope Management
Blueprint weight15%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate Strategy and Scope Management for PMI-CP. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 15% 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.

Sample questions

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.

Question 1

Topic: Strategy and Scope Management

A design-build team is preparing the mechanical bid package for a live hospital expansion. One week before release, hospital operations states that central-plant tie-ins are limited to two short outage windows, but the current scope documents do not assign shutdown sequencing or temporary cooling responsibility. The owner wants to avoid rework and keep the release date if possible. What is the best action?

  • A. Release the package now and resolve details through post-award RFIs.
  • B. Revise scope with operations and design, define tie-ins and boundaries, then update the baseline through formal control.
  • C. Add a contingency allowance and keep the scope description unchanged.
  • D. Record the outage limits as a risk for the next monthly review.

Best answer: B

What this tests: Strategy and Scope Management

Explanation: This is a scope-maturity problem revealed before procurement, not something to defer into execution. The best response is to clarify the missing requirements and package boundaries with the affected stakeholders, then update the controlled scope before issuing the package.

When new information exposes missing requirements, unclear boundaries, or immature assumptions, the project team should revise the scope to improve accuracy before work is released. Here, outage limits and responsibility for shutdown sequencing and temporary cooling are now known constraints that materially affect the package. A focused scope revision with operations, design, and package owners allows the team to define the missing requirement, clarify interface boundaries, and update the baseline in a controlled way.

  • Confirm the operating constraint and affected work.
  • Clarify ownership of tie-ins, sequencing, and temporary works.
  • Update scope documents, assumptions, and interface assignments.
  • Process any baseline adjustment through formal control before release.

Using contingency or later RFIs may mask uncertainty, but they do not mature the scope.

Newly revealed constraints and unclear boundaries require immediate scope maturation and controlled scope revision before release.


Question 2

Topic: Strategy and Scope Management

During design development for a hospital expansion, the architect proposes adding 40 pages of room-by-room narrative notes to the clinical areas package. Package interfaces are already defined, and the team is not selecting among alternative layouts or systems. Before revising scope, the owner wants evidence that the extra content improves delivery value and closes decision gaps rather than simply adding detail. Which artifact would best support that decision?

  • A. An interface register update for package dependencies and owners
  • B. A scope evaluation note assessing outcome alignment, open gaps, and scope maturity
  • C. A value engineering workshop to compare functional alternatives
  • D. A change or variation order record with cost and schedule fields

Best answer: B

What this tests: Strategy and Scope Management

Explanation: The need is to judge whether added content makes the scope more mature and decision-ready, not just more detailed. A scope evaluation note is the best fit because it checks outcome alignment, unresolved gaps, and whether the revision actually improves delivery value.

The core issue is scope maturity. The owner is not asking for better interface tracking, formal change documentation, or option optimization; the owner wants proof that the proposed revision improves the scope in a meaningful way. A scope evaluation note is built for that purpose because it tests whether added content ties to project outcomes, removes ambiguity, closes material gaps, and supports a clear decision.

  • Does the revision improve the intended delivery outcome?
  • Does it resolve an open scope or decision gap?
  • Does it make the package clearer and more complete for execution?

If not, the added pages are just detail accumulation, not a better scope definition. The closest distractor is value engineering, which is stronger when real functional alternatives are being compared.

This artifact directly tests whether the revision improves scope maturity and delivery value instead of only expanding documentation.


Question 3

Topic: Strategy and Scope Management

A health-system owner wants to approve a guaranteed maximum price (GMP) this week to keep a structural steel fabrication slot on a design-build hospital project. However, the operating room equipment list is still changing, ceiling service coordination is incomplete, and the estimate includes large allowances for medical gas and nurse-call systems. Which action best balances schedule pressure with sound scope and governance practice?

  • A. Delay all commitments until design is fully complete
  • B. Approve the full GMP now and rely on contingency
  • C. Authorize defined early-work packages and hold full GMP pending scope maturity review
  • D. Seek approval now and treat later clarifications as change orders

Best answer: C

What this tests: Strategy and Scope Management

Explanation: Changing owner requirements, incomplete coordination, and heavy use of allowances show the scope is not mature enough for full GMP commitment. The best tradeoff is to let clearly defined early work proceed while requiring a scope maturity review before full governance approval and price lock-in.

The key concept is scope maturity: a project should not make a full contract or governance commitment when major requirements, interfaces, and pricing assumptions are still unresolved. In this scenario, changing clinical equipment needs and incomplete ceiling coordination mean the basis of design is still moving, and large allowances confirm that the estimate is covering uncertainty rather than pricing mature scope.

A balanced response is to separate what is well defined from what is not:

  • allow only clearly bounded early-work packages
  • complete a scope maturity review on the unresolved systems
  • confirm interfaces, owner requirements, and estimate basis before full GMP approval

This protects schedule where scope is stable, while reducing avoidable change orders, claims, and weak governance decisions. The closest alternative is waiting for full design completion, but that is unnecessarily rigid if some early work is already sufficiently defined.

This preserves schedule for clearly defined work while avoiding a full contract commitment before critical scope and interfaces are mature enough.


Question 4

Topic: Strategy and Scope Management

On a mixed-use tower project, early construction packages are about to be released. The owner’s leasing team keeps sending “minor” layout revisions directly to the architect and trade partners. Some changes improve leasing value, but others affect issued packages and create conflicting field direction. The sponsor asks the project manager how to redesign the change-order process now so decisions stay fast without losing value or contract control. Which response is best?

  • A. Ask everyone to copy the project manager on change emails and issue a weekly summary so stakeholders remain informed.
  • B. Set one intake path for all changes, require benefit and impact analysis, apply approval thresholds with target response times, and communicate each decision to every affected party before work proceeds.
  • C. Stop accepting tenant-driven changes once package release begins so schedule and budget stay protected.
  • D. Allow urgent layout revisions to proceed on verbal direction in the field and reconcile pricing and paperwork later.

Best answer: B

What this tests: Strategy and Scope Management

Explanation: A robust change-order process must do more than circulate information. It should channel every request through one path, test value and contract effects, assign decision authority, and set response times so work is not changed before authorization.

The core concept is to design the change-order process early enough that beneficial changes can still be evaluated without losing control. Here, direct requests to designers and trade partners create scope ambiguity, inconsistent stakeholder understanding, and exposure to rework or later claims. The best response creates a single intake and review path, requires each request to document the business benefit, scope effect, cost and schedule impact, contract basis, and affected packages, and uses approval thresholds with target turnaround times. It also closes the loop by sending the decision to all impacted parties before work proceeds.

  • Capture each request in one place
  • Evaluate value and project impacts
  • Apply decision rights and timing targets
  • Communicate the outcome to affected teams

Visibility alone is not enough; the process must support fast, controlled decisions.

It creates a controlled, decision-ready change process that preserves value, contract discipline, and timely stakeholder action.


Question 5

Topic: Strategy and Scope Management

The owner reviews a draft scope for a hospital renovation and asks whether it is ready for baselining.

Exhibit: Scope workshop note

Project mission: Convert the east wing into an outpatient imaging clinic by March 2027.
Required outcomes:
- Increase daily patient throughput by 30%
- Keep patient travel path from entry to imaging under 6 minutes
- Avoid disruption to the adjacent emergency department

Candidate scope items:
- Add self-check-in kiosks at clinic entry
- Use bronze exterior panels to match nearby tower
- Install premium stone at reception desk
- Create donor photo wall near waiting area

Based on the exhibit, what is the best next action?

  • A. Prioritize donor and appearance requests to build stakeholder support.
  • B. Baseline all listed items now to minimize future scope disputes.
  • C. Add detailed finish specifications for each listed item first.
  • D. Rework scope around mission-linked outcomes and question unlinked preferences.

Best answer: D

What this tests: Strategy and Scope Management

Explanation: The exhibit already gives a mission and measurable outcomes, but most candidate items are aesthetic or preference-based with no visible link to throughput, travel path, or operational continuity. The scope should be refined by testing each item against those outcomes before baselining.

Outcome-focused scope starts with the project mission and desired results, not with a list of finishes, features, or stakeholder wishes. In this exhibit, the decision anchors are higher patient throughput, shorter patient travel time, and no disruption to the emergency department. A self-check-in kiosk may support those outcomes, but the bronze panels, premium stone, and donor wall are currently just preferences or specifications without a stated mission link.

  • Keep or further assess items that improve flow, access, or continuity.
  • Challenge, defer, or separately justify items driven only by aesthetics or preference.
  • Baseline scope only after each item shows a clear contribution to the mission.

The closest trap is adding more technical detail, because detailed specifications do not make a scope outcome-focused.

The exhibit shows measurable operational outcomes, so scope items should be kept, challenged, or deferred based on their clear contribution to those outcomes.


Question 6

Topic: Strategy and Scope Management

On a fast-track hospital expansion, owner equipment revisions are expected after trade packages are awarded. The project manager already has a standard change-order form that captures scope, cost, and schedule impacts, but supervisors still issue direction by email and no one knows who may approve a $25,000 field change or when affected trades must be notified. What is the next best step?

  • A. Require the steering committee to approve every cost-impacting change.
  • B. Define approval thresholds, decision rights, record ownership, and notification workflow.
  • C. Treat any contractor objection as a claim and log it immediately.
  • D. Route all requests through the PMIS and refine approvals later.

Best answer: B

What this tests: Strategy and Scope Management

Explanation: A change-order form captures information, but it does not control decisions by itself. Before more changes occur, the team should define approval thresholds, role responsibilities, the controlling record, and required communication steps so field direction cannot bypass governance.

In construction change-order management, documenting impacts is only one part of the process. Once a standard form exists, the next design step is to define how the process will operate: who initiates and reviews a change, which approval level applies at different thresholds, who owns the official change-order record, and when procurement, field supervision, and affected trades must be notified. That prevents informal email instructions from creating unauthorized scope, cost, or schedule impacts.

  • Set thresholds so routine changes and major changes follow different approval paths.
  • Assign clear decision rights and record ownership.
  • Define communication triggers so only authorized changes reach the field.

A PMIS can support this workflow, but it does not replace it, and a claim process starts later only if entitlement or compensation becomes contested.

The form exists, so the next step is to define who can decide, which record controls the change, and how approved direction is communicated.


Question 7

Topic: Strategy and Scope Management

On a hospital renovation project, the owner asks to relocate two nurse stations after wall framing has started. The superintendent has the revised sketch, photos, and list of affected trades, but impacts are being discussed in email threads and no one can tell which comments are current. The project uses a digital change-order system with linked documents, routing, and status dashboards. What should the project manager do next?

  • A. Open a change-order record, link documents, and route impact reviews.
  • B. Authorize rework immediately to avoid schedule delay.
  • C. Wait for final pricing, then submit one approval package.
  • D. Escalate the matter as a contract claim.

Best answer: A

What this tests: Strategy and Scope Management

Explanation: The next step is to capture the proposed scope change in the digital system and start the review workflow. That gives the team one current source of truth, preserves traceability, and speeds coordination among affected stakeholders before work is authorized.

When a potential scope change is identified and the supporting information is already available, the next step is to create the formal change-order record in the technology platform and route it for impact review. This uses technology for exactly the benefits tested here: visibility of current status, traceability of documents and decisions, structured workflow, and faster coordination across trades, design, and owner representatives.

By logging the change early, the team can collect schedule, cost, and constructability impacts in parallel and maintain a clear audit trail from request through approval. Starting field work first weakens control, waiting for final pricing delays visibility and stakeholder alignment, and treating the request as a claim confuses a proposed owner change with a contested entitlement matter. The key takeaway is that technology should support disciplined change control, not just faster messaging.

This is the right next step because it creates immediate visibility and traceability while starting the formal review workflow before approval or field action.


Question 8

Topic: Strategy and Scope Management

A municipal transit-station project is under pressure to add premium finishes and retail space. The owner’s mission is to open before a major event and improve passenger throughput and accessibility; several requested additions may increase cost without improving those outcomes. The project manager wants one artifact that can guide contract decisions, screen change orders, explain tradeoffs to stakeholders, and support governance decisions. Which artifact best fits this need?

  • A. PMIS dashboard centralizing project communications
  • B. Scope evaluation note mapping work to mission outcomes
  • C. Change order record documenting cost, time, and authorization
  • D. Governance decision record capturing approvals and escalation

Best answer: B

What this tests: Strategy and Scope Management

Explanation: An outcome-focused scope evaluation note is best because it connects scope choices to the mission and measurable results, not just requested features. That lets the team use the same basis when shaping contract decisions, reviewing change orders, communicating with stakeholders, and escalating tradeoffs to governance.

Outcome-focused scope means the project judges work by the results it must deliver, such as opening date, throughput, and accessibility. In this scenario, the strongest artifact is a scope evaluation note that links proposed scope, contract commitments, and change requests to mission outcomes, value, and acceptance criteria. It creates one decision basis that multiple parties can use instead of debating features in isolation.

  • For contract decisions, it helps define what the contract must protect or incentivize.
  • For change orders, it tests whether a requested change supports core outcomes or mainly adds preference.
  • For stakeholder communication and governance, it makes tradeoffs visible and easier to justify.

A change order record or governance record is useful later, but neither substitutes for outcome-based scope evaluation.

It provides a shared basis to test base scope and proposed changes against the project mission before contracts or approvals lock them in.


Question 9

Topic: Strategy and Scope Management

A transit-station upgrade is at a governance gate for a lump-sum electrical package. Design is 45% complete, traction-power interfaces with the civil package are still undefined, several owner equipment loads are marked TBD, and outage windows have not been confirmed by operations. The sponsor wants to award now to protect the schedule. What is the best action?

  • A. Seek governance approval now and resolve interfaces during execution
  • B. Defer full award, complete a scope maturity review, and authorize only clearly defined early works
  • C. Award the package now with added contingency for unresolved details
  • D. Ask bidders to include assumptions for the TBD items and price changes later

Best answer: B

What this tests: Strategy and Scope Management

Explanation: The package is not mature enough for a reliable lump-sum commitment or sound governance review. Undefined interfaces, TBD owner inputs, and unconfirmed outage constraints should be resolved before full award; if schedule pressure is real, only clearly bounded early work should move forward.

Scope maturity is sufficient when the team can define the work, key interfaces, constraints, and decision basis well enough to commit contractually or evaluate later changes fairly. Here, the electrical package still has unresolved package boundaries, owner-driven TBD loads, and unconfirmed outage windows. Those gaps mean the scope baseline is unstable, so a full lump-sum award would transfer uncertainty into pricing assumptions, change orders, and possible claims.

  • Confirm missing owner decisions and technical inputs.
  • Resolve major interface points with adjacent packages.
  • Validate execution constraints such as outage access.
  • If schedule protection is necessary, release only tightly bounded early works.

Adding money or assumptions does not make an immature scope mature; it only hides the uncertainty.

Key scope inputs, interfaces, and constraints are still unresolved, so full contract commitment is premature; only tightly bounded work should proceed until scope matures.


Question 10

Topic: Strategy and Scope Management

On a fast-track transit-station project, major trade packages will be released next month, but the operator, city, and retail tenants are still proposing scope changes. The sponsor wants a change-order process that keeps procurement moving while ensuring each change is evaluated for outcome impact, cost, schedule, risk, and stakeholder consequences. Which process design is best?

  • A. Let package leads approve urgent changes and reconcile impacts later.
  • B. Send every change to the steering committee before design updates.
  • C. Screen changes mainly against remaining contingency and schedule float.
  • D. Use a tiered workflow with a standard impact review and approval thresholds.

Best answer: D

What this tests: Strategy and Scope Management

Explanation: A tiered, criteria-based change process best balances responsiveness and control on a construction project. It allows minor changes to move quickly while ensuring each proposed change is assessed consistently for outcome, cost, schedule, risk, and stakeholder effects before approval.

The core concept is designing a change-order process that protects project outcomes without creating unnecessary delay. In this scenario, the best design is a tiered workflow established before package release, using a standard impact review for each proposed change and clear approval thresholds based on significance, interfaces, and stakeholder effects. That structure supports faster handling of low-impact changes while escalating higher-impact changes early enough to protect budget, schedule, risk position, and stakeholder alignment.

  • Standard review criteria improve decision quality.
  • Approval thresholds avoid overloading senior governance.
  • Early evaluation reduces downstream rework and claim exposure.

The closest distractor increases oversight, but routing every change upward slows the project without improving routine change decisions.

This design balances speed and control by requiring consistent multi-factor evaluation while matching decision rights to change significance.

Continue with full practice

Use the PMI-CP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Open the matching PM Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Free review resource

Read the PMI-CP guide on PMExams.com, then return to PM Mastery for timed practice.

Revised on Thursday, May 14, 2026