Courseiva

PRINCE2 7 Practitioner (Managing Successful Projects with PRINCE2, 7th Edition) (PRINCE2-PRACTITIONER) (PRINCE2-PRACTITIONER) — Questions 1–75

249 questions total · 4 pages · All types, answers revealed

Page 1 of 4

Page 2
1
MCQmedium

A PRINCE2 project is transitioning from the initiation phase to delivery. The Project Manager wants to foster a culture of psychological safety within the newly formed delivery team. According to PRINCE2 7 team dynamics, how is psychological safety best demonstrated?

A.Mandating that all communication must go through the Project Manager without peer interaction.
B.Ensuring that only positive feedback is ever shared during team meetings.
C.Punishing team members immediately when they report a minor error or near-miss.
D.Encouraging open dialogue where mistakes are treated as learning opportunities and dissenting views are welcomed.
AnswerD

Psychological safety is demonstrated through behaviour: treating mistakes as learning rather than blame, and welcoming dissenting views. This lets team members raise concerns and challenge decisions without fear, which PRINCE2 7 identifies as underpinning effective team dynamics.

Why this answer

Psychological safety in PRINCE2 7 team dynamics is demonstrated by creating an environment where team members feel safe to speak up, admit mistakes, and challenge ideas without fear of retribution. Encouraging open dialogue where mistakes are treated as learning opportunities and dissenting views are welcomed directly embodies this principle.

Exam trap

PRINCE2-Practitioner often tests whether candidates confuse psychological safety with 'being nice' or 'avoiding conflict' — the trap is selecting an answer that promotes harmony over honesty, when psychological safety actually requires welcoming dissent and acknowledging mistakes.

How to eliminate wrong answers

Option A is wrong because mandating all communication through the Project Manager eliminates peer interaction and creates a bottleneck that suppresses open dialogue, which is the opposite of psychological safety. Option B is wrong because ensuring only positive feedback is shared prevents honest discussion of problems and risks, which undermines the transparency and trust that psychological safety requires. Option C is wrong because punishing team members for reporting errors or near-misses discourages transparency and creates a fear-based culture, which is the antithesis of psychological safety.

2
MCQhard

A project is operating in a matrix organization where resources have dual reporting lines to functional managers and the PRINCE2 Project Manager. Resource availability is frequently compromised by functional priorities. How should the Project Manager apply PRINCE2 7 people principles to resolve this resource contention?

A.Bypass the functional managers entirely and negotiate private overtime arrangements directly with individual team members.
B.Establish formal resource agreements and transparent forecast tracking with functional managers, linking resource allocation directly to project stage boundaries and benefits.
C.Reallocate all project tasks exclusively to external contractors to avoid relying on matrixed internal resources.
D.Escalate to the Executive to issue a corporate mandate making the project the absolute priority over all functional work.
AnswerB

Formal resource agreements with functional managers, plus transparent forecast tracking tied to stage boundaries and benefits, address dual-reporting contention. This satisfies the stem's matrix-organisation constraint by making commitments explicit and aligning resource allocation with PRINCE2 7 people principles of clear roles and collaboration.

Why this answer

In a matrix organisation, the Project Manager must negotiate and formalise resource commitments with functional managers rather than bypass them, and PRINCE2 7's people principles stress transparency, collaboration and linking work to stage boundaries and benefits. Option B does this by establishing formal resource agreements and transparent forecast tracking tied to stage boundaries and benefits. This respects the dual reporting lines while giving the Project Manager a defensible basis for resource contention.

Exam trap

PRINCE2-Practitioner often tests the misconception that the Project Manager can simply escalate or bypass functional managers, when the correct approach is negotiated, transparent resource agreements aligned to stage boundaries.

How to eliminate wrong answers

Option A is wrong because bypassing functional managers and arranging private overtime undermines the matrix governance structure and creates contractual and wellbeing risks. Option C is wrong because wholesale replacement with contractors is a disproportionate, costly response that ignores the root cause and does not address the matrix governance issue. Option D is wrong because escalating for an absolute corporate mandate is a blunt instrument that damages cross-functional relationships and is not the collaborative approach PRINCE2 7 people principles advocate.

3
Multi-Selectmedium

A Project Manager in the Controlling a Stage process receives a request for change from a stakeholder. Which TWO actions must the Project Manager take first in handling this request?

Select 2 answers
A.Assess the impact of the change on the Business Case, risks, and tolerances
B.Immediately implement the change to satisfy the stakeholder
C.Send the change directly to the Project Board for automatic approval
D.Discard the change if it comes from anyone other than the Executive
E.Capture and log the request in the Issue Register
AnswersA, E

Impact assessment is mandatory before any change decision, letting the Project Manager evaluate effects on the Business Case, risks and stage tolerances. This determines whether the change can be handled within the stage or must escalate to the Project Board, satisfying PRINCE2's tolerance-based control.

Why this answer

In PRINCE2's Controlling a Stage process, the Project Manager must first capture and log the request for change in the Issue Register (option E), because every issue or change request must be formally recorded and tracked before any assessment or decision can be made. Next, the Project Manager must assess the impact of the change on the Business Case, risks, and tolerances (option A), since PRINCE2 requires an impact analysis against the project's baseline and tolerances to determine whether the change can be handled at the project-manager level or must be escalated to the Project Board. Option B is wrong because implementing a change immediately bypasses the mandatory impact assessment and change control procedure.

Option C is wrong because changes should only be escalated to the Project Board after the Project Manager has logged and assessed them, not sent automatically for approval. Option D is wrong because change requests can come from any stakeholder, not only the Executive, and must still be captured and evaluated.

Exam trap

The trap is thinking that changes should be implemented immediately or escalated without assessment — candidates often skip the crucial steps of logging and impact analysis.

4
MCQhard

A project plan includes strict sustainability milestones to comply with new environmental regulations. During plan development, the Project Manager needs to ensure that dependencies between environmental audit checkpoints and procurement deliverables are accurately mapped. Which tool/technique supports this within product-based planning?

A.Product Flow Diagram
B.Product Breakdown Structure
C.Benefits Management Approach
D.Quality Register
AnswerA

The Product Flow Diagram maps the order and dependencies between products, showing which deliverables must be complete before others begin. It therefore exposes the sequencing links between environmental audit checkpoints and procurement deliverables, which is exactly what the Project Manager needs to map.

Why this answer

The Product Flow Diagram (PFD) is a tool within PRINCE2's product-based planning technique that shows the sequence and dependencies between products. It is used to map the order in which products must be developed, including dependencies between environmental audit checkpoints and procurement deliverables. Option A is correct because the PFD specifically illustrates product dependencies.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between the Product Breakdown Structure and the Product Flow Diagram, and candidates may incorrectly choose the PBS when asked about dependencies or sequence.

How to eliminate wrong answers

Option B is wrong because the Product Breakdown Structure (PBS) hierarchically breaks down the project into products but does not show dependencies or sequence. Option C is wrong because the Benefits Management Approach describes how benefits will be managed and measured, not product dependencies. Option D is wrong because the Quality Register records quality activities and results, not the mapping of dependencies.

5
Multi-Selecthard

A project is in the 'Managing a Stage Boundary' process. The Project Manager is preparing the End Stage Report and the next Stage Plan. The project board has requested assurance that the project remains aligned with the PRINCE2 principle 'Focus on products'. Which TWO actions should the Project Manager take to demonstrate this principle? (Choose two.)

Select 2 answers
A.Ensure that the stage plan includes activities for risk management and issue resolution.
B.Update the product breakdown structure to reflect any changes in the products required for the next stage.
C.Verify that the project's organization structure includes a senior supplier who can approve product designs.
D.Review the product descriptions to ensure that quality criteria and quality methods are still valid for the next stage.
E.Confirm that the project board has approved the business case for the next stage.
AnswersB, D

Updating the product breakdown structure ensures that the project's products are clearly defined and agreed upon, which is central to the principle 'Focus on products'. By reflecting changes, the Project Manager ensures that the next stage plan is based on a current and accurate understanding of the required products, thereby aligning with the principle.

Why this answer

The principle 'Focus on products' requires that projects are defined and driven by the delivery of products that meet agreed quality criteria. At a stage boundary, the Project Manager should ensure that the product breakdown structure is updated and that product descriptions are reviewed to confirm their quality criteria and methods. These actions ensure that the next stage plan is product-centric and that the project remains aligned with the principle.

Exam trap

The trap here is to confuse the principle 'Focus on products' with other principles such as 'Continued business justification' or 'Defined roles and responsibilities', leading to the selection of actions that do not directly relate to product definition and quality.

6
Multi-Selecthard

During the Managing Product Delivery process, a Team Manager interacts with the Project Manager. Which THREE of the following are responsibilities of the Team Manager within this process?

Select 3 answers
A.Delivering completed products and reporting progress via Checkpoint Reports
B.Approving the overall Project Initiation Documentation
C.Creating Team Plans to schedule specialist activities
D.Authorizing stage-level Exception Plans
E.Accepting and checking Work Packages
AnswersA, C, E

Delivering completed products and reporting progress via Checkpoint Reports sits squarely within Managing Product Delivery, where the Team Manager accepts work packages, executes them, and keeps the Project Manager informed. Checkpoint Reports provide the agreed progress and forecast information, satisfying the stem's requirement for Team Manager responsibilities during that process.

Why this answer

In PRINCE2's Managing Product Delivery process, the Team Manager is responsible for accepting and checking Work Packages (option E) from the Project Manager, ensuring the work is understood and agreed before starting. The Team Manager also creates Team Plans (option C) to schedule and coordinate the specialist activities needed to produce the products. Finally, the Team Manager delivers the completed products and reports progress to the Project Manager via Checkpoint Reports (option A).

Options B and D are incorrect because approving the Project Initiation Documentation and authorizing stage-level Exception Plans are responsibilities of the Project Board, not the Team Manager.

Exam trap

PRINCE2-PRACTITIONER often tests the specific responsibilities of the Team Manager versus the Project Manager and Project Board, and candidates may incorrectly assign approval responsibilities to the Team Manager.

7
Multi-Selecthard

When applying product-based planning within the PRINCE2 Plans practice, which TWO of the following steps must be completed before estimating effort and scheduling activities?

Select 2 answers
A.Creating the final Gantt chart schedule of team work packages
B.Closing the project and writing the End Project Report
C.Writing the Project Product Description
D.Submitting an Exception Report to the Project Board
E.Creating the Product Breakdown Structure
AnswersC, E

The Project Product Description defines the project's overall purpose, composition and acceptance criteria, so it must be written first. It anchors the subsequent Product Breakdown Structure and gives the planning horizon against which effort and schedule are later estimated.

Why this answer

In PRINCE2 product-based planning, the first step is to write the Project Product Description (option C), which defines the overall project product, its customer quality expectations, acceptance criteria, and any key tolerances, providing the top-level anchor for all subsequent planning. The next step is to create the Product Breakdown Structure (option E), which decomposes the project product into its component products and shows the hierarchy of what must be produced. Only after the Project Product Description and Product Breakdown Structure exist can the planner write Product Descriptions, perform product flow analysis, and then estimate effort and schedule activities.

Option A is wrong because the Gantt chart schedule is an output of the scheduling step that comes after estimation, not a prerequisite. Option B is wrong because closing the project and writing the End Project Report occur at the end of the project, not during planning. Option D is wrong because an Exception Report is produced only when tolerances are forecast to be breached during a stage, which is unrelated to the pre-estimation planning steps.

Exam trap

PRINCE2-PRACTITIONER often tests the ordering of product-based planning steps — candidates may incorrectly place scheduling or Gantt chart creation before product definition, reversing the correct sequence.

8
MCQhard

A project manager is developing a Stage Plan using product-based planning. The project includes software development and strict environmental compliance documentation. During the creation of the Product Flow Diagram, the team realizes that the environmental compliance audit must be completed *before* software deployment can be signed off. How is this dependency represented?

A.As a hierarchical parent-child branch in the Product Breakdown Structure.
B.As a prerequisite dependency link on the Product Flow Diagram.
C.As an Exception Report submitted to the Board.
D.As an entry in the Quality Register under test failures.
AnswerB

The Product Flow Diagram shows the sequence and dependencies between products, so a mandatory ordering where the compliance audit must precede deployment sign-off is drawn as a prerequisite link. This satisfies the stem's constraint that the audit is completed before sign-off.

Why this answer

In PRINCE2 product-based planning, the Product Flow Diagram (PFD) shows the sequence and dependencies between products. A prerequisite dependency, where one product must be completed before another can start, is represented as a dependency link (arrow) from the prerequisite product to the dependent product. Here, the environmental compliance audit must be completed before software deployment sign-off, so this is a prerequisite dependency link on the PFD.

Exam trap

PRINCE2-Practitioner often tests the confusion between the Product Breakdown Structure (PBS) and Product Flow Diagram (PFD). Candidates may incorrectly select a PBS element when asked about dependencies, forgetting that the PBS shows hierarchy, while the PFD shows sequence and dependencies.

How to eliminate wrong answers

Option A is wrong because a hierarchical parent-child branch belongs in the Product Breakdown Structure (PBS), which shows composition, not sequence. Option C is wrong because an Exception Report is a PRINCE2 progress control document, not a planning artifact for dependencies. Option D is wrong because the Quality Register records quality activities and results, not product dependencies.

9
MCQeasy

In the PRINCE2 Risk practice, what is the primary difference between a risk and an issue?

A.Risks are positive, while issues are always negative.
B.Risks are managed by the Project Board, while issues are managed solely by Team Managers.
C.Risks relate to future uncertainty, whereas issues relate to events that have already occurred.
D.Risks require a Risk Register, while issues are never logged.
AnswerC

Risks concern uncertain future events that may or may not occur, and are managed proactively. Issues are events that have already happened and require a response, such as a request for change, off-specification or problem.

Why this answer

In PRINCE2, a risk is an uncertain event that, if it occurs, will have an effect on the project's objectives; it is something that has not yet happened. An issue, by contrast, is a problem or event that has already occurred and requires management attention. This temporal distinction—future uncertainty versus past or present occurrence—is the primary difference between the two concepts.

Exam trap

PRINCE2-Practitioner often tests the temporal distinction between risk (future) and issue (already occurred), so candidates who focus on positivity/negativity or ownership rather than timing select the wrong answer.

How to eliminate wrong answers

Option A is wrong because risks can be either threats (negative) or opportunities (positive), and issues are not always negative; an issue can be a request for change that improves the project. Option B is wrong because both risks and issues are managed at various levels; the Project Board sets tolerances and may be involved in escalated issues, while Team Managers can identify risks, so the split is not exclusive. Option D is wrong because while risks are recorded in the Risk Register, issues are recorded in the Issue Register, so the statement that issues are never logged is factually incorrect.

10
MCQeasy

In the PRINCE2 Plans practice, what is the name of the hierarchical structure that breaks down the project into its constituent products?

A.Risk Breakdown Structure
B.Product Breakdown Structure
C.Work Breakdown Structure
D.Organizational Breakdown Structure
AnswerB

The Product Breakdown Structure is the hierarchy that decomposes the project into its constituent products, satisfying the Plans practice requirement for product-based planning. It identifies every product and its components, forming the foundation for the Product Flow Diagram and Product Descriptions, which together define scope and dependencies before scheduling activities.

Why this answer

The Product Breakdown Structure (PBS) is the hierarchical diagram used in PRINCE2 to decompose the project into its constituent products, both management and specialist. It shows the products that must be created and their relationships, forming the basis for product flow diagrams and product descriptions. The PBS is a key component of the Plans theme, ensuring that all required products are identified and defined before planning activities and resources.

Exam trap

PRINCE2-Practitioner often tests the distinction between the Product Breakdown Structure (PBS) and the Work Breakdown Structure (WBS), as candidates with PMP or other PM backgrounds may incorrectly assume WBS is the correct answer for product decomposition.

How to eliminate wrong answers

Option A is wrong because the Risk Breakdown Structure (RBS) is a hierarchical representation of risks categorized by source or type, used in risk management, not for breaking down products. Option C is wrong because the Work Breakdown Structure (WBS) is a hierarchical decomposition of the project scope into work packages, focusing on activities and deliverables, but PRINCE2 specifically uses the PBS for product decomposition; the WBS is not a PRINCE2 term. Option D is wrong because the Organizational Breakdown Structure (OBS) defines the project team structure and reporting lines, not product decomposition.

11
MCQmedium

During the Initiating a Project (IP) process, how does the Project Manager establish the governance structure for the project?

A.By designing the project management team structure and defining role descriptions in the PID.
B.By outsourcing all governance responsibilities to an external auditing firm.
C.By letting the Team Managers self-organize their own reporting lines to the Project Board.
D.By having Corporate take over all daily decision-making from the Project Manager.
AnswerA

The Project Initiation Documentation contains the project management team structure and role descriptions, so governance is established by designing that structure and documenting it in the PID. This satisfies IP's requirement to define who is accountable, responsible and consulted before the project proceeds.

Why this answer

During Initiating a Project, the Project Manager establishes the governance structure by designing the project management team structure and defining role descriptions in the Project Initiation Documentation (PID). This includes identifying the Project Board, Project Manager, Team Managers, and other roles, and documenting their responsibilities and reporting lines.

Exam trap

PRINCE2-Practitioner often tests the misconception that governance can be delegated externally or that Team Managers define their own reporting lines; the trap is confusing governance design with operational management.

How to eliminate wrong answers

Option B is wrong because outsourcing governance to an external auditing firm abdicates the Project Board's accountability and violates PRINCE2's defined roles and responsibilities principle. Option C is wrong because Team Managers do not self-organize reporting lines to the Project Board; the governance structure is defined by the Project Manager and approved by the Board. Option D is wrong because Corporate taking over daily decision-making undermines the Project Manager's authority and the 'manage by exception' principle.

12
MCQmedium

During a project audit, it is discovered that team members are unsure who has the authority to approve design changes because the Project Management Team structure was never formally documented. Which PRINCE2 principle has been violated?

A.Defined roles and responsibilities
B.Focus on products
C.Tailor to suit the project
D.Manage by exception
AnswerA

Undocumented authority stems from failing to define who is accountable for what, which is precisely what the defined roles and responsibilities principle requires. It mandates that every member of the Project Management Team has a documented role, so approval authority for design changes is unambiguous rather than assumed.

Why this answer

The scenario states that the Project Management Team structure was never formally documented, leaving team members unsure who can approve design changes. PRINCE2's 'Defined roles and responsibilities' principle requires that the project management team structure be established, documented, and communicated, with clear accountabilities and delegated authority. The absence of this documentation is a direct violation of that principle.

Exam trap

PRINCE2-Practitioner often tests the overlap between 'Defined roles and responsibilities' and 'Manage by exception' — candidates may pick the latter because approval authority is mentioned, missing that the root failure is the undocumented structure.

How to eliminate wrong answers

Option B is wrong because 'Focus on products' concerns defining and delivering products to agreed quality criteria, not the governance structure or approval authority. Option C is wrong because 'Tailor to suit the project' is about adapting PRINCE2 to the project's environment, not about documenting who approves changes. Option D is wrong because 'Manage by exception' is about delegating authority within tolerances — while related, the failure here is the absence of any defined structure, not a failure to set tolerances.

13
MCQmedium

A project manager is analyzing a newly identified risk regarding potential supply chain disruption. After assessing its probability and impact, the project manager decides to engage with a key supplier to redesign the component to use locally sourced, sustainable materials instead. Which risk response category does this represent?

A.Avoid
B.Share
C.Transfer
D.Reduce
AnswerD

Redesigning the component to use locally sourced materials lowers the probability and impact of supply chain disruption, which is the PRINCE2 'Reduce' response. It changes the risk itself rather than transferring, avoiding, sharing or accepting it, so it fits the assessed threat directly.

Why this answer

Engaging with a key supplier to redesign the component to use locally sourced, sustainable materials reduces the probability and/or impact of the supply chain disruption risk. This is a 'Reduce' (or 'Mitigate') response, as it takes proactive action to lessen the risk.

Exam trap

PRINCE2-Practitioner often tests the definitions of risk responses, and candidates may confuse 'Reduce' with 'Avoid' or 'Transfer' when the action involves modifying the approach to lessen the risk.

How to eliminate wrong answers

Option A is wrong because 'Avoid' would mean eliminating the risk entirely, such as by not using that supplier or not requiring the component at all. Option B is wrong because 'Share' involves sharing the risk with a third party, often through insurance or contracts, which is not the case here. Option C is wrong because 'Transfer' involves shifting the risk to another party, such as through insurance or outsourcing, but here the project is actively working to reduce the risk.

14
Multi-Selecthard

Which THREE of the following factors should be considered when applying the PRINCE2 principle 'Tailor to suit the project'?

Select 3 answers
A.The requirement to alter mandatory PRINCE2 principles to suit executive convenience.
B.The risk profile and geographical dispersion of the project team.
C.The personal preferences and favorite management frameworks of individual team members.
D.The scale, complexity, and importance of the project.
E.The organizational culture, environment, and existing corporate governance standards.
AnswersB, D, E

Tailoring must reflect the project's risk profile and team dispersion, since these determine how much formality, control and communication structure the method needs. Higher risk or geographically spread teams require adapted governance, satisfying the stem's requirement to consider these factors when tailoring.

Why this answer

Option B is correct because tailoring must reflect the project's risk profile and the geographical dispersion of the team, which directly affect how processes, roles, and communication are adapted. Option D is correct because the scale, complexity, and importance of the project determine the appropriate level of formality, documentation, and control applied to PRINCE2. Option E is correct because tailoring must align with the organization's culture, environment, and existing corporate governance standards so PRINCE2 integrates with, rather than conflicts with, established practices.

Option A is wrong because PRINCE2 principles are mandatory and cannot be altered or omitted to suit executive convenience; only the processes, themes, and terminology are tailored. Option C is wrong because tailoring is driven by project and organizational factors, not by individual team members' personal preferences or favorite management frameworks.

Exam trap

PRINCE2-Practitioner often tests the misconception that tailoring allows you to change or skip principles — candidates pick options about altering principles or following personal preferences, but the exam expects you to know that principles are mandatory and tailoring is driven by project and organizational factors.

15
MCQeasy

Before closing a project, the Project Manager compiles a report detailing what went well and what went poorly, storing it in the corporate repository for future project managers to access. Which PRINCE2 principle is this fulfilling?

A.Continued business justification
B.Tailor to suit the project
C.Learn from experience
D.Focus on products
AnswerC

Capturing lessons on what went well and poorly, then storing them in the corporate repository, ensures future projects benefit from this experience. That directly fulfils the Learn from experience principle, which requires lessons to be recorded and shared throughout and after the project.

Why this answer

The scenario describes compiling a report on what went well and what went poorly and storing it for future project managers. This directly fulfills the 'Learn from experience' principle, which requires PRINCE2 projects to learn from previous projects and to capture lessons for future ones. The other principles do not specifically address this activity.

Exam trap

PRINCE2-PRACTITIONER often tests the principles by presenting scenarios that sound like one principle but actually map to another; candidates may confuse 'Learn from experience' with 'Continued business justification' when the scenario involves post-project review.

How to eliminate wrong answers

Option A is wrong because 'Continued business justification' ensures the project remains viable, not capturing lessons. Option B is wrong because 'Tailor to suit the project' involves adapting PRINCE2 to the project's environment, not storing lessons. Option D is wrong because 'Focus on products' emphasizes defining and delivering products, not learning from experience.

16
MCQmedium

A Team Manager wants to establish how frequently team progress should be reported to the Project Manager. Which report should be set up for this purpose?

A.Highlight Report
B.Checkpoint Report
C.Exception Report
D.End Stage Report
AnswerB

The Checkpoint Report is the mechanism for frequent progress updates from a Team Manager to the Project Manager, satisfying the stem's need to establish reporting frequency. Its cadence is defined by the Work Package's reporting requirements, so it directly answers how often team progress is reported.

Why this answer

The Checkpoint Report is the progress report produced by the Team Manager and sent to the Project Manager at a frequency defined in the Work Package. It reports on the status of the work package, including progress, issues, and next steps, which is exactly what the Team Manager needs to establish for reporting team progress.

Exam trap

PRINCE2-Practitioner often tests the direction and audience of each report — candidates who confuse Checkpoint (Team Manager to Project Manager) with Highlight (Project Manager to Board) will pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because the Highlight Report is produced by the Project Manager and sent to the Project Board, not from the Team Manager to the Project Manager. Option C is wrong because the Exception Report is produced when a stage or project is predicted to exceed its tolerances, not for routine progress reporting. Option D is wrong because the End Stage Report is produced by the Project Manager at the end of a stage for the Project Board, not for team progress reporting.

17
MCQeasy

Which PRINCE2 process is used by the Project Board to provide overall governance and control throughout the life of the project?

A.Managing Product Delivery
B.Directing a Project
C.Initiating a Project
D.Controlling a Stage
AnswerB

Directing a Project is the board-level process spanning the whole project, giving overall governance and control. It authorises initiation, stage boundaries, closure and ad hoc direction, satisfying the stem's requirement for board oversight throughout the project life.

Why this answer

Directing a Project (DP) is the process used by the Project Board to provide overall governance and control throughout the life of the project. It covers the Project Board's key decision points: authorizing initiation, authorizing the project, authorizing stage boundaries, giving ad-hoc direction, and authorizing project closure. DP runs from the pre-project phase through to project closure, making it the only process that spans the entire project lifecycle from a governance perspective.

Exam trap

PRINCE2-Practitioner often tests whether candidates know that Directing a Project is the Project Board's governance process spanning the whole project, catching those who confuse it with Controlling a Stage (Project Manager's process) or Initiating a Project (a one-time process).

How to eliminate wrong answers

Option A is wrong because Managing Product Delivery is the Team Manager's process for accepting, executing, and delivering Work Packages — it is a delivery-level process, not a governance process. Option C is wrong because Initiating a Project is a time-bound process that produces the PID and is completed once the Project Board authorizes the project; it does not provide ongoing governance. Option D is wrong because Controlling a Stage is the Project Manager's day-to-day delivery-control process during a stage, not the Project Board's governance process.

18
MCQeasy

In the PRINCE2 Quality practice, what is the primary purpose of a quality review meeting?

A.To examine a product against its quality criteria and detect defects.
B.To negotiate project budget increases with corporate management.
C.To brainstorm project risks and opportunities.
D.To evaluate team members' annual performance appraisals.
AnswerA

A quality review brings together the producer, reviewers and chair to inspect the product against its agreed quality criteria, identifying and logging defects. This directly satisfies the stem's requirement to examine the product and detect defects before approval.

Why this answer

In PRINCE2's Quality practice, a quality review meeting is a structured examination of a product against its quality criteria to detect and correct defects before the product is approved. It involves defined roles (Chair, Presenter, Reviewer, Scribe) and follows a formal agenda: review the product, identify defects, and agree on corrective actions. The primary purpose is to verify conformance to specifications, not to discuss budget, risks, or personnel.

Exam trap

PRINCE2-Practitioner often tests the confusion between Quality practice activities (quality reviews, quality control, quality assurance) and other practices like Risk or Business Case — candidates pick answers that sound like general project meetings but do not match the specific purpose of a quality review.

How to eliminate wrong answers

Option B is wrong because budget negotiations with corporate management are not part of the Quality practice — they belong to the Business Case and Progress practices, and quality reviews focus on product conformance, not funding. Option C is wrong because brainstorming risks and opportunities is the domain of the Risk practice, not Quality; quality reviews examine products against criteria, not uncertainties. Option D is wrong because evaluating team members' performance appraisals is a line-management activity, not a PRINCE2 quality review, which is product-focused and not personnel-focused.

19
MCQeasy

Which process provides the Project Board with the mechanism to authorize a project's initiation?

A.Starting up a Project
B.Directing a Project
C.Controlling a Stage
D.Initiating a Project
AnswerB

Directing a Project provides the Project Board's decision points, including authorising initiation via the DP1 activity after the Starting up a Project mandate and project brief. This satisfies the stem, as DP is the process granting that authorisation.

Why this answer

Directing a Project (DP) is the process that provides the Project Board with the mechanism to authorize project initiation. Specifically, DP1 Authorize Initiation is the activity where the Project Board reviews the Project Brief and authorizes the Project Manager to proceed with the Initiating a Project process. This is a formal decision point owned by the Project Board.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between Starting up a Project (pre-project preparation) and Directing a Project (Board authorization), so candidates must remember that authorization of initiation is a DP activity, not an SU activity.

How to eliminate wrong answers

Option A is wrong because Starting up a Project is the pre-project process that prepares the Project Brief and is triggered by the mandate; it does not include Project Board authorization of initiation. Option C is wrong because Controlling a Stage is the Project Manager's process for managing day-to-day work within a stage, not for authorizing initiation. Option D is wrong because Initiating a Project is the process where the Project Manager develops the PID; it is authorized by DP, not the authorizing process itself.

20
MCQhard

A project is operating under the Directing a Project (DP) process. The Executive leaves the organization unexpectedly. What action must the Project Board and Corporate level take within the DP framework?

A.The Project Manager automatically assumes the Executive role and approves their own reports.
B.Corporate must appoint a replacement Executive to maintain governance and business justification.
C.The project must be permanently closed immediately without appointing a successor.
D.The Senior Supplier takes over executive responsibilities and project funding.
AnswerB

The Executive owns the Business Case and chairs the Project Board, so their departure removes the role accountable for continued business justification. Corporate, which appoints the Executive, must name a replacement; otherwise the DP framework has no one able to authorise continued investment or decision-making.

Why this answer

The Executive is a mandatory Project Board role and is personally accountable for the business case. If the Executive leaves, corporate or programme management must appoint a replacement to maintain governance and ensure the project continues to have a valid business justification. Without an Executive, the Project Board cannot function properly.

Exam trap

The trap is assuming the Project Manager or another Board member can absorb the Executive role, when PRINCE2 requires corporate-level appointment of a replacement to preserve governance.

How to eliminate wrong answers

Option A is wrong because the Project Manager cannot assume a Project Board role — PRINCE2 requires separation between the Board and the Project Manager, and self-approval would violate governance. Option C is wrong because closing the project immediately is not required; the correct action is to replace the Executive so the project can continue if still justified. Option D is wrong because the Senior Supplier represents supplier interests and does not own the business case or funding; those are Executive responsibilities.

21
MCQhard

A project is using agile delivery methods within a PRINCE2 framework. The Project Board wants to receive progress updates on product increments rather than lengthy narrative reports. Which PRINCE2 progress reporting product should be tailored to meet this need?

A.Highlight Report
B.Checkpoint Report
C.Daily Log
D.End Stage Report
AnswerA

The Highlight Report is the progress product summarising status at a point in time, so it can be tailored to report product increments rather than narrative. This satisfies the Project Board's request for concise increment-based updates within the PRINCE2 framework.

Why this answer

The Highlight Report is a PRINCE2 progress report produced by the Project Manager for the Project Board at regular intervals, summarizing progress, status, and issues. It can be tailored to focus on product increments and agile metrics, making it suitable for the Project Board's need for concise updates. The Checkpoint Report is for the Team Manager to the Project Manager, and the End Stage Report is at stage boundaries.

Exam trap

PRINCE2-Practitioner often tests the audience and purpose of progress reports, so candidates who confuse the Checkpoint Report (internal to team) with the Highlight Report (to the Board) choose the wrong answer.

How to eliminate wrong answers

Option B is wrong because the Checkpoint Report is used by Team Managers to report progress to the Project Manager, not to the Project Board, and it focuses on work package status. Option C is wrong because the Daily Log is a personal record for the Project Manager, not a formal progress report to the Board. Option D is wrong because the End Stage Report is produced at the end of a stage, not for regular progress updates on increments.

22
Multi-Selecthard

When managing organizational change within a PRINCE2 7 project context, which THREE of the following strategies help ensure sustainable behavioral adoption?

Select 3 answers
A.Relying solely on strict contractual enforcement and punitive measures for non-compliance
B.Isolating the project team from business operations to prevent any operational feedback
C.Involving impacted end-users in co-designing training programs and transition workflows
D.Establishing clear feedback channels and support networks to help staff navigate the transition
E.Securing active, visible sponsorship from senior business leaders who model the new behaviors
AnswersC, D, E

Co-designing training and workflows with impacted end-users builds ownership and ensures the change fits actual working practise, rather than being imposed. This satisfies the sustainable behavioural adoption constraint, since participants who shape the transition are more likely to embed and maintain new behaviours.

Why this answer

Option C is correct because co-designing training and transition workflows with impacted end-users builds ownership and relevance, which increases the likelihood that new behaviors are actually embedded rather than merely mandated. Option D is correct because clear feedback channels and support networks provide the reinforcement, coaching, and issue-resolution mechanisms that sustain behavioral change after go-live. Option E is correct because visible senior sponsorship that models the desired behaviors signals priority and legitimacy, a key enabler of sustainable adoption in PRINCE2 7's people-focused change approach.

Option A does not belong because contractual enforcement and punitive measures may drive superficial compliance but not durable behavioral adoption. Option B does not belong because isolating the project team from business operations blocks the operational feedback and engagement needed for successful change.

Exam trap

PRINCE2-Practitioner often tests the misconception that strict contractual enforcement or isolating the team can drive adoption, confusing compliance with commitment.

23
MCQmedium

A Project Board delegates day-to-day control of a project stage to the Project Manager, stepping in only when agreed limits for cost and time are forecast to be exceeded. Which PRINCE2 principle does this governance model represent?

A.Defined roles and responsibilities
B.Tailor to suit the project
C.Manage by exception
D.Manage by stages
AnswerC

Manage by exception defines tolerances for cost and time, within which the Project Manager runs the stage without Board intervention; escalation occurs only when a forecast breach is imminent. This matches the stem's delegated day-to-day control with agreed limits, satisfying the principle's requirement for pre-defined boundaries and defined escalation points.

Why this answer

The scenario describes the Project Board delegating day-to-day control to the Project Manager and only intervening when agreed tolerances for cost and time are forecast to be exceeded. This is the definition of the 'Manage by exception' principle, which establishes tolerances and defines escalation procedures when those tolerances are threatened. The Board's role is to manage by exception, focusing on strategic decisions and only stepping in when exceptions occur.

Exam trap

PRINCE2-PRACTITIONER often tests the difference between 'Manage by exception' and 'Manage by stages' — candidates may focus on the stage aspect, but the key is the delegation within tolerances and escalation only when exceeded.

How to eliminate wrong answers

Option A is wrong because 'Defined roles and responsibilities' is about clearly defining who does what in the project, not about the delegation and tolerance mechanism. Option B is wrong because 'Tailor to suit the project' is about adapting PRINCE2 to the project's size, complexity, and environment, not about governance by exception. Option D is wrong because 'Manage by stages' is about dividing the project into stages for control and planning, not about the delegation of authority within tolerances.

24
MCQeasy

In the PRINCE2 Issues practice, what is the purpose of an Issue Report?

A.To log identified project risks.
B.To provide a detailed analysis and recommendation for a formal issue requiring Project Board decision.
C.To summarize overall stage progress periodically.
D.To record daily meeting minutes of the project team.
AnswerB

An Issue Report records and analyses a formal issue, capturing impact assessment and options, then recommends a course of action for the Project Board to decide, since the matter exceeds the Project Manager's delegated tolerance.

Why this answer

The Issue Report is the PRINCE2 document used to capture, analyse, and manage any issue (including problems, concerns, or change requests) that requires formal management attention. When an issue is escalated for a Project Board decision, the Issue Report contains the detailed analysis, options, and a recommendation so the Board can make an informed decision. It is not merely a log — it is the vehicle for formal issue resolution.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the Issue Register (a log of all issues) and the Issue Report (a detailed analysis and recommendation for a specific issue requiring a decision), so candidates must remember that the Report is the escalation document, not the log.

How to eliminate wrong answers

Option A is wrong because risks are recorded in the Risk Register, not the Issue Report; the Issue Report is used for issues that have already materialised or require formal change control. Option C is wrong because stage progress is summarised in the End Stage Report (and Highlight Reports during the stage), not in an Issue Report. Option D is wrong because daily team meeting minutes are captured in the Daily Log (or team logs), not in an Issue Report, which is reserved for formal issues requiring management action.

25
Multi-Selectmedium

Which THREE of the following activities are part of the Controlling a Stage (CS) process?

Select 3 answers
A.Authorizing project closure
B.Preparing the initial Project Brief
C.Authorizing a Work Package
D.Capturing and assessing issues and risks
E.Reviewing work package status
AnswersC, D, E

Authorising a Work Package sits squarely in Controlling a Stage, where the Project Manager allocates work, sets tolerances and confirms acceptance criteria with the Team Manager. It satisfies the stem's requirement for CS activities, unlike Managing Product Delivery, which receives and executes the Work Package.

Why this answer

Option C (Authorizing a Work Package) is correct because Controlling a Stage includes the activity of authorizing work packages to team managers once the stage plan and tolerances allow, using the Work Package authorization process. Option D (Capturing and assessing issues and risks) is correct because CS covers the ongoing capture, assessment, and management of issues and risks as they arise during the stage, feeding into the Issue and Risk Registers and stage-level decision making. Option E (Reviewing work package status) is correct because CS includes reviewing work package progress through checkpoints and reports, comparing actuals against the stage plan, and taking corrective action within stage tolerances.

Option A (Authorizing project closure) does not belong because closure is handled in the Closing a Project (CP) process, not CS. Option B (Preparing the initial Project Brief) does not belong because that is part of Starting up a Project (SU), which occurs before the project is authorized and before any stage is controlled.

Exam trap

PRINCE2-PRACTITIONER often tests the boundaries between processes; candidates may confuse activities from Controlling a Stage with those from Closing a Project or Starting Up a Project, leading to incorrect selections.

26
MCQeasy

An issue has been raised concerning a disagreement between the Senior User and a Supplier regarding product acceptance criteria. What type of issue is this?

A.A Risk Entry
B.A Request for Change
C.An Exception Report
D.A Problem or Concern
AnswerD

A disagreement over acceptance criteria is not a formal change to baseline products or a request for change; it is an unresolved conflict requiring resolution. PRINCE2 classifies such disagreements as problems or concerns, distinct from change requests and off-specifications.

Why this answer

In PRINCE2, an issue is any relevant event that has happened and requires management action. Issues are categorized as either a Request for Change (RFC) or a Problem/Concern. A disagreement between the Senior User and a Supplier about product acceptance criteria is not a change request — it is a problem or concern that needs resolution.

It is logged in the Issue Register and managed through the Issue and Change Control procedure.

Exam trap

PRINCE2-Practitioner often tests the confusion between issue types — candidates pick 'Request for Change' whenever a product or criteria is mentioned, but the correct classification depends on whether the issue proposes a modification (RFC) or is a disagreement/problem (Problem/Concern).

How to eliminate wrong answers

Option A (Risk Entry) is wrong because a risk is an uncertain future event, whereas this disagreement has already occurred and is therefore an issue, not a risk. Option B (Request for Change) is wrong because an RFC proposes a modification to a baselined product or specification; a disagreement about acceptance criteria is a problem to be resolved, not a formal change proposal. Option C (Exception Report) is wrong because an Exception Report is a Progress practice document that describes a forecast breach of tolerances and is not a type of issue.

27
MCQhard

A project is incorporating ESG (Environmental, Social, and Governance) principles. In which practice is the overall sustainability strategy for the project's outputs and outcomes formally documented and justified?

A.The Business Case practice
B.The Organizing practice
C.The Quality practice
D.The Risk practice
AnswerA

The Business Case practice documents and justifies the project's rationale, including benefits, costs and sustainability. ESG strategy for outputs and outcomes is formally captured there, satisfying the stem's requirement that the overall sustainability strategy be documented and justified in one practice.

Why this answer

The Business Case practice in PRINCE2 is where the justification for the project — including benefits, costs, risks, and now sustainability/ESG considerations — is documented and continuously reviewed. The Business Case captures the 'why' of the project, so any overarching sustainability strategy affecting the project's outputs and outcomes must be formally justified there. ESG principles are treated as part of the value proposition and dis-benefits analysis within the Business Case.

Exam trap

PRINCE2-Practitioner often tests the misconception that sustainability or ESG belongs to the Quality practice (because it sounds like a 'quality' attribute) or to Risk (because it involves trade-offs) — the correct anchor is always the Business Case, which owns the 'why' and the value justification.

How to eliminate wrong answers

Option B (Organizing) is wrong because the Organizing practice defines roles, responsibilities, and the project management team structure — it does not document strategic justification or sustainability rationale. Option C (Quality) is wrong because the Quality practice focuses on product specifications, quality criteria, and acceptance methods, not on the strategic justification of ESG outcomes. Option D (Risk) is wrong because the Risk practice manages uncertainty and its responses, not the formal documentation of sustainability strategy or benefits justification.

28
MCQeasy

A team member identifies a variance in project progress where a work package is running two weeks late. According to the Issues practice, what is the immediate first step the Project Manager should take?

A.Immediately issue an Exception Report to the Project Board.
B.Close the work package and assign the tasks to a new contractor.
C.Capture and log the issue in the Issue Register.
D.Modify the Stage Plan tolerance without consulting anyone.
AnswerC

The Issues practice requires every issue to be captured and logged in the Issue Register before any assessment or action. Logging the work package delay first creates the formal record needed for subsequent impact analysis and decision-making.

Why this answer

According to PRINCE2's Issues practice, any variance or potential problem should first be captured and logged in the Issue Register. The Project Manager then assesses and decides how to handle it, which may include escalating if tolerances are threatened. Logging the issue ensures it is tracked and managed through the issue and change control procedure.

Exam trap

PRINCE2-PRACTITIONER often tests the sequence of issue handling; the trap is jumping straight to an Exception Report before capturing and assessing the issue in the Issue Register.

How to eliminate wrong answers

Option A is wrong because an Exception Report is only issued when stage or project tolerances are forecast to be breached, and it goes to the Project Board after assessment, not as an immediate first step. Option B is wrong because closing the work package and reassigning tasks is a premature action without assessment or approval. Option D is wrong because modifying Stage Plan tolerances without consultation violates change control and the Project Board's authority.

29
MCQmedium

During the Closing a Project process, why is it important to archive the project records and documentation?

A.To overwrite the original Business Case with fictional success metrics.
B.To ensure historical project records are securely stored for future audits and organizational learning.
C.To keep the project officially open so the Project Manager continues receiving a salary.
D.To allow the Project Board to continue managing daily work packages indefinitely.
AnswerB

Archiving preserves the project's records as an auditable trail and a knowledge source, so future teams can reuse lessons and evidence compliance. Secure retention satisfies governance obligations while enabling organisational learning from what the project delivered and how.

Why this answer

Archiving project records during Closing a Project ensures that the historical documentation — including the Business Case, plans, reports, and lessons — is preserved for audit, compliance, and organizational learning. PRINCE2 emphasizes that closing should capture and store information so future projects can benefit from lessons learned and so the organization can demonstrate accountability. This is a core purpose of the Closing a Project process.

Exam trap

PRINCE2-Practitioner often tests whether candidates confuse the purpose of Closing a Project with ongoing management — the trap is picking an option that keeps the project alive or alters records instead of preserving them for audit and learning.

How to eliminate wrong answers

Option A is wrong because overwriting the Business Case with fictional metrics is unethical and contrary to PRINCE2 principles of continued business justification and integrity. Option C is wrong because keeping a project open to pay the Project Manager is not a valid PRINCE2 concept — projects must close when objectives are met or the project is terminated. Option D is wrong because the Project Board does not manage daily work packages; that is the Project Manager's responsibility, and Closing a Project explicitly ends the project, not extends it.

30
MCQhard

A project has experienced an unforecasted external market shift that drastically reduces the expected financial return, causing the Business Case to become unviable. According to the Business Case practice, what is the proper protocol?

A.Escalate the lack of viability to the Project Board so they can prematurely close the project.
B.Absorb the loss by cutting quality criteria across all product descriptions.
C.Transfer the financial shortfall to the Senior User's operational budget.
D.Continue the project until the current stage ends, then close it.
AnswerA

The Business Case is owned by the Project Board, so when viability is lost the Project Manager escalates via an Exception Report; the Board then decides whether to close the project prematurely or redirect it.

Why this answer

Under the PRINCE2 Business Case practice, the Business Case must remain viable throughout the project, and the Project Board owns the decision to continue, change, or stop. When an external market shift makes the Business Case unviable, the correct protocol is to escalate to the Project Board so they can decide whether to prematurely close the project. The Project Manager cannot unilaterally continue an unviable project.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that the Project Manager can absorb or reassign financial impacts; the trap is forgetting that only the Project Board can authorize premature closure of an unviable project.

How to eliminate wrong answers

Option B is wrong because cutting quality criteria to absorb a financial loss is not a valid Business Case response and would undermine product acceptance. Option C is wrong because transferring a financial shortfall to the Senior User's operational budget is not a PRINCE2 mechanism and bypasses Project Board authority. Option D is wrong because continuing until the stage ends ignores the need for immediate escalation and could waste further investment on an unviable project.

31
MCQeasy

In the PRINCE2 Issues practice, what is the primary purpose of the Issue Register?

A.To record completed quality reviews and test results.
B.To list all financial invoices paid to suppliers.
C.To record daily informal notes and thoughts of the Project Manager.
D.To maintain a formal record of all formal issues raised during the project lifecycle.
AnswerD

The Issue Register maintains a formal record of all formal issues raised throughout the project lifecycle, as the stem requires. It captures issue type, severity, priority, status and ownership, giving the Project Manager the management information needed to track and escalate issues.

Why this answer

The Issue Register is a formal management product that captures and tracks all formal issues (problems, concerns, requests for change, and off-specifications) raised during the project. It records details such as issue description, severity, impact analysis, and resolution status, supporting the Issue and Change Control procedure. It is distinct from the Daily Log, which holds informal notes and minor issues.

Exam trap

PRINCE2-Practitioner often tests the confusion between the Issue Register (formal issues) and the Daily Log (informal notes), so candidates pick the Daily Log option for formal issue tracking.

How to eliminate wrong answers

Option A is wrong because completed quality reviews and test results are recorded in the Quality Register, not the Issue Register. Option B is wrong because supplier invoices are financial records handled outside PRINCE2's Issue Register, typically in the project's financial systems. Option C is wrong because daily informal notes and thoughts belong in the Daily Log, which is a private PM tool, not the formal Issue Register.

32
MCQhard

A newly appointed Project Manager finds that the project organization structure has combined the roles of the Executive and the Project Manager into a single individual to save costs. According to PRINCE2 7, what is the primary risk of this configuration?

A.It invalidates the Risk Management Approach.
B.It violates the principle of managing by stages because stage boundaries cannot be approved.
C.It removes the vital separation between the person accountable for business justification and the person managing day-to-day delivery.
D.It prevents the Project Manager from utilizing team managers.
AnswerC

PRINCE2 requires the Executive to own the Business Case while the Project Manager runs day-to-day delivery. Merging them destroys that accountability separation, so no one independently challenges continued viability, directly creating the risk the stem describes.

Why this answer

In PRINCE2 7, the Executive is accountable for the business justification and represents the business interests, while the Project Manager manages day-to-day delivery. Combining these roles removes the separation of accountability and delivery, which is a fundamental check and balance. This creates a conflict of interest and undermines the principle of defined roles and responsibilities.

Exam trap

PRINCE2-Practitioner often tests the principle of separation of duties, so candidates who focus on cost savings or flexibility miss the governance risk of combining Executive and Project Manager roles.

How to eliminate wrong answers

Option A is wrong because the Risk Management Approach is a separate document and is not invalidated by role combination; the risk is governance, not the approach itself. Option B is wrong because managing by stages can still occur; the Project Board (which includes the Executive) approves stage boundaries, but if the Executive is also the Project Manager, the approval becomes self-approval, which is a governance issue, not a violation of the principle per se. Option D is wrong because the Project Manager can still utilize Team Managers; the combination does not prevent delegation of work packages.

33
MCQeasy

In the PRINCE2 Quality practice, what is the purpose of a Product Description?

A.To schedule team activities on a Gantt chart.
B.To outline the project budget and financial cash flow.
C.To log all project risks and their mitigation actions.
D.To define an individual product's purpose, composition, derivation, and quality criteria.
AnswerD

A Product Description defines an individual product's purpose, composition, derivation, and quality criteria, forming the basis for quality planning, testing, and acceptance. It applies to each product rather than the project as a whole, satisfying the Quality practice's requirement.

Why this answer

The Product Description is a PRINCE2 document that defines an individual product's purpose, composition, derivation, and quality criteria. It is created during product-based planning and forms the basis for agreeing what must be produced and how it will be quality-checked. Option D captures all four required elements of a Product Description as defined in the PRINCE2 Quality practice.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between the Product Description and other PRINCE2 documents such as the Risk Register, Business Case, and Quality Register, so candidates must remember that the Product Description is specifically about defining an individual product's attributes and quality criteria.

How to eliminate wrong answers

Option A is wrong because scheduling team activities on a Gantt chart is a project planning/scheduling activity, not the purpose of a Product Description. Option B is wrong because outlining the project budget and financial cash flow relates to the Business Case and financial planning, not to defining an individual product. Option C is wrong because logging project risks and mitigation actions is the purpose of the Risk Register, not the Product Description.

34
MCQhard

A company is utilizing an agile delivery method alongside PRINCE2. The Project Manager integrates sprint reviews to ensure stakeholder engagement and product validation at the end of each short iteration. Which PRINCE2 principle is primarily reinforced by this integration?

A.Manage by exception
B.Continued business justification
C.Learn from experience
D.Tailor to suit the project
AnswerD

Tailoring is the principle of adapting PRINCE2 to the project's context. Blending agile sprint reviews into the delivery approach modifies the method to fit an agile environment, satisfying the stem's requirement to integrate short iterations while retaining PRINCE2 governance and stakeholder validation.

Why this answer

'Tailor to suit the project' requires PRINCE2 to be adapted to the project's size, complexity, environment, and delivery approach. Integrating agile sprint reviews into a PRINCE2 project is a classic tailoring decision that combines PRINCE2 governance with agile delivery cadence. The principle explicitly supports using alternative delivery methods while retaining PRINCE2's governance framework.

Exam trap

The trap here is confusing 'tailor to suit the project' with 'learn from experience' — candidates see iterative reviews and assume lessons-learned is the driving principle, missing that the integration of an agile method is fundamentally a tailoring decision.

How to eliminate wrong answers

Option A is wrong because 'manage by exception' concerns tolerance-based delegation and escalation, not the integration of agile ceremonies. Option B is wrong because 'continued business justification' concerns whether the project remains viable, which is not what sprint reviews primarily reinforce. Option C is wrong because 'learn from experience' concerns capturing and applying lessons, which is a by-product of sprint reviews but not the primary principle being applied when integrating an agile method.

35
MCQeasy

In the PRINCE2 Progress practice, what is the name of the report produced by a Team Manager to inform the Project Manager of team-level progress?

A.Highlight Report
B.Exception Report
C.Checkpoint Report
D.End Stage Report
AnswerC

The Checkpoint Report is the progress report a Team Manager produces at agreed intervals to update the Project Manager on team-level progress, covering status, issues and next period's work. It satisfies the stem's requirement for the team-to-project-manager reporting mechanism within the Progress practice.

Why this answer

In PRINCE2, the Checkpoint Report is produced by the Team Manager and provided to the Project Manager at a frequency defined in the Work Package. It reports on the status of the work package, including progress, issues, and risks. This is distinct from the Highlight Report, which the Project Manager sends to the Project Board.

Exam trap

PRINCE2-Practitioner often confuses Checkpoint Report with Highlight Report; remember that Checkpoint is Team Manager to Project Manager, while Highlight is Project Manager to Project Board.

How to eliminate wrong answers

Option A is wrong because the Highlight Report is produced by the Project Manager for the Project Board, not by the Team Manager. Option B is wrong because the Exception Report is produced when tolerances are threatened or breached, and it is escalated to the Project Board. Option D is wrong because the End Stage Report is produced by the Project Manager at the end of a stage for the Project Board.

36
MCQeasy

A Project Manager is leading a project to develop a new mobile application. The project board has defined tolerances for time, cost, and scope. During a stage, the Project Manager discovers that the actual cost is forecast to exceed the stage cost tolerance by 10%. According to the PRINCE2 principle 'Manage by exception', what should the Project Manager do?

A.Request additional funds from the finance department without involving the project board.
B.Take corrective action to bring the cost back within tolerance and continue without informing the project board.
C.Immediately escalate the issue to the project board by producing an Exception Report.
D.Do nothing until the end of the stage, then report the overspend in the End Stage Report.
AnswerC

This is correct because the principle 'Manage by exception' requires that the Project Manager only escalates to the project board when a tolerance is forecast to be exceeded. Since the cost forecast exceeds the stage tolerance, the Project Manager must raise an Exception Report to inform the project board and seek a decision on how to proceed.

Why this answer

The principle 'Manage by exception' establishes that the Project Manager has delegated authority to manage within agreed tolerances and must escalate to the project board only when a tolerance is forecast to be exceeded. In this scenario, the cost forecast exceeds the stage tolerance, so the Project Manager must produce an Exception Report and escalate to the board for a decision.

Exam trap

The trap here is to assume that the Project Manager should try to resolve the overspend independently, when the principle 'Manage by exception' requires escalation as soon as a tolerance breach is forecast.

37
MCQhard

An organization applies PRINCE2 and uses rolling wave planning within the Plans practice. During Stage 2 execution, the Project Manager begins detailed planning for Stage 3. New environmental regulations come into light that require a complete redesign of Stage 3 deliverables. How should the Plans practice accommodate this?

A.Halt the entire project permanently without reviewing options.
B.Submit an Exception Report for Stage 2.
C.Incorporate the regulatory requirements into the detailed Stage 3 Plan during the stage boundary review for Stage 2/3.
D.Ignore the new regulations because Stage 3 was already outlined in the high-level Project Plan.
AnswerC

Rolling wave planning defers detailed planning of later stages until their boundary approaches. The new regulations are therefore incorporated into the detailed Stage 3 Plan during the Stage 2/3 boundary review, where the next stage plan is produced and approved.

Why this answer

In PRINCE2, rolling wave planning allows detailed planning for the next stage while later stages remain high-level. When new environmental regulations emerge that require redesign of Stage 3 deliverables, these should be incorporated into the detailed Stage 3 Plan during the stage boundary review for Stage 2/3. This ensures the plan remains accurate and aligned with the latest requirements.

Exam trap

PRINCE2-Practitioner often tests the timing of incorporating changes into plans, and candidates may incorrectly choose to raise an Exception Report or ignore the change instead of updating the next stage plan at the stage boundary.

How to eliminate wrong answers

Option A is wrong because halting the project permanently is an extreme reaction that ignores the possibility of adapting the plan; PRINCE2 emphasizes managing by exception and considering options. Option B is wrong because an Exception Report is only required if tolerances are forecast to be exceeded; there is no indication of that here. Option D is wrong because ignoring new regulations is unacceptable and violates the principle of business justification and compliance; the high-level Project Plan can be updated as needed.

38
MCQhard

A PRINCE2 project is being tailored for a small internal IT upgrade. The Project Manager proposes that the project board will consist of only the Project Manager and the Team Manager, and that the project will be managed as a single stage. Which principle is being compromised?

A.Tailor to suit the project environment
B.Manage by exception
C.Manage by stages
D.Defined roles and responsibilities
AnswerD

This is correct because the principle 'Defined roles and responsibilities' requires that the project has a clear organizational structure with defined roles, including a project board with business, user, and supplier representation. The proposed structure lacks these three primary stakeholder interests, compromising the principle.

Why this answer

The PRINCE2 principle 'Defined roles and responsibilities' requires that projects have a clear organizational structure with defined roles, including a project board that represents the business, user, and supplier interests. The proposed structure of only the Project Manager and Team Manager lacks these three stakeholder perspectives, which compromises the principle. While tailoring is allowed, it must not violate the principles.

Exam trap

The trap here is to focus on the single stage aspect and select 'Manage by stages', but the more fundamental violation is the lack of a properly constituted project board, which relates to defined roles and responsibilities.

39
MCQhard

A project is operating under the Controlling a Stage (CS) process. A supplier has delivered a Work Package product, but the quality inspection reveals that it does not meet the specified tolerance. What action should the Project Manager take under CS?

A.Escalate immediately to the Project Board requesting project closure.
B.Initiate the Closing a Project process immediately.
C.Raise an issue and instruct the Team Manager to rectify the defect, ensuring it remains within stage tolerances.
D.Accept the defective product anyway and update the Project Product Description to match the substandard output.
AnswerC

A failed quality inspection means the Work Package product breaches its specification, so the Project Manager records it as an issue and directs the Team Manager to correct the defect. Handling it within the stage keeps the deviation inside stage tolerances, avoiding escalation to the Project Board.

Why this answer

Under Controlling a Stage (CS), when a delivered product fails quality inspection, the Project Manager treats it as an issue. The Project Manager raises an issue, assesses it against stage tolerances, and if it can be resolved within tolerance, instructs the Team Manager to take corrective action (rectify the defect) via a revised Work Package. This keeps the project within the delegated authority of the Project Manager and avoids unnecessary escalation to the Project Board.

Exam trap

PRINCE2-Practitioner often tests the boundary between 'corrective action within tolerance' and 'escalation via Exception Report' — candidates frequently jump straight to escalation or closure when the correct first step is to raise an issue and attempt corrective action within delegated tolerances.

How to eliminate wrong answers

Option A is wrong because escalating to the Project Board for project closure is a disproportionate response — escalation only occurs if stage tolerances are forecast to be breached, and even then the Board decides on corrective action, not automatic closure. Option B is wrong because Closing a Project is triggered when the project is complete or terminated, not when a single product fails a quality check mid-stage. Option D is wrong because accepting a defective product and amending the Project Product Description to match substandard output is a fundamental breach of quality management — it undermines the agreed acceptance criteria and would corrupt the project's baseline.

40
MCQeasy

In the PRINCE2 Risk practice, what is the name of the log used to capture and maintain information on all identified threats and opportunities?

A.Issue Register
B.Daily Log
C.Quality Register
D.Risk Register
AnswerD

The Risk Register is the single log capturing every identified threat and opportunity, recording cause, probability, impact, proximity, and response. It satisfies the stem's requirement for the log maintaining information on all identified risks throughout the PRINCE2 Risk practice.

Why this answer

In PRINCE2, the Risk Register is the log used to capture and maintain information on all identified threats and opportunities. It records risk descriptions, likelihood, impact, proximity, and responses. The Issue Register, Daily Log, and Quality Register serve different purposes.

Exam trap

PRINCE2-Practitioner often tests the distinction between the Risk Register and the Issue Register. Candidates may confuse the two, forgetting that risks are potential future events, while issues are current problems.

How to eliminate wrong answers

Option A is wrong because the Issue Register records issues (problems or concerns) that have already occurred, not risks. Option B is wrong because the Daily Log is used by the Project Manager to record informal notes and actions, not formal risk information. Option C is wrong because the Quality Register records quality activities and results, not risks.

41
Multi-Selectmedium

Which TWO of the following are true regarding the Quality practice in PRINCE2 7? (Choose two)

Select 2 answers
A.Quality reviews are optional and only conducted if the budget permits.
B.Team Managers are responsible for approving the overarching Quality Management Approach.
C.Quality management requires defining customer quality expectations and acceptance criteria.
D.The Quality Management Approach describes how quality will be managed on the project.
E.Project managers should encourage teams to exceed agreed acceptance criteria ('gold-plating').
AnswersC, D

Quality management in PRINCE2 7 begins with capturing the customer's quality expectations and the acceptance criteria against which the final product will be judged. This satisfies the stem's requirement for a true statement about the Quality practice, since acceptance criteria must be defined before quality planning can proceed.

Why this answer

Option C is correct because PRINCE2 7's Quality practice begins by capturing the customer's quality expectations and then translating them into measurable acceptance criteria that products must satisfy. Option D is correct because the Quality Management Approach is the document that defines how quality will be managed across the project, including roles, responsibilities, standards, and techniques. Option A is wrong because quality reviews are a planned, mandatory part of the quality management approach, not an optional activity contingent on budget.

Option B is wrong because the Project Board (not Team Managers) approves the Quality Management Approach, which is part of the project initiation documentation. Option E is wrong because PRINCE2 explicitly discourages 'gold-plating' — delivering more than the agreed acceptance criteria is out of scope and a form of scope creep.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that quality reviews are optional or that Team Managers approve the Quality Management Approach, when in fact the Project Board approves it and reviews are mandatory.

42
MCQhard

A project is executing the Managing Product Delivery (MP) process. A Team Manager identifies that a Work Package cannot be completed within the agreed time due to an unforeseen technical bottleneck. What must the Team Manager do?

A.Directly submit an Exception Report to the Project Board.
B.Cancel the entire stage and re-plan the project.
C.Extend the Work Package end date unilaterally without notifying anyone.
D.Raise an issue and alert the Project Manager so that corrective action or escalation can be initiated.
AnswerD

A Work Package that cannot meet its agreed tolerances must be escalated, not absorbed locally. Raising an issue alerts the Project Manager, who can take corrective action or escalate to the Project Board, preserving PRINCE2's management-by-exception principle.

Why this answer

Under Managing Product Delivery (MP), the Team Manager is accountable for delivering the Work Package within the agreed tolerances. If a technical bottleneck means the Work Package cannot be completed within time tolerance, the Team Manager must raise an issue and inform the Project Manager, who can then take corrective action or escalate via an Exception Report if stage tolerances are threatened. The Team Manager has no authority to escalate directly to the Project Board or to unilaterally change baselines.

Exam trap

The trap is confusing the Team Manager's escalation path — candidates often assume the Team Manager can escalate directly to the Project Board or unilaterally adjust dates, when in fact all escalation must go through the Project Manager and respect the Work Package and stage tolerances.

How to eliminate wrong answers

Option A is wrong because the Team Manager does not report directly to the Project Board — escalation flows through the Project Manager, who owns the Exception Report and the stage-level tolerance assessment. Option B is wrong because cancelling an entire stage and re-planning the project is a Project Board decision triggered by a forecast breach of stage tolerances, not a Team Manager action. Option C is wrong because unilaterally extending the Work Package end date without notification violates the Work Package agreement and the change control approach — all changes to baselined dates must go through the Project Manager.

43
MCQeasy

A project manager is recording an uncertainty that could have a positive impact on the project schedule. Where should this uncertainty be logged?

A.The Issue Register
B.The Risk Register
C.The Benefits Management Plan
D.The Daily Log
AnswerB

The Risk Register records all uncertainties, whether threats or opportunities, because PRINCE2 defines risk as any uncertain event affecting objectives. A positive-impact uncertainty is therefore an opportunity and belongs there, satisfying the stem's requirement to log it in the single risk management product.

Why this answer

In PRINCE2, the Risk Register is the repository for all uncertainties — both threats (negative impacts) and opportunities (positive impacts). An uncertainty with a positive impact on schedule is by definition an opportunity, which is a type of risk, so it belongs in the Risk Register. The Issue Register is reserved for issues (problems that have already occurred or are certain to occur), not potential future uncertainties.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that positive uncertainties are 'benefits' or 'issues' rather than risks, causing candidates to select the Benefits Management Plan or Issue Register instead of the Risk Register.

How to eliminate wrong answers

Option A is wrong because the Issue Register records issues — events that have already happened or are certain to happen — not potential future uncertainties, even positive ones. Option C is wrong because the Benefits Management Plan documents expected benefits and how they will be measured and realized, not individual uncertainties or opportunities. Option D is wrong because the Daily Log is used for informal progress notes, actions, and minor observations by the project manager, not formal risk/opportunity records.

44
MCQmedium

A multi-national corporation is rolling out PRINCE2 across various departments. They adjust the standard management reports and terminology to align with existing corporate governance frameworks without losing core controls. Which PRINCE2 principle is being applied?

A.Defined roles and responsibilities
B.Manage by exception
C.Tailor to suit the project
D.Learn from experience
AnswerC

Tailor to suit the project means adapting PRINCE2's processes, themes, terminology and reports to the organisation's scale, governance and environment while retaining the principles. Aligning reports with corporate governance frameworks without losing core controls is exactly this tailoring.

Why this answer

The principle being applied is 'Tailor to suit the project' because the corporation is adjusting PRINCE2 reports and terminology to align with existing corporate governance frameworks while maintaining core controls. Tailoring ensures that PRINCE2 is adapted to the project's environment, size, complexity, and organizational standards without compromising its principles.

Exam trap

PRINCE2-Practitioner often tests the misconception that tailoring means ignoring PRINCE2 principles or that any adaptation is acceptable; the trap is confusing tailoring with abandoning core controls.

How to eliminate wrong answers

Option A is wrong because 'Defined roles and responsibilities' focuses on establishing clear roles, not on adapting reports and terminology. Option B is wrong because 'Manage by exception' is about setting tolerances and delegating authority, not about customizing documentation. Option D is wrong because 'Learn from experience' involves capturing and using lessons, not modifying governance frameworks.

45
MCQeasy

Which PRINCE2 process is specifically responsible for creating the Project Management Plan and establishing the baseline against which the project will be managed?

A.Initiating a Project
B.Managing a Stage Boundary
C.Controlling a Stage
D.Starting up a Project
AnswerA

Initiating a Project assembles the Project Initiation Documentation, including the Project Management Plan, and defines the baselines for scope, cost, time and quality against which the project is managed. This directly satisfies the stem's requirement for the process creating the plan and baseline.

Why this answer

The Initiating a Project process is where the Project Manager produces the Project Initiation Documentation (PID), including the Project Management Plan, the detailed Business Case, and the baseline for scope, cost, time, quality, risk, and benefits. It is the process that establishes the management approach and baselines against which the project will be controlled. This process runs after Starting up a Project and before the first stage begins.

Exam trap

PRINCE2-Practitioner often tests the confusion between Starting up a Project (pre-project, produces the Project Brief) and Initiating a Project (produces the PID and Project Management Plan), tricking candidates into selecting the earlier process.

How to eliminate wrong answers

Option B is wrong because Managing a Stage Boundary produces End Stage Reports and Next Stage Plans, and updates the Project Plan, but it does not create the original Project Management Plan or its baselines. Option C is wrong because Controlling a Stage is about day-to-day delivery of a stage — authorizing work packages, monitoring progress, and handling issues — not about establishing project-level baselines. Option D is wrong because Starting up a Project produces the Project Brief, the outline Business Case, and the daily log, but explicitly does not create the Project Management Plan; that is deferred to Initiating a Project.

46
MCQhard

A project is executing the Controlling a Stage process. The Project Manager identifies that multiple minor issues are occurring simultaneously, causing friction among team members. The Project Manager wants to capture these issues formally for ongoing management. Where should they be recorded?

A.Issue Register
B.Daily Log
C.Risk Register
D.Highlight Report
AnswerA

Minor issues arising during Controlling a Stage belong in the Issue Register, which captures all issues formally for ongoing management and assessment. The Daily Log only suits informal notes the Project Manager tracks personally, so it cannot satisfy the stem's requirement for formal, ongoing management of multiple simultaneous issues.

Why this answer

In PRINCE2, the Issue Register is used to capture and manage all issues, including minor ones that occur during a stage. The Project Manager records issues in the Issue Register to track their resolution and ensure they are addressed appropriately.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between the Issue Register, Risk Register, and Daily Log, and candidates may incorrectly choose the Daily Log for formal issue capture.

How to eliminate wrong answers

Option B is wrong because the Daily Log is used for informal notes and actions, not formal issue management. Option C is wrong because the Risk Register is for risks, not issues. Option D is wrong because the Highlight Report is for reporting progress to the Project Board, not for recording issues.

47
MCQeasy

What is the primary purpose of the Starting up a Project process?

A.To construct all specialist products and deliver them to the operational environment.
B.To ensure that the prerequisites for initiating a project are in place.
C.To close the project and archive all project records.
D.To manage the day-to-day execution of work packages.
AnswerB

Starting up a Project exists to answer whether the project is worthwhile and viable, ensuring prerequisites such as the Project Brief, project mandate and appointment of the Project Board are in place before Initiation begins.

Why this answer

The Starting up a Project (SU) process is the pre-project process whose purpose is to ensure the prerequisites for initiating a project are in place — specifically, that the project mandate exists, the project team is appointed, the Project Brief is produced, and the initiation stage is planned. It answers the question 'do we have a viable and worthwhile project?' before committing resources to the Initiation Stage. It is deliberately short and ends with a decision (via the Project Board) on whether to proceed to Initiating a Project.

Exam trap

PRINCE2-Practitioner often tests the confusion between Starting up a Project (pre-project prerequisites) and Initiating a Project (building the PID), causing candidates to pick answers that describe PID activities such as assembling the Business Case in full or planning the project in detail.

How to eliminate wrong answers

Option A is wrong because constructing specialist products and delivering them to operations is the purpose of Managing Product Delivery (MP) and the final delivery stages, not Starting up a Project. Option C is wrong because closing the project and archiving records is the purpose of the Closing a Project (CP) process, which occurs at the end of the project. Option D is wrong because managing day-to-day execution of Work Packages is the responsibility of the Team Manager under Managing Product Delivery (MP), and at the Project Manager level it is Controlling a Stage (CS).

48
MCQeasy

In the PRINCE2 Quality practice, what is the term used for the specific characteristics that a product must possess to meet stakeholder expectations and standards?

A.Risk thresholds
B.Quality criteria
C.Benefit measures
D.Project tolerances
AnswerB

Quality criteria are the measurable attributes defined in the Product Description that a product must exhibit to satisfy stakeholders. They form the benchmark against which quality control inspection and testing are performed during the Quality practice.

Why this answer

In PRINCE2, quality criteria are the specific, measurable characteristics that a product must have to satisfy stakeholder expectations and conform to relevant standards. They are defined during the 'Plans' and 'Quality' processes and are documented in the Product Description for each product. Quality criteria form the basis for quality control activities, such as testing and inspection, ensuring the product is fit for purpose.

Exam trap

PRINCE2-Practitioner often tests the confusion between quality criteria and other PRINCE2 terms like tolerances or benefits, so candidates must remember that quality criteria are product-specific attributes, not project-level constraints or business outcomes.

How to eliminate wrong answers

Option A is wrong because risk thresholds are the levels of risk exposure that trigger escalation or specific risk responses, not product characteristics. Option C is wrong because benefit measures are used to quantify the expected business benefits in the Business Case, not to define product quality. Option D is wrong because project tolerances are the permissible deviations from planned project-level targets (e.g., time, cost, scope) that define the Project Board's tolerance, not the attributes of a product.

49
MCQeasy

During stage execution, a Team Manager realizes that a work package cannot be completed within the agreed time tolerance due to unexpected technical hurdles. What should the Team Manager do according to the Issues practice?

A.Directly submit an Exception Report to the Project Board.
B.Inform the Project Manager immediately by raising an issue.
C.Quietly absorb the delay by reducing product quality.
D.Cancel the work package and hire a new team.
AnswerB

A work package forecast to breach its agreed time tolerance is a deviation the Team Manager cannot resolve alone, so it must be escalated as an issue to the Project Manager. This satisfies the stem's constraint, since only the Project Manager can decide on corrective action within stage tolerance.

Why this answer

Under PRINCE2's Issues practice, a Team Manager who cannot complete a work package within agreed tolerances must inform the Project Manager immediately by raising an issue. The Project Manager then assesses whether the deviation can be handled within stage tolerances or requires escalation. The Team Manager does not escalate directly to the Project Board.

Exam trap

PRINCE2-PRACTITIONER often tests escalation paths; the trap is thinking the Team Manager can go directly to the Project Board instead of informing the Project Manager first.

How to eliminate wrong answers

Option A is wrong because the Team Manager does not submit Exception Reports directly to the Project Board; that is the Project Manager's responsibility after assessment. Option C is wrong because quietly absorbing the delay by reducing quality violates quality and change control principles. Option D is wrong because cancelling the work package and hiring a new team is an extreme, unauthorized action that bypasses proper issue management.

50
MCQmedium

A project is nearing the end of a management stage. The Project Manager has drafted an End Stage Report. Who is responsible for reviewing and approving the End Stage Report?

A.The Team Managers
B.Corporate Quality Assurance
C.External auditors
D.The Project Board
AnswerD

The Project Board reviews and approves the End Stage Report at the end-of-stage assessment, deciding whether the stage has delivered against its tolerances and authorising the next stage. This authority cannot be delegated to the Project Manager, who authored the report.

Why this answer

The Project Board is responsible for reviewing and approving the End Stage Report, as it provides the board with an overview of the stage's performance and a request to approve the next stage. This approval is part of the 'Managing a Stage Boundary' process, where the board decides whether to continue, change, or stop the project. The Project Manager drafts the report, but the board owns the decision.

Exam trap

PRINCE2-PRACTITIONER often tests the roles and responsibilities in the 'Managing a Stage Boundary' process, and candidates may incorrectly assume the Project Manager approves the report rather than the Project Board.

How to eliminate wrong answers

Option A is wrong because Team Managers are responsible for managing teams and providing information to the Project Manager, not for approving stage reports. Option B is wrong because Corporate Quality Assurance may provide assurance but does not have decision-making authority in PRINCE2 governance. Option C is wrong because external auditors are not part of the PRINCE2 project organization and do not approve stage reports.

51
MCQmedium

During a project workshop, two senior team members engage in a heated argument regarding technical architecture, halting progress. As a PRINCE2 7 practitioner, how should the Project Manager handle this conflict?

A.Make an arbitrary decision yourself without listening to either party's technical arguments.
B.Ignore the argument and allow them to fight it out until one person dominates.
C.Immediately eject both individuals from the workshop to maintain hierarchical control.
D.Facilitate a structured discussion to refocus the debate on project tolerances, quality criteria, and collaborative solutions.
AnswerD

Facilitating a structured discussion directly addresses the workshop's stalled progress by channelling the disagreement toward project tolerances and quality criteria, satisfying PRINCE2 7's requirement that the Project Manager manage conflict constructively rather than arbitrate technical detail. Refocusing on agreed tolerances and collaborative solutions restores progress while preserving team members' ownership of the architecture decision.

Why this answer

PRINCE2 7 emphasizes collaborative people management, and the Project Manager should facilitate a structured discussion to refocus the debate on project tolerances, quality criteria, and collaborative solutions. Option D is correct because it addresses the conflict constructively, aligning with the principle of 'tailor to suit the project environment' and the 'people' aspect of PRINCE2 7. This approach maintains team cohesion and keeps the project moving forward.

Exam trap

PRINCE2-Practitioner often tests the misconception that a Project Manager should be authoritarian or avoid conflict, tempting candidates to choose options that are either too passive or too punitive rather than collaborative.

How to eliminate wrong answers

Option A is wrong because making an arbitrary decision without listening to technical arguments undermines collaboration and may lead to poor technical outcomes; it also violates the principle of 'learn from experience' and respect for team expertise. Option B is wrong because ignoring the argument and allowing a dominance battle can damage team morale and delay progress, contrary to effective people management. Option C is wrong because immediately ejecting both individuals is an extreme, punitive action that fails to address the root cause and may lose valuable team members, conflicting with PRINCE2 7's emphasis on supportive leadership.

52
MCQmedium

A project is developing a new software system. The Project Manager discovers that one of the operational benefits listed in the Business Case will actually occur 12 months *after* the project has officially closed. How should this be handled under PRINCE2 7?

A.Extend the project lifecycle by 12 months to allow the Project Manager to track the benefit.
B.Delete the benefit from the Benefits Management Approach because project closure terminates all benefit tracking.
C.Transfer accountability for the Business Case to the Senior Supplier once the software is deployed.
D.Ensure post-project benefit reviews are scheduled and handed over to operational management in the Benefits Management Approach.
AnswerD

Benefits Management Approach defines post-project review timing and assigns responsibility to operational management, so benefits arising after closure are still measured. This satisfies the stem's constraint that the benefit occurs 12 months after the project officially closes.

Why this answer

Under PRINCE2 7, benefits that materialise after project closure are explicitly managed through the Benefits Management Approach, which defines post-project benefit reviews and assigns responsibility to those who will own the benefit in the operational environment (typically the Senior User or operational management). The project does not need to remain open to track benefits; instead, the Benefits Management Approach is handed over as part of project closure so that reviews can occur after the project ends. Option D correctly reflects this by scheduling post-project reviews and transferring responsibility to operational management, ensuring benefits realisation is not lost when the project closes.

Exam trap

PRINCE2-Practitioner often tests the misconception that project closure terminates all benefit tracking, leading candidates to either extend the project unnecessarily or delete the benefit, when in fact the Benefits Management Approach is designed to manage post-project benefits.

How to eliminate wrong answers

Option A is wrong because extending the project lifecycle to track a post-closure benefit contradicts PRINCE2's principle of managing by stages and the concept of a project as a temporary organisation; projects are closed when their products are delivered, and benefit tracking continues outside the project. Option B is wrong because deleting the benefit is never acceptable; the Benefits Management Approach exists precisely to plan for benefits that occur after closure, and PRINCE2 requires that expected benefits be documented and reviewed even post-project. Option C is wrong because accountability for the Business Case remains with the Project Board (specifically the Executive) during the project, and after closure it transfers to the business owners or operational management, not the Senior Supplier, who is responsible for supplier resources and technical delivery, not benefit realisation.

53
MCQeasy

In PRINCE2, what is the primary purpose of the Progress practice?

A.To define the quality standards and review methods.
B.To identify and evaluate project risks and opportunities.
C.To monitor and control achievements against plans and ensure continued viability.
D.To establish the initial business case justification.
AnswerC

Progress monitors and controls achievements against plans and confirms continued viability, matching the stem's stated purpose. It provides the actual-versus-plan information, tolerances and forecasts that let the Project Board judge whether the Business Case remains viable and the project should continue.

Why this answer

The Progress practice in PRINCE2 is about monitoring and controlling achievements against plans and ensuring the project remains viable. It provides the mechanism to compare actual progress with planned progress and to take corrective action. Option C correctly describes this purpose.

Exam trap

PRINCE2-PRACTITIONER often tests the purpose of each practice, and candidates may confuse Progress with Quality or Risk, especially if they focus on the word 'control' without considering the full scope of the Progress practice.

How to eliminate wrong answers

Option A is wrong because defining quality standards and review methods is the purpose of the Quality practice, not Progress. Option B is wrong because identifying and evaluating risks and opportunities is the purpose of the Risk practice. Option D is wrong because establishing the initial business case justification is part of the Business Case theme, not the Progress practice.

54
MCQmedium

A project is running behind schedule due to unexpected regulatory sign-offs. The Project Manager identifies that the delay will consume the time tolerance agreed with the Project Board, but it will not exceed it. What should the Project Manager do, based on PRINCE2 principles?

A.Continue executing the stage plan since the forecast remains within agreed time tolerances.
B.Escalate immediately with an Exception Report because any delay is unacceptable.
C.Suspend the project immediately to re-verify the business justification.
D.Rewrite the Project Brief to adjust the quality expectations of the outputs.
AnswerA

Tolerance is delegated authority, so a forecast delay that stays within the agreed time tolerance requires no exception report or Board escalation. The Project Manager continues executing the stage plan, taking corrective action internally, satisfying the principle that management by exception operates within tolerances.

Why this answer

In PRINCE2, tolerances define the permissible deviation from planned targets before escalation is required. Since the forecast delay will consume but not exceed the agreed time tolerance, the Project Manager retains the authority to manage the stage within those limits. The correct action is to continue executing the stage plan, monitoring the situation closely, and only escalate if the tolerance is forecast to be exceeded.

This aligns with the 'Manage by Exception' principle, which empowers the Project Manager to take corrective action within delegated tolerances without unnecessary escalation.

Exam trap

PRINCE2-Practitioner often tests the misconception that any deviation from plan requires immediate escalation, confusing tolerance with zero tolerance, and overlooking the 'Manage by Exception' principle that empowers the Project Manager to act within agreed tolerances.

How to eliminate wrong answers

Option B is wrong because escalation via an Exception Report is only required when a tolerance is forecast to be exceeded, not merely when a delay occurs; PRINCE2 does not treat any delay as automatically unacceptable. Option C is wrong because suspending the project is a drastic action reserved for situations where the business justification is no longer valid or when instructed by the Project Board; a delay within tolerance does not warrant suspension. Option D is wrong because the Project Brief is a pre-project document that should not be rewritten during execution, and adjusting quality expectations is not a valid response to a time delay within tolerance; quality expectations are defined in the Project Product Description and should only be changed through formal change control.

55
MCQmedium

During the Starting up a Project process, what is the primary purpose of appointing the Project Manager?

A.To enable the Project Manager to plan the initiation stage and prepare the Project Brief.
B.To delegate full financial accountability for the entire project budget to the Project Manager.
C.To allow the Project Manager to authorize project closure independently.
D.To replace the Executive on the Project Board.
AnswerA

Appointing the Project Manager early enables that person to plan the initiation stage and prepare the Project Brief, since both activities require the role's authority. This satisfies SU's purpose of establishing a viable project foundation.

Why this answer

In PRINCE2, the Starting up a Project (SU) process is triggered by the mandate and its purpose is to ensure the prerequisites for initiating the project are in place. One of its activities is 'Appoint the Project Manager and the Project Management Team', which must happen early so the Project Manager can plan the Initiation Stage and draft the Project Brief (an output of SU). The Project Manager needs this appointment to perform the SU activities and prepare for the Initiating a Project process.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the Project Manager's operational responsibilities and the Project Board's accountability, tempting candidates to over-attribute financial or closure authority to the Project Manager.

How to eliminate wrong answers

Option B is wrong because financial accountability for the project budget ultimately rests with the Executive (supported by the Project Board), not delegated in full to the Project Manager; the Project Manager manages the stage-level budget within tolerances. Option C is wrong because project closure must be authorized by the Project Board via the Directing a Project process (DP5), not independently by the Project Manager. Option D is wrong because the Executive is a Project Board role that cannot be replaced by the Project Manager; PRINCE2 requires the Executive to remain accountable for the business case.

56
MCQeasy

During stakeholder analysis, a Project Manager identifies a stakeholder who has high power and low interest in the project. According to standard stakeholder management frameworks incorporated in PRINCE2 7, how should this stakeholder be managed?

A.Keep them fully informed with exhaustive daily operational reports.
B.Keep them satisfied with targeted, high-level summaries and proactive management of key issues.
C.Delegate their management entirely to junior administrative staff.
D.Ignore them completely since they have low interest.
AnswerB

High power demands their concerns be addressed, while low interest means they need only concise, high-level summaries rather than detailed engagement. Proactive management of key issues prevents surprises escalating into blockers, satisfying the "keep satisfied" quadrant of the power/interest grid that PRINCE2 7 incorporates for stakeholder analysis.

Why this answer

In the standard power/interest grid, a stakeholder with high power and low interest falls into the 'Keep Satisfied' quadrant. These stakeholders can block or derail the project if displeased, but they do not want day-to-day detail — so the correct approach is targeted, high-level summaries and proactive management of issues that could affect them. PRINCE2 7's Organizing practice and stakeholder engagement guidance support this tailored communication approach.

Exam trap

The trap is assuming low interest means low importance — candidates who ignore or over-communicate with high-power/low-interest stakeholders miss the 'Keep Satisfied' nuance that PRINCE2 7 tests.

How to eliminate wrong answers

Option A is wrong because exhaustive daily operational reports would overwhelm a low-interest stakeholder and likely increase disengagement — communication must be tailored to interest level, not maximized. Option C is wrong because delegating a high-power stakeholder to junior administrative staff is inappropriate; high-power stakeholders require senior-level relationship management and escalation paths. Option D is wrong because ignoring a high-power stakeholder is dangerous — even with low interest, they can exert influence (e.g., funding cuts, political blockers) if they become dissatisfied, so they must be actively kept satisfied.

57
MCQmedium

In the Controlling a Stage (CS) process, how does the Project Manager handle highlight reports?

A.Submit them to the Corporate/Programme level to request additional project funding.
B.Issue them daily to all Team Managers to track individual task completion.
C.Use them as the final evaluation document when closing the project.
D.Create and submit them to the Project Board at agreed intervals to report stage progress.
AnswerD

Highlight reports are the Project Manager's primary control instrument during a stage, produced at the frequency defined in the Communication Management Strategy and sent to the Project Board. This satisfies the CS process requirement to keep the Board informed of progress, without transferring day-to-day management authority.

Why this answer

In Controlling a Stage, the Project Manager creates Highlight Reports and submits them to the Project Board at the frequency agreed in the Communication Management Strategy (typically per reporting period, e.g., monthly or at stage checkpoints). The Highlight Report summarises stage progress, issues, risks, and forecast against the Stage Plan, enabling the Board to manage by exception.

Exam trap

PRINCE2-Practitioner often tests report direction and audience — candidates confuse Highlight Reports (PM to Board) with Checkpoint Reports (Team Manager to PM) or End Project Reports (CP), and pick options that send them to the wrong recipient or at the wrong frequency.

How to eliminate wrong answers

Option A is wrong because Highlight Reports go to the Project Board, not to Corporate/Programme for funding requests — funding escalations would be handled via an Exception Report or a Project Board decision, not a routine Highlight Report. Option B is wrong because daily reports to Team Managers is backwards: Team Managers send Checkpoint Reports to the PM, and Highlight Reports are periodic, not daily. Option C is wrong because the End Project Report (produced in Closing a Project) is the final evaluation document, not the Highlight Report.

58
MCQmedium

A PRINCE2 project is conducting a formal quality review for a safety-critical engineering component. During the review, a minor defect is found that can be easily corrected within the planned stage time and cost. What is the correct procedure for handling this defect?

A.Record the defect as a required action for the author to correct before re-submitting for review.
B.Escalate an Exception Report to the Project Board.
C.Submit a Request for Change to corporate management.
D.Reject the entire project immediately.
AnswerA

Recording the defect as a required action lets the author correct it and resubmit, which PRINCE2 quality review procedure specifies for minor defects that can be fixed within the stage's time and cost tolerances. The reviewer's role is to identify and log, not to amend the product directly.

Why this answer

In PRINCE2 quality reviews, a minor defect that can be corrected within stage tolerances is recorded as a required action for the author to fix before re-submission. This is part of the quality review technique, where the reviewer logs the defect in the Quality Register and the author corrects it. It does not require escalation or a Request for Change because it is within tolerance.

Exam trap

The trap is escalating a minor defect to the Project Board or raising a Request for Change, but PRINCE2 expects minor defects to be handled at the quality review level within tolerances.

How to eliminate wrong answers

Option B is wrong because an Exception Report is only needed when a stage or project is predicted to exceed its tolerances; a minor defect within time and cost does not trigger this. Option C is wrong because a Request for Change is for changes to baselined products, not for correcting defects found during quality review. Option D is wrong because rejecting the entire project is an extreme overreaction; the defect is minor and correctable.

59
MCQeasy

In the PRINCE2 Issues practice, what is the primary purpose of a Request for Change?

A.To report a defect in a product that failed its quality review.
B.To request additional risk register entries.
C.To request extra vacation time for the project manager.
D.To formally propose a modification to a project baseline.
AnswerD

A Request for Change formally proposes a modification to a project baseline, triggering assessment of impact on scope, cost, time and risk before the Project Board authorises any change, distinguishing it from an Off-Specification, which reports an existing deviation.

Why this answer

A Request for Change (RFC) in PRINCE2 is a formal proposal to modify a project baseline, such as scope, schedule, cost, or quality parameters. It is one of the three types of issues and is raised when someone wants to change an agreed baseline. The RFC is logged in the Issue Register and assessed for impact before a decision is made by the appropriate authority.

Exam trap

PRINCE2-Practitioner often tests whether candidates can distinguish between the three issue types, so candidates who select off-specification for a baseline modification question confuse a defect report with a change request.

How to eliminate wrong answers

Option A is wrong because reporting a defect that failed quality review is an off-specification issue, not a Request for Change; off-specifications address products that do not meet requirements, while RFCs propose modifications to baselines. Option B is wrong because requesting additional risk register entries is not a formal PRINCE2 issue type; risk identification is part of the Risk practice, not the Issues practice. Option C is wrong because requesting vacation time is an HR administrative matter, not a project issue within PRINCE2's Issue practice.

60
MCQhard

A PRINCE2 project is operating with a Team Manager who discovers that a work package cannot be completed within the agreed time tolerance due to unexpected technical complexity. According to PRINCE2, what is the Team Manager's immediate reporting duty?

A.Escalate directly to the Project Board by raising an Exception Report.
B.Notify the Project Manager immediately so the impact on stage tolerances can be assessed.
C.Quietly extend the work package deadline without telling anyone.
D.Submit a Request for Change to Corporate, Programme Management or Portfolio Direction.
AnswerB

The Team Manager must escalate to the Project Manager as soon as a work package is forecast to breach its agreed tolerances. PRINCE2 assigns tolerance monitoring at stage level to the Project Manager, so only they can assess whether the time overrun consumes remaining stage tolerance or triggers an exception report.

Why this answer

According to PRINCE2, the Team Manager is responsible for managing the work package and must inform the Project Manager as soon as it is forecast that the work package will exceed its tolerances. The Project Manager then assesses the impact on stage tolerances and decides whether to escalate. Direct escalation to the Project Board or raising an Exception Report is not the Team Manager's duty.

Exam trap

PRINCE2-Practitioner often tests the boundary between Team Manager and Project Manager responsibilities, so candidates who confuse the escalation levels or reporting products choose the wrong answer.

How to eliminate wrong answers

Option A is wrong because the Team Manager does not raise Exception Reports; that is the Project Manager's responsibility when stage tolerances are threatened. Option C is wrong because quietly extending the deadline violates the principle of management by exception and the work package agreement. Option D is wrong because a Request for Change is for changes to baselined products, not for reporting a forecast tolerance breach; also, it should go to the Project Manager, not Corporate.

61
Multi-Selectmedium

Which TWO of the following activities are performed during the Starting up a Project (SU) process?

Select 2 answers
A.Authorizing the Project Management Plan
B.Preparing the Project Brief
C.Executing all Work Packages for specialist delivery
D.Appointing the Executive and Project Manager
E.Conducting the final post-project benefit review
AnswersB, D

Preparing the Project Brief is a core SU activity, producing the outline of the project's scope, business case and approach that the Project Board reviews before authorising initiation. This satisfies the stem's requirement for activities performed during Starting up a Project.

Why this answer

In PRINCE2, the Starting up a Project (SU) process is the pre-project process whose purpose is to ensure the prerequisites for initiating a project are in place, and it explicitly includes preparing the Project Brief (option B), which captures the outline business case, project definition, and approach for the project board's decision. It also includes appointing the Executive and the Project Manager (option D), since the project board's Executive role must be filled and the Project Manager appointed before the project can be initiated. Option A is wrong because authorizing the Project Management Plan occurs in the Directing a Project (DP) process, specifically the DP4 'Authorise the Project' activity, after the Initiating a Project process has produced the plan.

Option C is wrong because executing Work Packages for specialist delivery happens in the Controlling a Stage (CS) and Managing Product Delivery (MP) processes during the delivery stages, not in SU. Option E is wrong because the final post-project benefit review is part of the Closing a Project (CP) process and/or benefits management after the project, not Starting up a Project.

Exam trap

PRINCE2-Practitioner often tests whether candidates can distinguish SU activities (Project Brief, appointing Executive/PM) from IP activities (Project Management Plan, PID, baselining), catching those who assume all early planning happens in one process.

62
MCQmedium

A PRINCE2 project is executing a stage when an unexpected risk event occurs. The risk was previously identified and evaluated as having a medium impact, and a contingency reserve was set aside. The risk materializes, and the contingency reserve is used. How should this be recorded in the Risk Register?

A.Convert the risk into an End Stage Report.
B.Raise a Request for Change to corporate management.
C.Delete the risk entry from the Risk Register immediately.
D.Update the Risk Register to record that the risk has materialized and the planned response was executed.
AnswerD

The Risk Register entry is updated to show the risk has materialised and the planned response, funded from the contingency reserve, was executed. This satisfies the stem's requirement to record the materialised risk and the use of the reserve.

Why this answer

When a previously identified risk materializes and the planned response is executed, the Risk Register must be updated to reflect that the risk has occurred and the response was implemented. This ensures that the risk status is current and that lessons can be learned. The Risk Register is a living document that tracks the status of all risks throughout the project.

Exam trap

The trap is thinking that a materialized risk should be deleted or converted to another document, but PRINCE2 requires updating the Risk Register to maintain an accurate history.

How to eliminate wrong answers

Option A is wrong because an End Stage Report is a progress report, not a record of risk materialization. Option B is wrong because a Request for Change is used for changes to baselined products, not for recording risk events. Option C is wrong because deleting the risk entry would lose valuable information; instead, the risk should be closed or updated to show it has materialized.

63
MCQeasy

A project manager wants to ensure that all changes to project baselines are formally controlled. Under which practice is change control managed?

A.The Organizing practice
B.The Quality practice
C.The Issues practice
D.The Progress practice
AnswerC

Change control sits within the Issues practice, which covers raising, assessing and deciding on requests for change and off-specifications, then updating baselines once approved. This satisfies the requirement that all baseline changes are formally controlled through a single defined route.

Why this answer

Change control is managed under the Issues practice in PRINCE2. The Issues practice encompasses the identification, assessment, and control of changes to baselines, ensuring that all changes are formally evaluated, approved, and implemented.

Exam trap

PRINCE2-Practitioner often tests the misconception that change control is part of the Quality or Progress practice; the trap is forgetting that changes are a type of issue and thus managed under the Issues practice.

How to eliminate wrong answers

Option A is wrong because the Organizing practice deals with roles and responsibilities, not change control. Option B is wrong because the Quality practice focuses on quality planning and control, not baseline changes. Option D is wrong because the Progress practice monitors and reports progress, but does not manage changes to baselines.

64
MCQhard

A PRINCE2 project is implementing an AI system. The risk management team identifies an ethical risk regarding biased algorithmic outputs. The project team decides to implement continuous algorithmic auditing and diverse training datasets. Which risk response is being applied?

A.Accept
B.Mitigate
C.Avoid
D.Transfer
AnswerB

Continuous algorithmic auditing and diverse training datasets reduce the probability and impact of biased outputs, which is the definition of a mitigate response. It targets the specific ethical risk identified, lowering its likelihood rather than transferring, avoiding or accepting it.

Why this answer

Mitigate is the correct response because implementing continuous algorithmic auditing and diverse training datasets are actions taken to reduce the probability and/or impact of the ethical risk of biased outputs. These measures proactively lower the risk while allowing the project to continue.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between Mitigate and Avoid for ethical risks; candidates may think that auditing and diverse data avoid the risk, but Avoid would mean not using AI at all, whereas Mitigate reduces the risk while proceeding.

How to eliminate wrong answers

Option A is wrong because Accept means taking no action and simply tolerating the risk, which is not the case here. Option C is wrong because Avoid would involve eliminating the risk by not implementing the AI system or changing its scope to remove the ethical risk, but the project is proceeding with mitigation measures. Option D is wrong because Transfer involves shifting the risk to a third party, such as through insurance or contractual agreements, which is not happening.

65
MCQmedium

During a PRINCE2 project stage, the Project Manager forecasts that the stage cost will exceed the upper cost tolerance by 5%. According to the Progress practice, what is the mandatory action the Project Manager must take?

A.Quietly borrow funds from the next stage's budget without informing the Project Board.
B.Absorb the cost overrun by reducing the quality checks on deliverables.
C.Raise an Exception Report and submit it to the Project Board.
D.Close the project immediately.
AnswerC

Exceeding the stage cost tolerance breaches the delegated authority defined in the stage plan, so the Project Manager must escalate by raising an Exception Report to the Project Board. The Board then decides whether to authorise a revised stage or exception plan.

Why this answer

According to the PRINCE2 Progress practice, if the Project Manager forecasts that stage costs will exceed the upper cost tolerance, this constitutes an exception. The Project Manager must raise an Exception Report and submit it to the Project Board, as the Project Board is responsible for authorizing exceptions and deciding on corrective actions. This ensures that the project remains within the agreed tolerances and that the Board can make informed decisions.

Exam trap

PRINCE2-PRACTITIONER often tests the tolerance concept, and candidates may incorrectly think the Project Manager can handle the overrun within the stage without escalation, but exceeding a tolerance always requires an Exception Report.

How to eliminate wrong answers

Option A is wrong because borrowing funds from the next stage's budget without informing the Project Board violates the tolerance boundaries and is not allowed. Option B is wrong because reducing quality checks to absorb cost overruns compromises the project's quality criteria and is unethical and against PRINCE2 principles. Option D is wrong because closing the project immediately is an extreme action that is not mandatory; the Project Board may decide to continue with revised tolerances or take other actions.

66
Multi-Selectmedium

Which TWO of the following reports are used in the Progress practice to communicate status between different levels of management? (Choose two)

Select 2 answers
A.Business Case Review (Team Manager to Senior User)
B.Risk Log Summary (Supplier to External Auditor)
C.Checkpoint Report (Team Manager to Project Manager)
D.Project Product Description (Executive to Corporate Management)
E.Highlight Report (Project Manager to Project Board)
AnswersC, E

The Checkpoint Report provides progress information from the Team Manager to the Project Manager at the work package level, typically at the frequency defined in the Work Package. It is one of the reports communicating status between management levels.

Why this answer

In PRINCE2's Progress practice, the Checkpoint Report (option C) is the regular progress report sent by the Team Manager to the Project Manager, providing status on the work package at the team-to-project-management level. The Highlight Report (option E) is the report the Project Manager sends to the Project Board at agreed intervals, summarizing project progress at the project-management-to-board level; together these two are the standard progress communication reports between management levels. Option A is not a PRINCE2 progress report — the Business Case is a document reviewed at decision points, not a Team Manager-to-Senior User status report.

Option B is incorrect because the Risk Log is a project document, not a report sent by a Supplier to an External Auditor. Option D is wrong because the Project Product Description is a product-definition document owned by the Project Manager, not an Executive-to-corporate-management progress report.

Exam trap

PRINCE2-Practitioner often tests the confusion between Progress reports (Checkpoint, Highlight, End Stage, End Project) and other management products (Business Case, Project Product Description, Risk Log) — candidates pick documents that sound like reports but are not part of the Progress practice's reporting chain.

67
MCQhard

A Project Manager is executing the Managing a Stage Boundary process. Halfway through compiling the End Stage Report, a major external market shift invalidates a key assumption in the Business Case. What should the Project Manager do?

A.Ignore the shift, as the End Stage Report only reflects past stage performance
B.Include the impact in the End Stage Report and recommend an Exception Plan or project closure
C.Stop the current stage immediately without consulting the Project Board
D.Immediately rewrite the Business Case and submit it to Corporate
AnswerB

A major external market shift invalidates a Business Case assumption, so the Project Manager must escalate through the End Stage Report rather than conceal it. Recommending an Exception Plan or project closure satisfies the Managing a Stage Boundary requirement to assess continued viability and refer the decision to the Project Board, which owns Business Case approval.

Why this answer

The End Stage Report must include an assessment of how the stage performed against its plan and any impact on the ongoing viability of the Business Case. A major external market shift that invalidates a key assumption is exactly the kind of information the Project Board needs to decide whether to continue, amend, or close the project. The PM should therefore document the impact and recommend either an Exception Plan or project closure for the board's decision.

Exam trap

PRINCE2-Practitioner often tests the misconception that the End Stage Report is purely backward-looking, tricking candidates into ignoring forward-looking Business Case impacts that must be escalated to the Project Board.

How to eliminate wrong answers

Option A is wrong because the End Stage Report is not merely retrospective — it must also inform the continued business justification and the Next Stage Plan, so ignoring a material market shift would breach the 'continued business justification' principle. Option C is wrong because stopping a stage is a Project Board decision under Directing a Project; the PM cannot unilaterally halt delivery outside the 'Manage by Exception' framework. Option D is wrong because the Business Case is owned by the Executive and approved by the Project Board, not Corporate directly, and rewriting it without going through the stage boundary governance process bypasses proper escalation.

68
MCQhard

A PRINCE2 project is implementing an enterprise-wide software system. The Project Manager wants to ensure that all business units affected by the change are adequately represented in decision-making and requirements-gathering. Which PRINCE2 practice and governance structure addresses this?

A.Progress practice through Highlight Reports
B.Organizing practice through the appointment of Senior Users representing affected business units
C.Quality practice through Quality Review meetings
D.Plans practice through Product Flow Diagrams
AnswerB

The Organizing practice defines roles, responsibilities and accountability, and Senior Users represent those who will use the product. Appointing Senior Users from each affected business unit satisfies the stem's representation constraint, embedding their requirements into decision-making through the project board structure.

Why this answer

The Organizing practice defines the project's governance structure, including the Project Board roles of Executive, Senior User(s), and Senior Supplier(s), plus assurance and support roles. Appointing Senior Users to represent affected business units ensures those units have a voice in decision-making and requirements-gathering, satisfying the 'representation of all interested parties' principle. This is a governance/role-design question, so Organizing is the correct practice.

Exam trap

PRINCE2-PRACTITIONER often tests which practice 'owns' stakeholder representation — candidates see 'requirements-gathering' and pick Quality or Plans, but representation in decision-making is an Organizing practice concern via the Senior User role.

How to eliminate wrong answers

Option A is wrong because the Progress practice covers monitoring, reporting, and control (including Highlight Reports) — it does not define governance roles or stakeholder representation. Option C is wrong because the Quality practice covers quality planning, control, and review techniques; Quality Review meetings verify products against criteria but do not ensure business-unit representation in decision-making. Option D is wrong because the Plans practice covers plan design and product-based planning techniques (including Product Flow Diagrams), which address what will be delivered and in what sequence, not who represents stakeholders.

69
MCQhard

A project team is implementing an agile delivery approach. The Project Manager is configuring the Plans practice to support iterative product delivery. How should the plans be structured to ensure PRINCE2 governance while allowing agile flexibility?

A.Replace all Stage Plans with a single immutable Project Plan.
B.Maintain management stages with Stage Plans, while using iterative delivery increments for product creation.
C.Force all deliverables into rigid 12-month delivery blocks.
D.Eliminate the Project Plan and rely solely on informal team whiteboards.
AnswerB

Stage Plans preserve the Project Board's stage-boundary control and tolerance-based governance, while iterative increments let teams deliver product components repeatedly. This satisfies the stem's dual constraint: PRINCE2 governance retained alongside agile flexibility in product creation.

Why this answer

To blend PRINCE2 governance with agile flexibility, the Plans practice should maintain management stages with Stage Plans for governance and control, while allowing iterative delivery increments (e.g., sprints) within those stages for product creation. This satisfies the PRINCE2 principle of 'Manage by Stages' while enabling agile delivery.

Exam trap

The trap is thinking that PRINCE2 and agile are incompatible — candidates may choose to eliminate stage boundaries or project plans, but PRINCE2 can be tailored to support agile while retaining governance.

How to eliminate wrong answers

Option A is wrong because replacing all Stage Plans with a single immutable Project Plan removes the stage boundaries that enable Project Board control and the 'Manage by Stages' principle. Option C is wrong because forcing rigid 12-month delivery blocks contradicts agile iterative delivery and reduces flexibility. Option D is wrong because eliminating the Project Plan and relying on informal whiteboards removes the documented baseline and governance required by PRINCE2.

70
MCQmedium

A project manager is developing a Business Case and needs to account for the operational costs that will occur after the project is completed and handed over to operations. What PRINCE2 term describes these ongoing costs?

A.Contingency reserves
B.Stage tolerance costs
C.Sunk costs
D.Whole-life costs
AnswerD

Whole-life costs encompass the total cost of ownership, combining project costs with ongoing operational and maintenance expenditure after handover. This directly satisfies the stem's requirement to account for post-project operational costs within the Business Case, since PRINCE2 defines whole-life costs as covering the entire lifespan of the project's output.

Why this answer

Whole-life costs in PRINCE2 refer to the total cost of ownership of a project's output over its entire life, including operational costs after handover. The Business Case must account for these ongoing costs to assess the project's continued viability. Option D correctly identifies the term for these post-project operational costs.

Exam trap

PRINCE2-PRACTITIONER often tests the difference between project costs and whole-life costs, and candidates may incorrectly choose 'contingency reserves' or 'sunk costs' if they do not recall that whole-life costs explicitly include post-project operational costs.

How to eliminate wrong answers

Option A is wrong because contingency reserves are funds set aside to cover the cost of risks that may occur, not the ongoing operational costs after project closure. Option B is wrong because stage tolerance costs are not a PRINCE2 term; stage tolerances are the permissible deviation from the stage plan, not a cost category. Option C is wrong because sunk costs are costs already incurred that cannot be recovered, not future operational costs.

71
MCQmedium

A PRINCE2 project is executing a stage. The Project Manager discovers that due to an unexpected supply chain bottleneck, the stage will finish 3 weeks late, which breaches the stage time tolerance. The Project Manager prepares an Exception Report and an Exception Plan. Who has the authority to approve the Exception Plan?

A.Project Manager
B.Team Manager
C.Corporate, Programme Management or Portfolio Direction
D.Project Board
AnswerD

The stage time tolerance has been breached, so the deviation sits outside the Project Manager's delegated authority. Only the Project Board, which owns the stage boundary and sets tolerances, can approve an Exception Plan that replaces the current Stage Plan.

Why this answer

The Project Board is responsible for approving Exception Plans. When a stage is predicted to exceed its tolerance, the Project Manager escalates the issue by creating an Exception Report and an Exception Plan. The Project Board, as the authority responsible for the overall project, reviews and approves the Exception Plan to bring the project back on track.

Exam trap

The trap is assuming that the Project Manager can approve the Exception Plan because they prepared it, or that the Team Manager can approve it because they are closer to the work. The exam tests the principle that the Project Board is the ultimate authority for approving Exception Plans.

How to eliminate wrong answers

Option A is wrong because the Project Manager does not have the authority to approve an Exception Plan; they can only prepare it. Option B is wrong because the Team Manager is responsible for managing a team and does not have the authority to approve Exception Plans. Option C is wrong because Corporate, Programme Management or Portfolio Direction is outside the project and would only be involved in extreme circumstances, such as project closure, not for approving an Exception Plan.

72
Multi-Selecthard

Which TWO of the following actions are mandatory when executing the Closing a Project (CP) process?

Select 2 answers
A.Drafting a new Project Brief for a follow-on project
B.Handing over products and ensuring operational support arrangements are in place
C.Rewriting the Project Product Description to reflect reduced scope
D.Authorizing the next stage plan for immediate execution
E.Evaluating the project by comparing actual performance against the baseline
AnswersB, E

Closing a Project requires confirmed product handover and agreed operational support arrangements, since the project cannot close while the outputs remain unsupported. This satisfies the mandatory acceptance and support transition activity within the CP process.

Why this answer

Option B is correct because Closing a Project requires the project manager to confirm that the products have been handed over to the customer/operations and that the necessary operational and support arrangements (e.g., service agreements, training, maintenance) are in place, as captured in the Handover and Support sections of the End Project Report. Option E is correct because evaluating the project against its baselines (the original Project Plan, Business Case, and benefits) is a mandatory activity in CP, producing the End Project Report and lessons learned to assess performance and confirm whether objectives were met. Option A is not mandatory in CP; a follow-on project would require its own Project Brief produced during Starting up a Project, not during closure.

Option C is wrong because the Project Product Description is baselined and not rewritten at closure to reflect reduced scope; scope changes are handled through change control during the project. Option D is wrong because authorizing the next stage plan is part of Managing a Stage Boundary (or the directing/authorizing activity), not Closing a Project, which instead deals with post-project recommendations.

Exam trap

PRINCE2-Practitioner often tests the confusion between activities in Closing a Project and those in Managing a Stage Boundary or Starting Up a Project, so candidates must remember that handover and evaluation are mandatory closing activities, while planning the next stage or creating a new Project Brief are not.

73
MCQmedium

During the Initiating a Project process, the Project Manager is refining the Business Case. What key financial metric is typically evaluated to ensure the project represents value for money?

A.Daily checkpoint report frequency
B.Return on Investment (ROI) or Net Present Value (NPV)
C.Team member daily hourly wages
D.Number of open risks in the Risk Register
AnswerB

ROI and NPV quantify expected financial return and discounted future value respectively, letting the Project Board judge whether the investment delivers value for money. These metrics underpin the Business Case's justification, satisfying the requirement to evaluate financial viability during Initiating a Project.

Why this answer

The Business Case in PRINCE2 must demonstrate that the project is desirable, viable, and achievable, and its financial justification is typically expressed through investment appraisal metrics such as Return on Investment (ROI) or Net Present Value (NPV). These quantify whether the benefits outweigh the costs and whether the project represents value for money. The Project Manager refines these figures during Initiating a Project to support the Project Board's authorization decision.

Exam trap

PRINCE2-Practitioner often tests the confusion between financial appraisal metrics (ROI, NPV, IRR) and operational or risk metrics (checkpoint frequency, risk counts), tricking candidates into selecting an operational measure as the value-for-money indicator.

How to eliminate wrong answers

Option A is wrong because checkpoint report frequency is a progress-control mechanism defined in the Communication Management Approach, not a financial value-for-money metric. Option C is wrong because individual team member hourly wages are cost inputs, not an investment appraisal metric — they do not by themselves indicate whether the project delivers value. Option D is wrong because the number of open risks is a risk-management indicator, not a financial appraisal metric, and a high risk count does not directly measure value for money.

74
MCQhard

A PRINCE2 project is adopting agile delivery. The Project Board is concerned that product quality might be compromised due to rapid, iterative coding cycles. Which PRINCE2 practice and tool combination should the Project Manager emphasize to reassure the Board?

A.Plans practice using Product Flow Diagrams to map out every single line of code.
B.Risk practice using risk avoidance to halt all agile sprints.
C.Quality practice using clear Product Descriptions with acceptance criteria and defined quality review methods for every increment.
D.Progress practice using daily Highlight Reports sent to the Executive.
AnswerC

Product Descriptions carry acceptance criteria and defined quality review methods, so each agile increment is measured against agreed tolerances rather than assumed correct. This directly addresses the Board's concern about quality compromise during rapid iterative coding cycles.

Why this answer

The Quality practice, supported by clear Product Descriptions with acceptance criteria and defined quality review methods, ensures that each agile increment meets the required quality standards. This reassures the Board that rapid iterations will not compromise quality because every product has explicit quality criteria and review techniques. Product Descriptions are the key tool for embedding quality into iterative delivery.

Exam trap

PRINCE2-Practitioner often tests the misconception that agile delivery bypasses PRINCE2 quality controls, so candidates pick Progress or Plans options instead of the Quality practice with Product Descriptions.

How to eliminate wrong answers

Option A is wrong because Product Flow Diagrams map dependencies between products, not every line of code, and do not address quality assurance in agile cycles. Option B is wrong because halting all agile sprints is not a PRINCE2 risk response and contradicts the purpose of adopting agile delivery. Option D is wrong because daily Highlight Reports are not a PRINCE2 product (Highlight Reports are typically end-stage or periodic) and do not directly assure product quality.

75
MCQmedium

A project manager is setting up the project organization. The project involves highly specialized nuclear engineering. The Senior Supplier wants to delegate technical oversight to an external subcontractor. According to PRINCE2, who remains ultimately accountable for the supplier's delivery performance on the Project Board?

A.Project Assurance
B.The Project Manager
C.The external subcontractor's lead engineer
D.The Senior Supplier
AnswerD

The Senior Supplier role carries accountability for supplier delivery performance on the Project Board, and delegating technical oversight to a subcontractor does not transfer that accountability. The board member remains answerable for the supplier's contribution regardless of internal delegation.

Why this answer

The Senior Supplier remains ultimately accountable for the supplier's delivery performance on the Project Board, even if technical oversight is delegated to an external subcontractor. In PRINCE2, the Senior Supplier role represents the supplier community and is accountable for the delivery of products to the required quality, time, and cost. Delegation of tasks does not transfer accountability.

Exam trap

PRINCE2-Practitioner often tests the misconception that accountability can be delegated along with technical oversight, when in fact the Senior Supplier remains ultimately accountable for supplier delivery performance.

How to eliminate wrong answers

Option A is wrong because Project Assurance provides independent oversight and does not own supplier delivery performance. Option B is wrong because the Project Manager manages the project on a day-to-day basis but is not accountable for supplier performance on the Project Board; that accountability lies with the Senior Supplier. Option C is wrong because the external subcontractor's lead engineer is not a Project Board role and does not hold ultimate accountability.

Page 1 of 4

Page 2

All pages

Practice PRINCE2-PRACTITIONER by domain

Target a specific domain to shore up weak areas.

See all domains with question counts →