PMPRocket
PMP Practice QuestionsGovernance Frameworks
Business Environment Domain

Governance Frameworks PMP Practice Questions

Test yourself with 7 free, scenario-based PMP practice questions on governance frameworks, drawn from the Business Environment 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

A large infrastructure project uses a stage-gate process with five gates. At Gate 3, the project review committee finds that the business case assumptions from Gate 1 are no longer valid due to a significant market shift. What should happen at Gate 3?

  1. A.Proceed as planned — the project has already passed two gates and has too much invested to stop, even if the original market assumptions are no longer valid.
  2. B.Update only the schedule to account for the market changes and proceed
  3. C.The gate committee should decide to proceed, hold, or kill the project based on the current business case validity, not the sunk cost.
  4. D.Refer the decision to the project manager, who knows the project best
Show answer and explanation

Correct answer: C

Stage-gate governance exists precisely to create structured decision points where continuing investment is evaluated on current merit, not historical commitment. At Gate 3, the committee must decide go/no-go/hold based on the project's current strategic and financial viability. Sunk cost fallacy — continuing because of past investment — is a classic governance failure. Updating only the schedule ignores the root cause: invalid business case assumptions. Gate decisions belong to the governance committee, not the project manager.

Question 2 of 7

A steering committee for a major transformation program meets quarterly to review project status and authorize continued funding. Between meetings, the project manager receives a critical risk that could derail the program within six weeks if not addressed. What is the BEST course of action?

  1. A.Wait for the next quarterly steering committee meeting to report the risk formally
  2. B.Handle the risk independently to avoid concerning the steering committee with what may be perceived as operational-level issues below their governance threshold.
  3. C.Escalate only if the risk materializes into an actual issue
  4. D.Request an emergency steering committee session or invoke the escalation protocol to get timely governance input on a program-threatening risk.
Show answer and explanation

Correct answer: D

Governance frameworks include escalation protocols for exactly this scenario — risks that require governance-level decisions before the next scheduled review. A six-week window before a program-threatening risk requires immediate escalation, not waiting for a quarterly cycle. Waiting guarantees the opportunity window closes. Handling independently exceeds the PM's authority for program-level decisions. Escalating only after the risk materializes converts a manageable risk into a crisis.

Question 3 of 7

A project sponsor wants to bypass the organization's Change Control Board (CCB) to approve a major scope addition quickly because the client is pressuring for faster decisions. The PM estimates the change will add 8 weeks and $200,000. What should the project manager do?

  1. A.Explain to the sponsor that the CCB process exists to protect the project and organization, and work to expedite the formal CCB review rather than bypass it.
  2. B.Implement the change now to satisfy the client and document it retroactively
  3. C.Agree to bypass the CCB this once given the urgency of client pressure and the sponsor's direct request, planning to retroactively document the change in the next project status report.
  4. D.Tell the sponsor the change cannot be approved without two weeks of analysis
Show answer and explanation

Correct answer: A

Governance frameworks, including the CCB, exist to ensure accountability and protect both the project and organization from unauthorized scope, cost, or schedule changes. The project manager's role is to uphold governance even under pressure. Bypassing the CCB — even once — sets a precedent that erodes governance integrity. Implementation before approval is gold-plating and a governance violation. Agreeing to bypass makes the PM complicit in circumventing controls. Refusing to expedite is unnecessarily rigid — the goal is to work within governance, not slow it down.

Question 4 of 7

A large organization's project portfolio is experiencing a pattern of projects being approved despite weak business cases, and then being cancelled 12-18 months in at great cost. Which TWO governance improvements would MOST directly address this problem?

Select all that apply.

  1. A.Implement mid-project business case reviews at defined stage gates to catch strategic drift before sunk costs become prohibitive
  2. B.Increase the project management training budget to improve PM competency
  3. C.Require all projects to report to the PMO weekly
  4. D.Strengthen the project initiation gate criteria to require validated financial models, clear benefit owners, and strategic alignment evidence before approval.
  5. E.Require all projects to use agile methodology to enable faster iteration
Show answer and explanation

Correct answers: A and D

The described pattern — weak approvals followed by late cancellations — is a front-end governance and mid-lifecycle governance failure. Tightening initiation criteria prevents weak projects from entering the portfolio. Mid-project business case reviews at stage gates create structured kill points before costs escalate further. Mandating agile changes methodology, not the root cause. PM training improves execution but not selection criteria or governance discipline. Weekly PMO reporting (E) improves visibility but does not address the governance decision-making failure.

Question 5 of 7

A project's Phase 2 tollgate review is approaching. The project is on schedule and within budget, but a recent quality audit found that 22% of completed components do not meet the agreed technical specifications. The project sponsor wants to proceed to Phase 3 to maintain the timeline. What should the tollgate committee decide?

  1. A.Proceed to Phase 3 as the sponsor recommends — schedule is the most important constraint
  2. B.Hold Phase 3 entry until the Phase 2 quality issues are resolved — defects carried forward compound in cost and complexity.
  3. C.Proceed conditionally — allow Phase 3 to begin for non-dependent activities while Phase 2 defects are remediated in parallel.
  4. D.Cancel the project — a 22% defect rate indicates fundamental design failure
Show answer and explanation

Correct answer: B

Tollgate reviews exist to prevent defect propagation between phases. A 22% component failure rate is a significant quality failure that, if carried into Phase 3, will result in far more expensive rework when defects interact with new work built on flawed foundations. The 'hold' decision protects the project's long-term cost and quality profile even at the expense of short-term schedule pressure. Proceeding for schedule reasons alone sacrifices quality for velocity — a classic false economy. Conditional proceed risks dependency conflicts if Phase 3 activities interact with defective Phase 2 components. Cancellation is disproportionate for a recoverable quality issue.

Question 6 of 7

An agile program is using a Lean Portfolio Management (LPM) approach. The portfolio kanban board shows three epics in 'analysis,' five in 'implementing,' and two in 'done.' WIP limits are set at two for analysis and four for implementing, but the limits are consistently ignored. What is the MOST serious consequence of ignoring WIP limits in LPM?

  1. A.Overloading the implementing stage prevents flow, increases multitasking, extends cycle time, and reduces the portfolio's ability to deliver value predictably.
  2. B.The portfolio kanban board becomes cluttered and difficult to read, which signals a systemic WIP limit problem rather than just a board design issue that tools can fix.
  3. C.The teams will have too much work and will become stressed, which is a symptom rather than a root cause and does not address the flow and predictability problem in the portfolio.
  4. D.The portfolio governance team will lose visibility into project status, a concern that the Lean Portfolio Management cadence and portfolio kanban board can address through adjusted reporting.
Show answer and explanation

Correct answer: A

WIP limits in Lean Portfolio Management are not administrative rules — they are flow control mechanisms rooted in Little's Law. When WIP limits are exceeded, work in the system increases, individual cycle times lengthen, context-switching rises, and portfolio throughput paradoxically decreases. Five epics in implementation when the limit is four means the system is overloaded, and predictability degrades. Board readability is a minor consequence. Team stress is a secondary effect. Visibility is actually improved by a kanban board regardless of WIP limit adherence.

Question 7 of 7

A project steering committee includes the project sponsor, three senior business stakeholders, the CIO, and the CFO. At a critical milestone review, the business stakeholders unanimously support proceeding, but the CIO raises a cybersecurity concern that has not been assessed. The CFO has no opinion. What should the steering committee do?

  1. A.Pause the proceed decision and commission a rapid cybersecurity risk assessment before approving Phase progression.
  2. B.Proceed based on majority vote, treating three business stakeholder votes as sufficient to override the CIO's cybersecurity risk assessment without further technical review.
  3. C.Overrule the CIO — business value outweighs technical concerns
  4. D.Proceed now and address cybersecurity in the next phase
Show answer and explanation

Correct answer: A

Steering committees must make risk-informed decisions. A cybersecurity concern raised by the CIO — the organization's technical risk authority — at a milestone review is a governance red flag that cannot be overridden by enthusiasm for business progress. Proceeding without a risk assessment exposes the organization to breaches, regulatory penalties, and reputational damage. Governance by majority vote is inappropriate for risk decisions where subject matter expertise is concentrated in a specific role. Overruling the CIO disregards the expertise that makes the CIO's role valuable. Deferring to the next phase carries the unassessed risk forward into additional investment.

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 Business Environment practice questions

Organizational Change Management (17)AI in Project Management (12)Compliance and Governance (11)Strategic Alignment and Business Case (11)Sustainability (11)Benefits Realization and Transition (10)