PRINCE2 7 Practitioner (Managing Successful Projects with PRINCE2, 7th Edition) (PRINCE2-PRACTITIONER) PRINCE2-PRACTITIONER Questions 76–150 | Page 2/4

MCQeasy

In a large infrastructure project, the Project Board includes a representative from the user community, a representative of senior supplier interests, and an Executive representing business interests. Which PRINCE2 principle is being implemented?

A.Defined roles and responsibilities

B.Tailor to suit the project

C.Manage by exception

D.Continued business justification

AnswerA

The Project Board's three stakeholder perspectives — business, user and supplier — map directly onto PRINCE2's defined roles and responsibilities principle, which requires each stakeholder interest to be represented in the project management team structure.

Why this answer

The scenario describes the three primary Project Board interests — Business (Executive), User, and Supplier — each formally represented with defined accountabilities. This is the direct embodiment of the 'Defined roles and responsibilities' principle, which requires that the project management team structure be established with clear roles, and that the three primary stakeholder interests be represented on the Board. The presence of all three interests is the textbook signal for this principle.

Exam trap

The trap here is confusing 'Defined roles and responsibilities' (who is on the team and what they are accountable for) with 'Tailor to suit the project' (adapting the method) — candidates see 'large infrastructure project' and wrongly reach for tailoring.

How to eliminate wrong answers

Option B is wrong because 'Tailor to suit the project' concerns adapting PRINCE2's processes, themes, and products to the project's size, risk, and environment — it is not about who sits on the Board. Option C is wrong because 'Manage by exception' is about delegating authority with defined tolerances so the Board only intervenes when thresholds are breached, not about the composition of the Board. Option D is wrong because 'Continued business justification' is about ensuring there is a valid Business Case throughout the project, not about stakeholder representation on the governance body.

Full explanation →

MCQeasy

Which PRINCE2 process provides the interface between the management of the project and the day-to-day creation of the project's specialist products?

A.Starting up a Project

B.Directing a Project

C.Managing Product Delivery

D.Controlling a Stage

AnswerC

Managing Product Delivery sits between the Project Manager and the Team Manager, accepting work packages and confirming delivery of specialist products. It satisfies the stem's requirement for the interface between project management and day-to-day creation, since the Team Manager controls the actual production work within the agreed tolerances.

Why this answer

Managing Product Delivery (MP) is the process that sits between the Project Manager and the Team Manager, authorising work packages, ensuring specialist products are created, and accepting completed work packages. It is explicitly defined as the interface between project management and the day-to-day creation of specialist products.

Exam trap

The trap is confusing 'authorising work' (Controlling a Stage) with 'delivering work' (Managing Product Delivery) — candidates pick CS because it mentions work packages, but the interface with day-to-day product creation is MP.

How to eliminate wrong answers

Option A is wrong because Starting up a Project is a pre-project process that appoints the executive, PM, and team, and produces the Project Brief — it does not interface with product creation. Option B is wrong because Directing a Project is the Project Board's process for authorising the project, stages, and exceptions — it operates above the PM, not at the delivery interface. Option D is wrong because Controlling a Stage is the PM's process for monitoring and controlling the stage; it authorises work packages but the actual interface with Team Managers and product creation happens in MP.

Full explanation →

MCQeasy

In the PRINCE2 Plans practice, what is the primary purpose of a Project Plan?

A.To define individual product quality criteria.

B.To detail the daily tasks of team members for a single week.

C.To record identified project risks.

D.To provide a high-level schedule and cost baseline for the entire project lifecycle.

AnswerD

The Project Plan sits above stage plans and covers the whole project, establishing the high-level schedule and cost baseline against which the Project Board authorises and monitors progress, satisfying the stem's requirement for the Project Plan's primary purpose within the Plans practice.

Why this answer

The primary purpose of a Project Plan in PRINCE2 is to provide a high-level schedule and cost baseline for the entire project lifecycle. It defines the project's products, activities, resources, and tolerances, and serves as the baseline against which progress is monitored and controlled. The Project Plan is approved by the Project Board and is essential for managing by exception.

Exam trap

PRINCE2-Practitioner often tests the confusion between the Project Plan and other plans or documents like the Product Description or Risk Register, leading candidates to select an incorrect purpose.

How to eliminate wrong answers

Option A is wrong because defining individual product quality criteria is the purpose of a Product Description, not the Project Plan. Option B is wrong because detailing daily tasks for a single week is the purpose of a Team Plan or a Work Package, not the Project Plan. Option C is wrong because recording identified project risks is the purpose of the Risk Register, not the Project Plan.

Full explanation →

MCQmedium

A project risk has been identified regarding potential supply chain delays for sustainable materials. The Project Manager wants to assign ownership for investigating and monitoring this specific risk. Who should be assigned as the risk owner?

A.The person best suited to manage the risk

B.Corporate Risk Management

C.Always the Project Manager

D.The Executive exclusively

AnswerA

Assigning the person best suited to manage the risk satisfies the PRINCE2 requirement that risk ownership sits with whoever has the authority, expertise and resources to investigate and monitor it. Ownership is not tied to seniority or the Project Manager; the individual closest to the supply chain delay is best placed to act.

Why this answer

In PRINCE2, the risk owner is the person responsible for managing, monitoring, and controlling a specific risk. The risk owner should be the individual best suited to manage that risk, which may not always be the Project Manager. This ensures that the risk is handled by someone with the appropriate authority, expertise, and resources.

Exam trap

PRINCE2-Practitioner often tests the misconception that the Project Manager is always the risk owner, but the correct answer is that the risk owner is the person best suited to manage the risk.

How to eliminate wrong answers

Option B is wrong because Corporate Risk Management is typically responsible for overall risk framework and governance, not for managing individual project risks. Option C is wrong because the Project Manager is not automatically the risk owner for all risks; ownership should be assigned based on who is best positioned to manage the risk. Option D is wrong because the Executive is accountable for the business case and overall project success, but not necessarily the owner of every risk; risk ownership should be delegated appropriately.

Full explanation →

MCQhard

A project is using an agile delivery method within a PRINCE2 governance framework. The Project Board wants to ensure that delivery increments are meeting quality standards before acceptance. Who is responsible for formally accepting completed products on behalf of the user community?

A.The Senior Supplier

B.The Project Manager

C.The Senior User

D.Corporate Management

AnswerC

The Senior User represents the user community's interests and formally accepts completed products on its behalf, confirming they meet requirements. This satisfies the stem's agile-within-PRINCE2 scenario, where increments still require that role's acceptance before the Project Board authorises stage or project closure.

Why this answer

In PRINCE2, the Senior User role represents the user community's interests and is accountable for specifying user needs and ensuring that the project delivers products that meet those needs. Formal acceptance of completed products on behalf of the user community is a key responsibility of the Senior User, as they are the ones who will ultimately use or benefit from the products. This ensures that the products are fit for purpose from the user's perspective before final acceptance.

Exam trap

PRINCE2-Practitioner often tests the distinction between roles in the Project Board, particularly confusing the Senior User's responsibility for acceptance with the Project Manager's responsibility for delivery or the Senior Supplier's responsibility for quality.

How to eliminate wrong answers

Option A is wrong because the Senior Supplier is responsible for providing resources and expertise to deliver the products, not for accepting them on behalf of users. Option B is wrong because the Project Manager is responsible for day-to-day management and delivery within constraints, but not for formal acceptance on behalf of the user community. Option D is wrong because Corporate Management is outside the project organization and provides the mandate and resources, but does not formally accept products on behalf of users.

Full explanation →

Multi-Selectmedium

A project is experiencing severe difficulties in the current delivery stage. The Project Manager determines that stage tolerances will be exceeded. Which TWO documents or reports are directly involved in handling this exception situation?

Select 2 answers

A.Checkpoint Report

B.Daily Log

C.Project Brief

D.Exception Report

E.Exception Plan

AnswersD, E

When stage tolerances are forecast to be exceeded, the Project Manager escalates by producing an Exception Report documenting the deviation, its cause, impact and options. This triggers Project Board direction, satisfying the need to formally raise the exception before any corrective plan is authorised.

Why this answer

In PRINCE2, when a Project Manager forecasts that stage tolerances will be exceeded, the situation must be escalated to the Project Board via an Exception Report (option D), which documents the exception, its cause, impact, and options, and requests a decision. If the Board approves corrective action that changes the stage or project plan, an Exception Plan (option E) is produced to replace the remainder of the current Stage Plan (or Project Plan) and is approved through the same process as the original plan. The Checkpoint Report (A) is a progress update from a team to the Project Manager within a stage and does not handle tolerance breaches at stage level.

The Daily Log (B) is a personal record of informal issues and actions, not a formal exception document. The Project Brief (C) is a pre-project document capturing the initial scope and approach, and it plays no role in exception handling.

Exam trap

PRINCE2-Practitioner often tests the distinction between routine progress products (Checkpoint Report, Highlight Report, Daily Log) and the formal exception products (Exception Report, Exception Plan) — candidates pick Checkpoint Report because it sounds like the escalation document, but it is only a routine update.

Full explanation →

MCQmedium

A project team has reached the 'norming' stage of team development according to Bruce Tuckman's model referenced in PRINCE2 7. Which team dynamic characteristic should the Project Manager expect at this stage?

A.High levels of conflict and friction as members compete for roles and influence.

B.Disbandment of the team and emotional resistance to project closure.

C.Complete autonomy where the team operates effectively without any management oversight.

D.Establishment of working agreements, mutual trust, and a cohesive team identity.

AnswerD

Norming follows storming, when resolved conflict lets the team agree how to work together. Working agreements, mutual trust, and a shared identity are the defining characteristics of this stage, distinguishing it from the dependence of forming and the friction of storming.

Why this answer

In Tuckman's model, the 'norming' stage is characterized by the establishment of working agreements, mutual trust, and a cohesive team identity. Team members begin to resolve their differences, appreciate each other's strengths, and focus on the team's goals. The Project Manager should expect the team to start working collaboratively and constructively.

Exam trap

The trap is confusing the characteristics of the 'norming' stage with those of 'storming' or 'performing'. Candidates might choose 'complete autonomy' thinking it sounds positive, but that is more characteristic of 'performing'. The key is to remember that 'norming' is about establishing working agreements and trust.

How to eliminate wrong answers

Option A is wrong because high levels of conflict and competition for roles are typical of the 'storming' stage, not 'norming'. Option B is wrong because disbandment and emotional resistance to closure occur in the 'adjourning' stage. Option C is wrong because complete autonomy without management oversight is not a characteristic of 'norming'; it is more aligned with the 'performing' stage, and even then, some oversight may be needed.

Full explanation →

MCQeasy

In the PRINCE2 Quality practice, what is the purpose of establishing a Quality Register?

A.To list all identified threats and opportunities.

B.To maintain a chronological log of quality activities, tests, and results.

C.To record financial expenditures and cost variances.

D.To define the overall project organization structure.

AnswerB

The Quality Register provides a chronological record of all quality activities planned and undertaken — including tests, reviews and their results — giving the Project Manager an auditable log to track completion and confirm products meet their quality criteria.

Why this answer

The Quality Register is a PRINCE2 quality record that logs all quality activities — planned and actual — including tests, inspections, reviews, and their results. It provides an auditable trail of quality management throughout the project, supporting the Quality practice's goal of ensuring products meet their quality criteria. It is distinct from the Issue Register, Risk Register, and Lessons Log.

Exam trap

The trap is confusing the Quality Register with the Risk Register or Issue Register — candidates must remember that the Quality Register specifically logs quality activities, tests, and results, not risks or issues.

How to eliminate wrong answers

Option A is wrong because threats and opportunities are recorded in the Risk Register, not the Quality Register. Option C is wrong because financial expenditures and cost variances are tracked in the Business Case, financial reports, and the project budget — not the Quality Register. Option D is wrong because the project organization structure is defined in the Project Initiation Documentation (PID) and the Organizing practice, not the Quality Register.

Full explanation →

MCQhard

A PRINCE2 project is structured with multiple delivery teams operating under different Team Managers. One Team Manager consistently fails to provide Checkpoint Reports on time, blinding the Project Manager to potential schedule slippages. According to the Progress practice, what is the best governance remedy?

A.Escalate an issue to the Project Board regarding team-level reporting non-compliance and review team management arrangements.

B.Ignore the missing reports and prepare Highlight Reports based on guesswork.

C.Raise an Exception Report for the entire project.

D.Fire the Team Manager immediately without consulting anyone.

AnswerA

Late Checkpoint Reports are a team-management failure that blinds progress monitoring, so the Project Manager escalates the non-compliance as an issue to the Project Board. The Board can then review the team management arrangements, since only it holds the authority to change or replace a Team Manager's reporting obligations.

Why this answer

Escalating an issue to the Project Board regarding team-level reporting non-compliance and reviewing team management arrangements is the best governance remedy. The Progress practice requires timely and accurate information flow; persistent failure to provide Checkpoint Reports undermines the Project Manager's ability to monitor progress and control the project. Escalation allows the Project Board to address the non-compliance, potentially through the Senior Supplier or by changing team management arrangements.

Exam trap

PRINCE2-Practitioner often tests the misconception that the Project Manager should either ignore missing reports or immediately escalate to an Exception Report, when the correct first step is to address the issue and escalate to the Project Board if unresolved.

How to eliminate wrong answers

Option B is wrong because ignoring missing reports and preparing Highlight Reports based on guesswork violates the principle of accurate information and could lead to poor decisions. Option C is wrong because raising an Exception Report for the entire project is premature; the issue is with one team's reporting, not necessarily a project-level exception. Option D is wrong because firing the Team Manager immediately without consultation is not a governance remedy and bypasses proper escalation and due process.

Full explanation →

MCQhard

A project manager is working in an environment where senior management demands rigid adherence to a strict, unmodified, multi-year PRINCE2 methodology, despite the project being a small, two-week internal event. Which PRINCE2 principle is being violated by management's approach?

A.Learn from experience

B.Tailor to suit the project

C.Focus on products

D.Manage by exception

AnswerB

PRINCE2 must be scaled to the project's size, complexity, and risk. Applying an unmodified multi-year methodology to a two-week internal event ignores that requirement, violating the Tailor to suit the project environment principle, which demands adaptation rather than rigid adherence.

Why this answer

The PRINCE2 principle 'Tailor to suit the project' requires that the method be adapted to the project's size, complexity, importance, capability, and risk. A rigid, unmodified multi-year methodology applied to a two-week internal event is a textbook violation because the project's scale does not justify the full PRINCE2 framework. Tailoring ensures that PRINCE2 remains fit for purpose rather than becoming bureaucratic overhead.

Exam trap

PRINCE2-Practitioner often tests the misconception that PRINCE2 must be applied rigidly in all projects, confusing tailoring with abandoning the method, when in fact tailoring is a mandatory principle that requires adapting the method to the project's context.

How to eliminate wrong answers

Option A is wrong because 'Learn from experience' concerns capturing and applying lessons from previous projects, which is not the issue here—the problem is the inappropriate application of the method, not a failure to learn. Option C is wrong because 'Focus on products' is about defining and delivering products that meet quality criteria, and nothing in the scenario suggests that product definition is being neglected. Option D is wrong because 'Manage by exception' relates to delegating authority within defined tolerances, and the scenario describes rigid control, not a lack of exception management.

Full explanation →

Multi-Selectmedium

Which THREE of the following statements correctly describe how the PRINCE2 principle 'Manage by stages' is applied?

Select 3 answers

A.Breaking a project into stages allows risks to be reviewed and managed more effectively over time.

B.Management stages are identical to technical stages such as design, build, and test.

C.Management stages provide the Project Board with key decision-making points to authorize continuation.

D.Detailed planning is done for the current stage, while higher-level planning is maintained for later stages.

E.Projects must always have exactly three management stages regardless of their size.

AnswersA, C, D

Manage by stages divides the project into manageable chunks, each with its own plan, tolerances and end-of-stage assessment. This lets the Project Board review risks, business justification and progress at defined points, adjusting direction before committing further resources.

Why this answer

Option A is correct because dividing a project into management stages creates regular review points at which risks can be reassessed and managed as the project progresses, which is a core benefit of the 'Manage by stages' principle. Option C is correct because each management stage ends at a decision point where the Project Board reviews progress and business justification and authorizes (or refuses) continuation to the next stage. Option D is correct because PRINCE2 applies the 'manage by exception' and staged-planning approach: the current stage is planned in detail while later stages are only planned at a higher level until they are reached.

Option B is incorrect because management stages are governance/decision boundaries and are not the same as technical stages (such as design, build, and test), which relate to specialist work and may span or sit within management stages. Option E is incorrect because the number of management stages is not fixed at three; it depends on the size, complexity, and risk of the project and is determined during initiation.

Exam trap

PRINCE2-Practitioner often tests the confusion between management stages (governance decision points owned by the Project Board) and technical stages (specialist delivery phases), and the false belief that PRINCE2 prescribes a fixed number of stages.

Full explanation →

Multi-Selecthard

Which TWO of the following statements correctly describe the relationship between tolerances and reporting in the PRINCE2 Progress practice?

Select 2 answers

A.If stage tolerances are forecast to be breached, the Project Manager must raise an Exception Report.

B.Highlight Reports are used exclusively by Team Managers to report to the Project Manager.

C.Tolerances establish the boundaries of authority delegated by the Project Board to the Project Manager.

D.An Exception Plan is approved by the Project Manager without Project Board involvement.

E.Tolerances can only be set for time and cost, never for quality or scope.

AnswersA, C

Forecasting a stage tolerance breach triggers escalation because the Project Manager's delegated authority ends at that boundary. The Exception Report informs the Project Board, which owns stage tolerances, enabling it to direct corrective action or re-plan. This satisfies the stem's constraint that stage-level deviation requires formal upward reporting rather than local resolution.

Why this answer

Option A is correct because in PRINCE2, when stage tolerances are forecast to be exceeded, the Project Manager must escalate the matter by raising an Exception Report to the Project Board, which then decides how to proceed. Option C is correct because tolerances define the limits of delegated authority: the Project Board sets project-level tolerances and delegates stage tolerances to the Project Manager, who may only act within those boundaries. Option B is incorrect because Highlight Reports are produced by the Project Manager for the Project Board, not exclusively by Team Managers.

Option D is incorrect because an Exception Plan, once prepared, must be approved by the Project Board (the authority that set the tolerance), not by the Project Manager alone. Option E is incorrect because PRINCE2 tolerances can be set for the six aspects of project performance — time, cost, quality, scope, risk, and benefits — not only time and cost.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that Exception Plans are approved by the Project Manager or that tolerances only cover time and cost, when in fact the Board approves exception plans and tolerances span all six performance targets.

Full explanation →

MCQeasy

In the Quality practice, who is responsible for approving the Quality Management Approach and setting overall quality expectations?

A.Corporate Quality Assurance

B.The Team Manager

C.The Project Manager

D.The Project Board

AnswerD

The Project Board approves the Quality Management Approach and sets overall quality expectations, providing the mandate and resources for the Quality practice. This satisfies the stem's requirement for the approving authority, distinct from the Project Manager, who creates the approach, and assurance roles, which review it.

Why this answer

In PRINCE2, the Project Board is accountable for approving the Quality Management Approach and setting overall quality expectations, as part of its responsibility for project assurance and strategic direction. The Board owns the quality strategy at the project level, ensuring alignment with corporate quality standards.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between creating and approving the Quality Management Approach — candidates may select the Project Manager, but approval authority belongs to the Project Board.

How to eliminate wrong answers

Option A is wrong because Corporate Quality Assurance may provide standards and guidance, but approval of the project's Quality Management Approach rests with the Project Board. Option B is wrong because the Team Manager is responsible for executing quality activities within work packages, not setting overall quality expectations. Option C is wrong because the Project Manager creates and maintains the Quality Management Approach but does not approve it — approval is a Board responsibility.

Full explanation →

Multi-Selecthard

Which THREE of the following are specific responsibilities of the Project Board within the Directing a Project (DP) process?

Select 3 answers

A.Maintaining the daily Risk Log and Issue Register

B.Authorizing initiation

C.Drafting individual Work Package Descriptions

D.Authorizing a stage or Exception Plan

E.Authorizing project closure

AnswersB, D, E

Authorising initiation is a decision the Project Board alone can make, sitting within Directing a Project's DP1 activity. The Board reviews the Project Brief and confirms the project remains viable before committing resources to the Initiation Stage, satisfying the stem's requirement for a specific Board responsibility rather than a Project Manager task.

Why this answer

Within PRINCE2's Directing a Project (DP) process, the Project Board is accountable for the key decision points, and option B ('Authorizing initiation') is correct because DP activity DP1 requires the Board to approve the Project Brief and authorize the Project Initiation Documentation work to begin. Option D ('Authorizing a stage or Exception Plan') is correct because DP3 (Authorize a Stage or Exception Plan) is the Board's decision to approve the next Stage Plan or an Exception Plan before work proceeds. Option E ('Authorizing project closure') is correct because DP5 (Authorize Project Closure) is the Board's responsibility to confirm the project may be closed once the End Project Report and acceptance are in place.

Option A is incorrect because maintaining the daily Risk Log and Issue Register is a Project Manager (and Project Support) responsibility, not a Board decision activity. Option C is incorrect because drafting Work Package Descriptions is delegated to the Project Manager when agreeing work with Team Managers, not performed by the Project Board.

Exam trap

PRINCE2-Practitioner often tests the distinction between Project Board responsibilities and Project Manager responsibilities, tempting candidates to assign operational tasks like maintaining logs or drafting work packages to the Board.

Full explanation →

MCQhard

A project is currently executing the Controlling a Stage (CS) process. A new risk is identified that threatens the achievement of the stage objectives and exceeds the Project Manager's risk budget. What must the Project Manager do under CS?

A.Rewrite the Business Case to remove the affected benefits.

B.Close the project immediately without consulting anyone.

C.Absorb the risk cost by secretly cutting quality checks on other Work Packages.

D.Escalate the risk to the Project Board via an Issue Report or Exception Report.

AnswerD

Under Controlling a Stage, the Project Manager only handles risks within the delegated risk budget. A threat exceeding that tolerance becomes an exception, so it must be escalated to the Project Board through an Issue Report or Exception Report for a decision.

Why this answer

Under Controlling a Stage, the Project Manager must manage risks within the delegated tolerances and risk budget. When a risk exceeds the Project Manager's authority (risk budget), it becomes an exception that must be escalated to the Project Board via an Issue Report or Exception Report, so the Board can decide on corrective action. The Project Manager cannot unilaterally change the Business Case or absorb costs beyond delegated limits.

Exam trap

PRINCE2-Practitioner often tests the boundary of the Project Manager's authority versus the Project Board's authority, tricking candidates into choosing actions that exceed delegated tolerances.

How to eliminate wrong answers

Option A is wrong because the Business Case is owned by the Project Board and changing benefits is outside the Project Manager's authority under CS. Option B is wrong because closing a project is a Project Board decision made via Directing a Project, not a unilateral Project Manager action. Option C is wrong because secretly cutting quality checks violates the quality management approach and is a form of tolerance breach, not a valid risk response.

Full explanation →

MCQeasy

A project is underway to develop a new logistics system. During execution, a major industry regulation changes, rendering the current business case unviable. Which PRINCE2 principle is primarily being applied when the Project Board recommends stopping the project?

A.Continued business justification

B.Focus on products

C.Tailor to suit the project

D.Manage by exception

AnswerA

Continued business justification requires the project to remain viable and aligned with a valid Business Case throughout. When the regulation change invalidates that justification, the Project Board is obliged to stop or re-scope, so the principle directly drives the recommendation to halt.

Why this answer

The Continued business justification principle states that a PRINCE2 project must have a valid Business Case at all times, and if it ceases to be viable the project should be stopped. When a regulatory change invalidates the business case, the Project Board's recommendation to stop the project is the direct application of this principle — it is the 'stop' half of 'continue or stop' decision-making. This is why the Business Case is reviewed at every stage boundary and exception.

Exam trap

PRINCE2-Practitioner often tests the confusion between Continued business justification (should we still do this?) and Manage by exception (escalate when tolerances are breached) — candidates pick Manage by exception because a 'major change' sounds like an exception, but the trigger here is viability, not tolerance breach.

How to eliminate wrong answers

Option B is wrong because Focus on products is about defining outputs and their quality criteria, not about evaluating whether the project should continue. Option C is wrong because Tailor to suit the project concerns adapting PRINCE2 methods to project size, complexity, and environment, not terminating a project. Option D is wrong because Manage by exception is about delegating tolerance and escalating only when tolerances are forecast to be breached — it is a control mechanism, not the principle that mandates stopping when justification fails.

Full explanation →

MCQmedium

A PRINCE2 project is closing. The Project Manager is preparing the End Project Report and must decide what to include about the project's products. Which statement correctly describes the content required for the End Project Report?

A.It must include the detailed product descriptions for every product created, along with the quality inspection results for each product.

B.It must include the Project Initiation Documentation and the full Business Case, since these are the baseline against which the project is evaluated.

C.It must include the updated Risk Register, Issue Register, and Lessons Log as appendices, since these are formally handed over at project closure.

D.It must include a summary of the project's performance against its baseline, including costs, schedule, and benefits, and a review of how the project performed against the Business Case.

AnswerD

The End Project Report is the Project Manager's report to the Project Board at the end of the project. It summarizes performance against the project baseline, including cost, schedule, and benefits, and reviews the project against the Business Case. It also includes lessons and an assessment of whether the project has delivered the expected benefits, which supports the board's decision to approve closure. This matches the Closing a Project purpose of confirming the project's outputs and outcomes.

Why this answer

The End Project Report evaluates the project's performance against its baseline and reviews the Business Case, including whether expected benefits are being realized. It is a summary report for the Project Board, not a repository for every product description or management product. The Project Manager uses it to support the board's decision to approve project closure, so it must focus on performance, benefits, and lessons rather than duplicating detailed documentation.

Exam trap

The trap here is assuming the End Project Report must contain all detailed product and quality records, when it is actually a summary performance and benefits review that references those records.

Full explanation →

Multi-Selecthard

Which THREE of the following statements correctly characterize the application of the PRINCE2 principle 'Focus on products'?

Select 3 answers

A.A project's outputs and their quality requirements must be defined and agreed upon before work begins.

B.Deliverables must satisfy acceptance criteria before being formally signed off by the customer.

C.Product Descriptions are essential management products used to define each output's quality and criteria.

D.Focus on products means ignoring project schedules and focusing solely on deliverables.

E.The Project Manager is responsible for independently writing all Product Descriptions without consulting stakeholders.

AnswersA, B, C

Focus on products requires defining and agreeing outputs and their quality requirements before work commences, ensuring effort is directed at delivering specified products rather than activity for its own sake. This matches the principle's emphasis on agreed product definition.

Why this answer

Option A is correct because the 'Focus on products' principle requires that a project's outputs and their quality requirements be clearly defined and agreed upon before work begins, ensuring a shared understanding of what will be delivered. Option B is correct because deliverables must satisfy their defined acceptance criteria before being formally signed off by the customer, which is the mechanism by which the principle ensures fitness for purpose. Option C is correct because Product Descriptions are essential management products in PRINCE2 that define each output's purpose, composition, quality criteria, and quality method, directly supporting the 'Focus on products' principle.

Option D is incorrect because focusing on products does not mean ignoring schedules; PRINCE2 integrates product definition with plans and timescales, so schedules remain essential. Option E is incorrect because Product Descriptions are typically developed collaboratively with stakeholders and those with relevant expertise, not independently by the Project Manager alone.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that 'Focus on products' means ignoring schedules or that the Project Manager alone writes Product Descriptions, but the exam expects recognition of collaborative definition and quality criteria.

Full explanation →

MCQmedium

A project is implementing product-based planning. The Project Manager has created a Product Breakdown Structure. What is the next logical step in product-based planning?

A.Create the Schedule and Gantt chart immediately.

B.Write the detailed Product Descriptions for the identified products.

C.Estimate the duration and effort for each activity.

D.Establish work package tolerances.

AnswerB

Writing Product Descriptions follows directly from the Product Breakdown Structure, since the PBS only identifies and hierarchically arranges products without defining them. Each description then specifies purpose, composition, derivation, quality criteria, and responsibilities — the detail PRINCE2 requires before constructing the Product Flow Diagram and planning activities.

Why this answer

After creating a Product Breakdown Structure (PBS), the next logical step in product-based planning is to write detailed Product Descriptions for each identified product. This step defines the purpose, composition, quality criteria, and acceptance methods for each product, which are essential before planning activities and resources. It ensures that all products are clearly understood and agreed upon.

Exam trap

PRINCE2-PRACTITIONER often tests the sequence of product-based planning steps, expecting candidates to know that writing Product Descriptions follows the PBS, not scheduling or estimating.

How to eliminate wrong answers

Option A is wrong because creating a schedule and Gantt chart comes after defining products and their descriptions; it is an activity-based planning step that follows product definition. Option C is wrong because estimating duration and effort for activities occurs after product descriptions are written and activities are identified. Option D is wrong because establishing work package tolerances is part of the Managing a Stage Boundary process or authorizing work packages, not the immediate next step after PBS creation.

Full explanation →

MCQhard

An organization is executing a tiny internal improvement project that will last only two weeks and involve two people. The Project Manager suggests scaling down the standard PRINCE2 management products, governance boards, and reporting structures to match the scale. Which principle supports this decision?

A.Manage by exception

B.Tailor to suit the project

C.Focus on products

D.Manage by stages

AnswerB

Tailor to suit the project requires scaling PRINCE2's management products, governance and reporting to the project's size, complexity and risk. For a two-week, two-person project, this principle justifies the reduced documentation and lighter boards described.

Why this answer

'Tailor to suit the project' is the PRINCE2 principle that explicitly requires the method to be adapted to the project's size, complexity, risk, and environment. Scaling down management products, governance boards, and reporting for a two-week, two-person project is the textbook application of this principle. PRINCE2 is designed to be tailored, not applied rigidly.

Exam trap

PRINCE2-Practitioner often tests the difference between 'Tailor to suit the project' (adapting the method) and 'Manage by exception' (delegating authority) — candidates see 'scaling down' and may wrongly pick the latter.

How to eliminate wrong answers

Option A is wrong because 'Manage by exception' concerns delegating authority with tolerances so the Board only intervenes when thresholds are breached — it does not address scaling the method itself. Option C is wrong because 'Focus on products' is about defining and delivering products to agreed quality criteria, not about adapting governance artefacts. Option D is wrong because 'Manage by stages' is about dividing the project into governance stages with decision points, not about scaling documentation and boards.

Full explanation →

MCQhard

A project introduces a risk where a new software tool might fail to comply with upcoming environmental electronic waste regulations (ESG integration). The Project Manager wants to apply a response that transfers the financial impact of this risk. Which response is best suited?

A.Accepting the risk and doing nothing.

B.Avoiding the risk by canceling the project entirely.

C.Mitigating the risk by redesigning the software.

D.Transferring the risk by negotiating a strict vendor penalty clause for non-compliance.

AnswerD

Transfer shifts financial exposure to a third party. A strict vendor penalty clause for non-compliance makes the supplier bear the cost if the software breaches e-waste regulations, satisfying the requirement to transfer the financial impact rather than mitigate or accept it.

Why this answer

The option marked [CORRECT] is D because transferring a risk means shifting the financial impact to a third party, typically through insurance, warranties, or contractual penalties. A strict vendor penalty clause for non-compliance places the financial consequence of regulatory failure on the vendor, directly satisfying the Project Manager's goal. This aligns with PRINCE2's risk response 'transfer' (also called 'share' in some contexts), where the risk itself remains but the financial burden is reallocated.

The other options do not achieve financial transfer: acceptance retains the impact, avoidance eliminates the risk by cancelling the project (not transferring), and mitigation reduces probability or impact but does not shift financial liability.

Exam trap

PRINCE2-Practitioner often tests the confusion between 'transfer' and 'mitigate' or 'avoid', where candidates mistakenly think that redesigning software (mitigation) or cancelling the project (avoidance) transfers financial impact, when only a contractual or insurance arrangement truly shifts the financial burden to a third party.

How to eliminate wrong answers

Option A is wrong because accepting the risk means the project bears the full financial impact if the regulation is breached, which contradicts the goal of transferring financial impact. Option B is wrong because avoiding the risk by cancelling the project eliminates the risk entirely but does not transfer any financial impact; it simply abandons the project. Option C is wrong because mitigating the risk by redesigning the software reduces the likelihood or impact of non-compliance but does not transfer the financial consequence to another party; the project still retains the residual risk.

Full explanation →

MCQhard

A PRINCE2 project includes an environmental sustainability risk: excessive waste during manufacturing. The project team identifies an opportunity: partnering with a local recycling startup could turn this waste into a secondary revenue stream. Which risk response is most appropriate for this opportunity?

A.Exploit

B.Share

C.Enhance

D.Reject

AnswerA

Exploit suits this opportunity because the project can actively ensure the recycling partnership is realised, capturing the secondary revenue stream. It removes uncertainty by making the beneficial outcome happen, directly addressing the waste-to-revenue opportunity rather than merely sharing or enhancing it.

Why this answer

Exploit is the correct response because it seizes the opportunity to realize the benefits directly by removing uncertainty and ensuring the opportunity definitely happens. In this case, partnering with a local recycling startup turns waste into revenue, which is a proactive move to capture the positive risk. Exploit is used when the organization wants to make the opportunity occur and has the capability to do so.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between Exploit and Enhance for opportunities; candidates may confuse the two, but Exploit is about making the opportunity definitely happen, while Enhance only increases its probability or impact.

How to eliminate wrong answers

Option B is wrong because Share involves partnering with a third party to share the ownership and potential benefits of an opportunity, but here the project is not sharing the opportunity; it is actively exploiting it by forming a partnership to realize the benefit. Option C is wrong because Enhance aims to increase the probability and/or impact of an opportunity, but it does not guarantee that the opportunity will be realized; Exploit is stronger and more appropriate when the organization wants to ensure the opportunity happens. Option D is wrong because Reject is a response to a threat (avoidance) or to an opportunity that is not pursued; it is not applicable when the organization decides to actively pursue the opportunity.

Full explanation →

MCQmedium

A project manager is preparing a stage plan. To ensure that quality reviews are properly scheduled, what must be integrated into the schedule alongside technical task activities?

A.External auditor personal credentials

B.Quality review and testing activities

C.Operational staff annual leave records

D.Corporate shareholder meeting dates

AnswerB

Quality review and testing activities must be scheduled alongside technical tasks because PRINCE2 treats quality as a planned product-based activity; without them in the stage plan, reviews slip and products are accepted without the required evidence against their quality criteria.

Why this answer

In PRINCE2, the stage plan must include all activities required to deliver the stage's products, including quality control activities. Quality reviews and testing are essential to verify that products meet their quality criteria as defined in the product descriptions. By integrating these activities into the schedule, the project manager ensures that sufficient time and resources are allocated for quality checks, preventing them from being overlooked or rushed.

This aligns with the PRINCE2 principle of 'focus on products' and the quality theme, which requires planned quality control measures.

Exam trap

PRINCE2-Practitioner often tests the misconception that quality activities are separate from the schedule or can be performed ad-hoc, but the correct answer emphasizes their integration into the stage plan.

How to eliminate wrong answers

Option A is wrong because external auditor personal credentials are not a scheduling component; while auditors may be involved in some projects, their credentials are not activities to be integrated into the stage plan. Option C is wrong because operational staff annual leave records are not part of the stage plan; they may be considered as resource availability constraints, but they are not activities to be scheduled alongside technical tasks. Option D is wrong because corporate shareholder meeting dates are irrelevant to the stage plan; they are organizational events that do not directly contribute to the delivery of the stage's products.

Full explanation →

Multi-Selectmedium

Which TWO of the following statements correctly describe the application of the PRINCE2 principle 'Continued business justification'?

Select 2 answers

A.If the business justification for a project ceases, the project should be stopped.

B.Project managers are solely responsible for writing and owning the Business Case.

C.Business justification is only required during project initiation and final closure.

D.Business justification metrics must be strictly financial and cannot include qualitative benefits.

E.The business case must remain valid throughout the entire lifecycle of the project.

AnswersA, E

A project lacking valid business justification must be discontinued, satisfying the principle's requirement that justification remains valid throughout. PRINCE2 mandates that if the Business Case no longer demonstrates viable justification, the project board should stop the project rather than continue investing, ensuring resources are not wasted on unjustified work.

Why this answer

Option A is correct because the PRINCE2 principle 'Continued business justification' mandates that a project must have a justifiable reason to continue; if the Business Case no longer demonstrates viable justification (e.g., benefits no longer outweigh costs and risks), the project should be stopped rather than continued by inertia. Option E is correct because this principle requires the Business Case to be reviewed and revalidated at every stage boundary and whenever significant changes occur, ensuring justification remains valid throughout the entire project lifecycle, not just at initiation. Option B is incorrect because the Business Case is owned by the Executive (senior responsible owner), while the Project Manager typically writes and maintains it on the Executive's behalf.

Option C is incorrect because business justification must be continuously reviewed at stage boundaries and exception situations, not only at initiation and closure. Option D is incorrect because PRINCE2 explicitly allows both financial and non-financial/qualitative benefits (e.g., compliance, reputation, social value) to justify a project.

Exam trap

PRINCE2-Practitioner often tests the misconception that the Project Manager owns the Business Case and that justification is only checked at initiation and closure, when in fact the Executive owns it and it is re-validated at every stage boundary.

Full explanation →

100

MCQhard

An organization is executing a multi-year transformation project under PRINCE2 7. The corporate strategy shifts, placing a massive new emphasis on net-zero carbon targets. The Executive reviews the project's Business Case and realizes the project's outputs no longer align with the new strategic mandate, although the project is on time and under budget. What is the mandatory PRINCE2 action?

A.Ignore the corporate strategy shift until the project officially closes.

B.Transfer the project to the Senior Supplier to operate as commercial work.

C.Halt the project through premature closure because business justification no longer exists.

D.Continue the project because it is on time and under budget.

AnswerC

Continued business justification is mandatory, so a Business Case that no longer aligns with strategic mandate removes the project's rationale. On-time, under-budget delivery is irrelevant when benefits are invalidated, so premature closure is required rather than continuing to the next stage boundary.

Why this answer

In PRINCE2, the Business Case is the driving force behind any project, and it must be reviewed at every stage boundary and on an exception basis. If the project no longer aligns with corporate strategy and the business justification is invalidated, the correct action is to close the project prematurely. This is a mandatory principle: 'Continued business justification' requires that the project remains viable and aligned with strategic objectives.

Even if the project is on time and under budget, without a valid Business Case, it must be stopped.

Exam trap

PRINCE2-Practitioner often tests the misconception that projects should continue if they are on time and under budget, ignoring the need for continued business justification. Candidates may incorrectly prioritize schedule and cost performance over strategic alignment.

How to eliminate wrong answers

Option A is wrong because ignoring a strategic shift violates the PRINCE2 principle of continued business justification and the Executive's responsibility to ensure alignment with corporate strategy. Option B is wrong because transferring the project to the Senior Supplier is not a PRINCE2 process; the Senior Supplier is a role responsible for providing resources and expertise, not for taking over projects as commercial work. Option D is wrong because being on time and under budget does not justify continuing a project that no longer delivers value; PRINCE2 prioritizes business justification over schedule and cost performance.

Full explanation →

101

MCQmedium

A PRINCE2 project is applying the Quality practice. The Project Manager is defining the quality approach for a project that will deliver a new software system. The Project Manager must ensure that quality activities are properly planned and controlled. Which action best reflects the Quality practice?

A.Conduct a single quality review at the end of the project to assess whether all products meet the required quality criteria, and document the results in the End Project Report.

B.Assign all quality responsibilities to Project Assurance, since it is independent of the Project Manager and can verify products objectively.

C.Define quality criteria and quality methods for each product in its product description, and record quality activities in the Quality Register.

D.Rely on the supplier's internal quality management system and accept their quality certificates as evidence that the products meet the required criteria.

AnswerC

The Quality practice requires that quality criteria and quality methods be defined for each product, typically in the product description, and that quality activities be recorded in the Quality Register. This ensures that quality is planned into the project from the start and that quality control activities are tracked and reported. The Quality Register provides a record of planned and actual quality activities, including inspections and tests, which supports the Project Manager in monitoring quality progress.

Why this answer

The Quality practice requires quality criteria and methods to be defined for each product, and quality activities to be recorded and tracked in the Quality Register. This product-based approach ensures that quality is planned, controlled, and evidenced throughout the project. Relying solely on supplier certificates, deferring quality to a single end review, or assigning all quality work to Project Assurance would not provide the timely, product-level control that PRINCE2 requires.

Exam trap

The trap here is assuming quality can be delegated entirely to Project Assurance or verified only at the end, when PRINCE2 requires product-based quality criteria, methods, and activities planned and recorded throughout.

Full explanation →

102

MCQmedium

A PRINCE2 project is executing a stage. The Project Manager discovers that a supplier has delivered software that contains undocumented open-source components, violating corporate security and licensing standards. How should this be classified and handled?

A.Record as a risk in the Risk Register.

B.Log as a Request for Change to lower the corporate security standards.

C.Raise an Exception Report for the Project Board immediately.

D.Log as an off-specification in the Issue Register and require supplier remediation.

AnswerD

Undocumented open-source components breach the agreed specification, so this is an off-specification rather than a request for change or general concern. Logging it in the Issue Register and requiring supplier remediation restores conformity with corporate security and licensing standards.

Why this answer

Undocumented open-source components in delivered software violate corporate security and licensing standards, meaning the product does not meet its specification. In PRINCE2, this is classified as an off-specification, which is a type of issue. It should be logged in the Issue Register and the supplier required to remediate the non-compliance.

Exam trap

PRINCE2-Practitioner often tests the distinction between risks, issues, and changes, and candidates may incorrectly classify a current non-compliance as a risk or a request for change.

How to eliminate wrong answers

Option A is wrong because a risk is a potential future event, whereas this is an actual problem that has already occurred. Option B is wrong because a Request for Change is for proposing a change to a baseline, not for addressing a violation of standards; lowering security standards is not appropriate. Option C is wrong because an Exception Report is only needed if tolerances are forecast to be exceeded; there is no indication of that here, and the issue should first be handled at the project level.

Full explanation →

103

MCQeasy

Under the PRINCE2 Organizing practice, which role represents the interests of those who will use the project's outputs, operate the resulting solution, or realize the benefits?

A.Senior User

B.Project Assurance

C.Senior Supplier

D.Executive

AnswerA

The Senior User role embodies those who specify and use the project's outputs, operate the solution and realise benefits. This satisfies the Organizing practice's requirement to represent user interests on the Project Board, distinct from the Senior Supplier who provides resources and the Executive who owns the business case.

Why this answer

The Senior User role in PRINCE2 represents the interests of those who will use the project's outputs, operate the resulting solution, or realize the benefits. This role is accountable for specifying the user requirements and ensuring the solution meets them, thereby securing the expected benefits. The Senior User sits on the Project Board alongside the Executive and Senior Supplier, providing the user perspective throughout the project lifecycle.

Exam trap

PRINCE2-Practitioner often tests the confusion between the Executive (who owns the business case) and the Senior User (who represents users and benefits), leading candidates to incorrectly select the Executive for user-related responsibilities.

How to eliminate wrong answers

Option B is wrong because Project Assurance is a role that provides independent oversight and monitoring of the project on behalf of the Project Board, not a representation of user interests. Option C is wrong because the Senior Supplier represents the interests of those designing, developing, and delivering the project's products, not the users or operators. Option D is wrong because the Executive is the single individual ultimately accountable for the project's success and owns the business case, but does not specifically represent the users who will operate the solution or realize benefits.

Full explanation →

104

Multi-Selectmedium

During the Managing a Stage Boundary process, the Project Manager is preparing for the End Stage Report. Which TWO of the following activities are essential when compiling this report? (Choose two.)

Select 2 answers

A.Conducting a benefits realisation review with the business stakeholders.

B.Reviewing the stage's performance against its tolerances.

C.Updating the Project Plan with actual progress and revised forecasts.

D.Preparing the next Stage Plan in detail.

E.Summarising the stage's issues and risks and their status.

AnswersB, E

The End Stage Report must summarise the stage's actual performance compared to the Stage Plan, including any deviations from tolerances. This review provides the Project Board with the necessary information to decide whether to proceed. It is a core input to the report, ensuring transparency and informed decision-making.

Why this answer

The End Stage Report is a critical document that provides the Project Board with a summary of the stage's performance, including progress against tolerances and the status of issues and risks. These elements are essential for the Board to make an informed decision about continuing the project. Activities like updating the Project Plan or preparing the next Stage Plan are separate from compiling the report, although they may use its content.

Exam trap

The trap here is conflating the End Stage Report with other deliverables of the Managing a Stage Boundary process, such as the next Stage Plan, which are distinct.

Full explanation →

105

MCQmedium

A project is using PRINCE2 to deliver a new healthcare information system. The Project Manager is reviewing the project's progress and notices that the project's business case has not been updated since the project was initiated six months ago. During this time, the regulatory environment has changed, and the expected benefits are now less certain. Which PRINCE2 principle is being violated?

A.Learn from experience

B.Manage by stages

C.Continued business justification

D.Focus on products

AnswerC

This is correct because the principle 'Continued business justification' requires that the business case is reviewed and updated throughout the project to ensure that the project remains viable and aligned with the business objectives. Failing to update the business case despite significant changes in the regulatory environment violates this principle.

Why this answer

The principle 'Continued business justification' mandates that a project must have a justified business case that is reviewed and updated throughout the project lifecycle. In this scenario, the business case has not been updated despite significant regulatory changes that affect the expected benefits, which means the project may no longer be justified. This is a clear violation of the principle.

Exam trap

The trap here is to focus on the review aspect and attribute it to 'Manage by stages', but the specific violation is the lack of ongoing justification, which is the domain of 'Continued business justification'.

Full explanation →

106

MCQmedium

A PRINCE2 project is executing a stage. The Project Manager wants to establish how frequently Highlight Reports will be submitted to the Project Board. Where should this reporting frequency be formally defined?

A.Risk Register

B.Stage Plan

C.Communication Management Approach

D.Project Product Description

AnswerC

The Communication Management Approach defines the Project Board's information needs, including the frequency, format and recipients of Highlight Reports. It is the PRINCE2 document that formally records reporting frequency, satisfying the stem's requirement to establish how often reports are submitted.

Why this answer

The frequency of Highlight Reports is a communication management detail and should be formally defined in the Communication Management Approach. This document describes the communication needs of the project, including what information will be shared, with whom, when, and how. It is the correct place for reporting frequency.

Exam trap

The trap is selecting the Stage Plan or Highlight Report itself as the location for frequency, but PRINCE2 specifies that communication frequency is documented in the Communication Management Approach.

How to eliminate wrong answers

Option A is wrong because the Risk Register records risks and responses, not communication frequencies. Option B is wrong because the Stage Plan details the work, schedule, and resources for a stage, but not the reporting frequency to the Project Board. Option D is wrong because the Project Product Description defines the customer's quality expectations and acceptance criteria, not communication protocols.

Full explanation →

107

Multi-Selectmedium

Which TWO of the following describe valid aspects of the Issues practice in PRINCE2 7? (Choose two)

Select 2 answers

A.Team Managers have the authority to increase project stage cost tolerances.

B.The Issue Register is maintained by Corporate Management outside the project.

C.Issues must be resolved exclusively by the Executive without team input.

D.Issues can be categorized as Requests for Change, Off-specifications, or Problems/Concerns.

E.All formal issues must be captured and logged in the Issue Register.

AnswersD, E

PRINCE2 7 classifies issues into three types: Requests for Change, Off-specifications, and Problems/Concerns. This taxonomy drives how each issue is assessed and escalated, so the categorisation described is a valid aspect of the Issues practice.

Why this answer

Option D is correct because PRINCE2 7 classifies issues into three types: Requests for Change (RFCs), Off-specifications (something not meeting a specification), and Problems/Concerns (general issues raised by stakeholders). Option E is correct because the Issues practice requires that all formal issues be captured and logged in the Issue Register, which is maintained by the Project Manager as part of the project's issue management approach. Option A is incorrect because cost tolerances are set by the Project Board and can only be changed by them, not by Team Managers.

Option B is incorrect because the Issue Register is maintained by the Project Manager within the project, not by Corporate Management outside it. Option C is incorrect because issues are not resolved exclusively by the Executive; the Project Manager and team members are typically involved in assessing and resolving issues, with escalation to the Project Board only when tolerances are threatened.

Exam trap

PRINCE2-Practitioner often tests the misconception that issues are only changes or that the Issue Register is maintained outside the project; the trap is confusing the Issue Register with the Risk Register or assuming Corporate Management owns it.

Full explanation →

108

MCQhard

A PRINCE2 project is operating with decentralized agile delivery teams. An issue arises where two teams have conflicting dependencies on a shared database component, threatening the stage schedule. The Team Managers cannot resolve it between themselves. What is the correct escalation path under PRINCE2?

A.Escalate the issue to the Project Manager for logging and resolution.

B.Escalate directly to Corporate, Programme Management or Portfolio Direction.

C.Raise an Exception Report to the Project Board immediately.

D.Ignore the conflict and let the teams figure it out to preserve agile self-organization.

AnswerA

Team Managers escalate issues they cannot resolve to the Project Manager, who logs them in the Issue Register and decides on resolution. Escalating to the Project Board would breach the management level at which this dependency conflict belongs.

Why this answer

In PRINCE2, the Project Manager is responsible for managing issues and escalating to the Project Board only if the issue threatens stage tolerances or cannot be resolved within the Project Manager's authority. The Team Managers should first escalate to the Project Manager, who logs the issue and attempts resolution. Direct escalation to the Board or Corporate is not the correct path.

Exam trap

PRINCE2-Practitioner often tests the escalation path for issues, so candidates who jump directly to the Project Board or Corporate without involving the Project Manager pick the wrong answer.

How to eliminate wrong answers

Option B is wrong because escalation to Corporate, Programme Management or Portfolio Direction is only appropriate for issues beyond the project's authority, typically via the Project Board. Option C is wrong because an Exception Report is raised only when a tolerance is forecast to be exceeded; the issue has not yet threatened stage tolerances, and the Project Manager should first assess and manage it. Option D is wrong because ignoring the conflict violates PRINCE2's issue management and could jeopardize the stage schedule.

Full explanation →

109

Multi-Selecthard

When implementing the Risk practice in a PRINCE2 7 project, which THREE of the following steps are part of the risk management procedure? (Choose three)

Select 3 answers

A.Depreciate (writing off risk assets over time)

B.Identify (context and risks)

C.Liquidate (closing supplier contracts automatically)

D.Plan (selecting and planning risk responses)

E.Assess (estimating probability and impact)

AnswersB, D, E

Identify is the first step of the PRINCE2 risk management procedure, covering both understanding the project context and recognising individual threats and opportunities. It precedes assessment and planning, ensuring risks are captured before being estimated or responded to.

Why this answer

The PRINCE2 7 risk management procedure consists of five steps: Identify, Assess, Plan, Implement, and Communicate. Option B (Identify) is correct because the procedure begins with identifying the risk context and then the risks themselves, establishing what could threaten or enhance the project objectives. Option E (Assess) is correct because this step covers estimating each risk's probability and impact and then evaluating them to prioritize which risks need attention.

Option D (Plan) is correct because this step involves selecting appropriate risk responses and preparing the specific response plans for the prioritized risks. Options A (Depreciate) and C (Liquidate) are incorrect because they are financial/accounting and contract-closure concepts, not steps in the PRINCE2 risk management procedure.

Exam trap

PRINCE2-Practitioner often tests the exact naming and sequence of the risk management procedure steps, luring candidates with plausible-sounding business terms like 'Depreciate' or 'Liquidate' that belong to finance, not risk.

Full explanation →

110

Multi-Selecthard

Which THREE of the following management products are part of the PRINCE2 Quality practice framework?

Select 3 answers

A.Quality Register

B.Product Description

C.Issue Register

D.Risk Register

E.Quality Management Approach

AnswersA, B, E

The Quality Register is a core PRINCE2 management product within the Quality practice, recording quality activities, results and approvals throughout the project. It satisfies the stem's requirement by tracking planned and completed quality checks, providing the audit trail the Quality practice demands for verifying that products meet their agreed quality criteria.

Why this answer

The PRINCE2 Quality practice defines several management products, and the Quality Register (A) is correct because it is the log used to record quality activities, including planned quality inspections and their results, throughout the project. The Product Description (B) is correct because it documents the purpose, composition, derivation, format, quality criteria, and quality method for a product, forming the basis for quality control. The Quality Management Approach (E) is correct because it describes how the project will implement quality management, including procedures, techniques, standards, and responsibilities.

The Issue Register (C) is not part of the Quality practice; it belongs to the Change practice and records issues and their resolution. The Risk Register (D) is not part of the Quality practice; it belongs to the Risk practice and captures identified risks, their analysis, and responses.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between management products from different practices, such as mixing up the Quality Register with the Issue Register or Risk Register, because they are all logs but belong to distinct practices.

Full explanation →

111

MCQeasy

Which PRINCE2 practice focuses on defining *how*, *when*, and *by whom* a project's products will be created, verified, and controlled?

A.Plans practice

B.Quality practice

C.Progress practice

D.Business Case practice

AnswerA

The Plans practice defines how, when and by whom products are created, verified and controlled, matching the stem's three-part requirement exactly. It produces the Project, Stage and Team Plans that schedule products, assign responsibilities and set the control and verification arrangements.

Why this answer

The Plans practice in PRINCE2 is specifically responsible for producing the Project Plan, Stage Plans, and Team Plans, which define the products to be delivered, the activities and resources required, the timescales, and the responsibilities for creation, verification, and control. It answers the 'how, when, and by whom' questions through the product-based planning technique, including Product Descriptions and Product Breakdown Structures. The other practices deal with different aspects: Quality defines acceptance criteria, Progress tracks performance, and Business Case justifies the investment.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the Plans practice and the Quality practice, as both involve defining requirements for products; candidates must remember that Plans defines the creation and control mechanisms, while Quality defines the acceptance criteria and verification methods.

How to eliminate wrong answers

Option B is wrong because the Quality practice focuses on defining quality criteria, quality assurance, and quality control activities, not on the scheduling and assignment of work to create products. Option C is wrong because the Progress practice is concerned with monitoring and reporting on the achievement of plans, not with defining how and when products will be created. Option D is wrong because the Business Case practice deals with the justification for the project based on costs, benefits, risks, and timescales, not with the detailed planning of product creation.

Full explanation →

112

MCQhard

A PRINCE2 project is executing its final stage. During the Closing a Project process, the Project Manager prepares the End Project Report. A key stakeholder demands that the project remain open for another three months to support post-project user adoption. According to PRINCE2, how should this be handled?

A.Transfer project executive accountability to the Senior User and keep the project open.

B.Reject project closure and rewrite the PID into a new Stage Plan.

C.Proceed with project closure, handing over operational user adoption responsibilities to operational management as outlined in the Benefits Management Approach.

D.Extend the project duration by three months to manage user adoption.

AnswerC

PRINCE2 closure transfers post-project user adoption to operational management, as defined in the Benefits Management Approach. Keeping the project open for adoption support falls outside the project's remit; benefits realisation is owned operationally after the project closes, so the Project Manager proceeds with closure.

Why this answer

PRINCE2 treats the project as a temporary organisation that ends when its products are delivered and accepted; post-project user adoption is an operational responsibility, not a project one. The Benefits Management Approach defines how benefits will be measured and who owns post-project activities, so the Project Manager should proceed with closure and hand over adoption responsibilities to operational management.

Exam trap

The trap is conflating project closure with benefit realisation — candidates may think the project must stay open until benefits are fully realised, but PRINCE2 assigns post-project benefit tracking to operational management via the Benefits Management Approach.

How to eliminate wrong answers

Option A is wrong because transferring executive accountability to the Senior User and keeping the project open violates the temporary nature of projects and the defined roles — the Executive remains accountable until closure. Option B is wrong because rewriting the PID into a new Stage Plan is not a valid response to a stakeholder demand and misuses PRINCE2 artefacts. Option D is wrong because extending the project purely to manage user adoption confuses project delivery with business-as-usual operations, which is outside the project mandate.

Full explanation →

113

MCQeasy

Which PRINCE2 process runs from the initial pre-project phase until the project is successfully initiated or aborted?

A.Initiating a Project

B.Controlling a Stage

C.Directing a Project

D.Starting up a Project

AnswerD

Starting up a Project is the pre-project process, triggered by the mandate and running until the Project Board authorises Initiating a Project. It produces the Project Brief and appoints the Project Manager and Executive, satisfying the stem's requirement for the process spanning pre-project activity.

Why this answer

Starting up a Project is the pre-project process that runs from the initial mandate until the project is either successfully initiated (i.e., the Project Brief is approved and the board authorizes initiation) or aborted. It produces the Project Brief, the outline Business Case, the project approach, and the daily log, and appoints the project management team. It is deliberately short and ends with the 'Authorize Initiation' decision by the Project Board.

Exam trap

PRINCE2-Practitioner often tests the boundary between Starting up a Project (pre-project, produces Project Brief) and Initiating a Project (produces PID), tricking candidates into choosing the latter for questions about the pre-project phase.

How to eliminate wrong answers

Option A is wrong because Initiating a Project begins after Starting up a Project has completed and the board has authorized initiation; it produces the PID, not the pre-project groundwork. Option B is wrong because Controlling a Stage operates during delivery stages, not in the pre-project phase. Option C is wrong because Directing a Project is an ongoing process that runs from project authorization through to project closure, spanning the whole project rather than being confined to the pre-project phase.

Full explanation →

114

MCQeasy

During the Initiating a Project process, the Project Manager must prepare the Project Plan. What does this plan specifically cover?

A.Post-project operational maintenance schedules

B.The entire project's timescales, costs, and major products across all stages

C.Only the activities of the Starting up a Project process

D.Detailed weekly tasks for the immediate delivery team only

AnswerB

The Project Plan covers the entire project, spanning all stages, and defines timescales, costs and major products. This satisfies the stem's requirement for what the Project Manager prepares during Initiating a Project, distinct from stage plans.

Why this answer

The Project Plan in PRINCE2 covers the entire project, including all stages, and details the timescales, costs, and major products. It is a high-level plan that provides the baseline for monitoring and control throughout the project.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the Project Plan and Stage Plans, leading candidates to select options that describe only a portion of the project or operational activities.

How to eliminate wrong answers

Option A is wrong because post-project operational maintenance schedules are typically covered in the Benefits Management Approach or operational plans, not the Project Plan. Option C is wrong because the Project Plan covers the whole project, not just the Starting up a Project process. Option D is wrong because detailed weekly tasks for the immediate team are found in Team Plans, not the Project Plan.

Full explanation →

115

MCQhard

A PRINCE2 project is operating with time and cost tolerances set at +/- 5%. Halfway through Stage 2, a major disruption occurs. The Project Manager forecasts a cost overrun of 8% and a schedule delay of 10%. What governance procedure is triggered?

A.Exception procedure resulting in an Exception Report to the Project Board

B.Risk Management Approach review by Project Assurance

C.Project Closure procedure

D.Initiating a Project process

AnswerA

Forecast overruns of 8% cost and 10% delay breach the +/-5% Stage tolerances, so the Project Manager must raise an Exception Report and escalate to the Project Board, which decides whether to continue, change scope, or close.

Why this answer

When the forecast cost overrun (8%) and schedule delay (10%) both exceed the stage tolerances (+/- 5%), the Project Manager must trigger the Exception procedure and produce an Exception Report for the Project Board. The Board then decides whether to authorize an Exception Plan or take other action. This is the standard PRINCE2 governance response to a forecast tolerance breach.

Exam trap

PRINCE2-Practitioner often tests the distinction between the Exception procedure and other governance responses, catching candidates who pick 'Project Closure' or 'Risk Management Approach review' instead of recognizing a tolerance breach triggers an Exception Report.

How to eliminate wrong answers

Option B is wrong because a Risk Management Approach review by Project Assurance is not a governance procedure triggered by a tolerance breach; Project Assurance provides independent oversight but does not respond to exceptions. Option C is wrong because Project Closure is triggered when the project is ending (either prematurely or at completion), not when a stage tolerance is breached mid-project. Option D is wrong because Initiating a Project is the process used at the start of the project to develop the PID; it is not re-triggered by a mid-stage exception (though an Exception Plan may be developed, that is part of the Exception procedure, not Initiating a Project).

Full explanation →

116

Multi-Selectmedium

Which THREE of the following principles are among the seven core principles of PRINCE2?

Select 3 answers

A.Learn from experience

B.Continuous risk elimination

C.Tailor to suit the project

D.Focus on products

E.Manage by consensus

AnswersA, C, D

Learn from experience is one of the seven PRINCE2 principles, requiring lessons to be sought, recorded and acted upon throughout the project rather than only at closure. This satisfies the principle-selection constraint by naming a genuine core principle that governs continual improvement.

Why this answer

Option A (Learn from experience) is correct because PRINCE2's seven principles explicitly include 'Learn from experience,' requiring the project team to capture and apply lessons throughout the project, not just at closure. Option C (Tailor to suit the project) is correct because 'Tailor to suit the project environment' is a core PRINCE2 principle, ensuring the method's processes, themes, and documentation are scaled appropriately to the project's size, complexity, and risk. Option D (Focus on products) is correct because 'Focus on products' is a PRINCE2 principle that directs the project to define and deliver products meeting agreed quality criteria, using product descriptions and the product breakdown structure.

Option B (Continuous risk elimination) is not a PRINCE2 principle; PRINCE2 addresses risk through the Risk theme and 'Manage by exception,' and it does not aim to eliminate all risk. Option E (Manage by consensus) is not a PRINCE2 principle; PRINCE2 uses 'Manage by exception' with defined tolerances and a single accountable Project Board, rather than consensus-based decision-making.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the seven principles, seven themes, and seven processes — candidates pick plausible-sounding but non-existent principles like 'continuous risk elimination' or 'manage by consensus'.

Full explanation →

117

MCQhard

An organization is executing a software development project where user requirements change rapidly. The Project Manager ensures that every delivered software increment has a clear Product Description outlining its acceptance criteria before development starts. Which PRINCE2 principle is being rigorously applied?

A.Continued business justification

B.Manage by stages

C.Focus on products

D.Tailor to suit the project

AnswerC

Focus on products requires defining each product's purpose, composition and quality criteria, here via Product Descriptions with acceptance criteria, before work begins. This satisfies the stem's constraint of rapidly changing requirements by basing development on agreed product definitions rather than shifting specifications.

Why this answer

'Focus on products' requires that projects define and deliver products against agreed Product Descriptions, which specify purpose, composition, quality criteria, and acceptance criteria. The scenario explicitly states that every delivered increment has a clear Product Description with acceptance criteria before development starts — this is the direct application of the principle.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between 'focus on products' and 'manage by stages' — candidates see 'increments' and 'delivery' and wrongly pick manage by stages, missing that the defining feature of the scenario is the Product Description and acceptance criteria.

How to eliminate wrong answers

Option A is wrong because 'continued business justification' concerns whether the project remains viable and aligned with the Business Case, not the definition of product acceptance criteria. Option B is wrong because 'manage by stages' concerns dividing the project into authorised increments, not the product definition itself. Option D is wrong because 'tailor to suit the project' concerns adapting PRINCE2 to the project context, not the rigorous definition of product acceptance criteria.

Full explanation →

118

MCQmedium

During the Initiating a Project process, the Project Manager is defining the Change Control Approach. What is the primary purpose of this approach?

A.To outline how staff members will be hired and dismissed during the project.

B.To determine how financial invoices are paid to external suppliers.

C.To establish how benefits will be measured post-project.

D.To specify how potential issues and changes to baselined products will be logged, assessed, and controlled.

AnswerD

The Change Control Approach defines the mechanism for recording, assessing, and deciding upon issues and changes affecting baselined products, including roles, tolerances, and escalation. This directly satisfies the Initiating a Project purpose of establishing how change will be governed before delivery begins.

Why this answer

The Change Control Approach defines how the project will manage issues and changes to baselined products, including how they are logged, assessed, and controlled. It is part of the Project Initiation Documentation and ensures that changes are handled consistently and with appropriate authority.

Exam trap

Candidates often confuse the Change Control Approach with other strategies like Risk or Quality, or with the Benefits Management Approach — the key is to remember that change control is specifically about issues and changes to baselined products.

How to eliminate wrong answers

Option A is wrong because staff hiring and dismissal are covered by the organization's HR policies, not the Change Control Approach. Option B is wrong because supplier invoicing is a financial/contract management matter, not change control. Option C is wrong because benefits measurement is addressed in the Benefits Management Approach, not the Change Control Approach.

Full explanation →

119

MCQmedium

During Starting up a Project (SU), the Project Manager is drafting the Project Brief. The Corporate/Programme level wants to know what specific benefits will be achieved, but the exact realization dates and financial metrics are still too uncertain to finalize. How should the Project Manager handle this in the Project Brief?

A.Delay the authorization of the Starting up a Project process until Corporate provides exact financial projections.

B.Leave out the Business Case entirely until the Initiating a Project process is authorized.

C.Include an outline Business Case capturing the expected benefits and general timing, acknowledging that precise metrics will be refined during Initiation.

D.Include a fully detailed Business Case with guaranteed ROI figures to satisfy the Executive.

AnswerC

An outline Business Case fits Starting up a Project, where only the Project Brief is produced; the full Business Case belongs to Initiating a Project. Capturing expected benefits and general timing satisfies the Corporate/Programme need for direction while deferring precise metrics, which remain too uncertain to finalise at this stage.

Why this answer

The Project Brief produced during Starting up a Project (SU) contains an outline Business Case — enough to justify the project's initiation, but not the full detailed Business Case, which is developed during Initiating a Project (IP). The outline captures expected benefits and general timing while acknowledging that precise metrics, costs, and ROI will be refined during Initiation. This matches PRINCE2's principle of 'continued business justification' without over-committing to uncertain figures.

Exam trap

PRINCE2-Practitioner often tests the difference between the outline Business Case (SU) and the detailed Business Case (IP) — candidates mistakenly believe SU requires a fully costed case, or that the Business Case can be omitted from the Project Brief.

How to eliminate wrong answers

Option A is wrong because delaying authorization of SU until exact financials are available contradicts PRINCE2's staged approach — SU is designed to produce an outline, not a fully costed case, and blocking it defeats the purpose of the pre-project stage. Option B is wrong because the Business Case is a required component of the Project Brief; omitting it entirely violates the PRINCE2 theme of Business Case and leaves the project without justification. Option D is wrong because fabricating guaranteed ROI figures is dishonest and violates the 'continued business justification' principle — the Business Case must be realistic and refined as information becomes available, not artificially inflated to please the Executive.

Full explanation →

120

MCQmedium

A project manager receives an urgent request from a Senior User to add a new feature that was not in the original Project Product Description. The feature requires minor effort and fits within the stage cost tolerance. How should this request be handled?

A.Add the feature to the Risk Register as an opportunity.

B.Log the request as a Request for Change in the Issue Register and evaluate its impact.

C.Reject the request because scope can never be changed after project initiation.

D.Implement the feature immediately since it fits within stage cost tolerance.

AnswerB

Any proposed change to baselined products must follow change control, regardless of size or tolerance headroom. Logging it as a Request for Change in the Issue Register triggers impact evaluation on scope, cost, schedule and risk before the Project Board or delegated authority decides, preserving the integrity of the agreed baseline.

Why this answer

The request is a change to the project's scope, so it must be handled through the change control process. Logging it as a Request for Change in the Issue Register and evaluating its impact ensures that the change is properly assessed, approved or rejected, and documented. Even if it fits within tolerance, the change must go through the appropriate configuration management and change control steps.

Exam trap

The trap is thinking that because the change is minor and within tolerance, it can be implemented without going through change control. The exam emphasizes that all changes must be managed through the change control process, regardless of size, to ensure proper evaluation and documentation.

How to eliminate wrong answers

Option A is wrong because adding it to the Risk Register as an opportunity is not appropriate; it is a change request, not a risk. Option C is wrong because scope can be changed after project initiation, but it must go through change control. Option D is wrong because implementing immediately without evaluation bypasses the change control process and could have unforeseen impacts on other parts of the project, even if it fits within cost tolerance.

Full explanation →

121

MCQeasy

When establishing project roles in the Organizing practice, why is it recommended that the Executive and the Project Manager roles not be held by the same person?

A.So that the Project Manager can act as the Senior User simultaneously.

B.To allow the Project Manager to have final approval over the project budget.

C.To ensure segregation of duties and maintain objective governance and accountability.

D.Because PRINCE2 mandates that project managers must always report to external contractors.

AnswerC

Separating Executive and Project Manager preserves segregation of duties: the Executive owns the business justification and chairs the Project Board, while the Project Manager runs day-to-day delivery. Combining them removes independent scrutiny, undermining objective governance and accountability for project success.

Why this answer

The Executive and Project Manager roles must be held by different people to ensure segregation of duties, preventing a conflict of interest where the same individual would both direct the project and be accountable for its day-to-day delivery. This separation maintains objective governance, as the Executive represents the business interests and holds the Project Manager accountable for performance, while the Project Manager focuses on managing the project on a daily basis. PRINCE2 emphasizes clear accountability and checks and balances within the project organization.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that the Executive and Project Manager can be combined for efficiency, but the exam expects candidates to recognize that this violates the principle of defined roles and responsibilities and segregation of duties.

How to eliminate wrong answers

Option A is wrong because the Senior User role is a separate project board role representing user interests, not a fallback for the Project Manager; combining them would also violate segregation of duties. Option B is wrong because budget approval authority typically rests with the Project Board or Executive, not the Project Manager, and this does not explain why the roles should be separate. Option D is wrong because PRINCE2 does not mandate that project managers report to external contractors; this is a fabricated constraint not found in the method.

Full explanation →

122

MCQhard

A project is subject to strict ESG reporting requirements. The Project Board needs assurance that the project's sustainability benefits are being accurately measured and reported. Who should provide independent assurance of these benefits?

A.The Team Manager

B.Project Assurance

C.The Project Manager

D.The Senior Supplier

AnswerB

Project Assurance independently monitors performance against the Business Case on the Project Board's behalf, so it verifies that sustainability benefits are measured and reported accurately. This satisfies the ESG assurance constraint by giving the Board objective confidence in reported benefits, separate from the Project Manager's own reporting.

Why this answer

In PRINCE2, Project Assurance is the role responsible for independently monitoring all aspects of project performance and providing the Project Board with confidence that the project remains viable and on track. Because the Board needs independent assurance that ESG/sustainability benefits are being measured and reported accurately, Project Assurance is the correct provider — it is explicitly independent of the Project Manager and Team Manager. This independence is what makes the assurance credible to the Board.

Exam trap

PRINCE2-Practitioner often tests the independence principle — candidates confuse the Project Manager's monitoring duties with Project Assurance and pick the Project Manager because they 'own' reporting, missing that assurance must be independent of the delivery chain.

How to eliminate wrong answers

Option A is wrong because the Team Manager is responsible for producing the products and managing the team, not for providing independent assurance to the Board; their view is inherently operational and not independent. Option C is wrong because the Project Manager runs the project day-to-day and cannot independently assure their own work — PRINCE2 explicitly separates assurance from management. Option D is wrong because the Senior Supplier represents the supplier interests on the Board and is accountable for the quality of supplier products, not for independent assurance of benefit measurement.

Full explanation →

123

MCQmedium

In the Managing Product Delivery (MP) process, what is the purpose of the 'Accepting a work package' activity?

A.To allow the Team Manager to bypass the Project Manager and report directly to the Executive.

B.To authorize the creation of a new stage in the project schedule.

C.To formally close the project and hand over products to operations.

D.To ensure the Team Manager understands and commits to delivering the Work Package within agreed constraints.

AnswerD

Accepting a work package confirms the Team Manager understands the scope, tolerances and constraints before committing to delivery. This satisfies the stem's requirement by establishing the agreement between Project Manager and Team Manager, ensuring the Work Package is only accepted when achievable within the agreed time, cost and quality constraints.

Why this answer

The 'Accepting a work package' activity in Managing Product Delivery ensures that the Team Manager fully understands the Work Package — its products, scope, constraints, and tolerances — and formally commits to delivering it. This agreement is the basis for the Team Manager's subsequent reporting and the Project Manager's control.

Exam trap

The trap here is confusing the 'Accepting a Work Package' activity with stage authorization or project closure — candidates often mix up the responsibilities of the Team Manager and the Project Board.

How to eliminate wrong answers

Option A is wrong because the Team Manager reports to the Project Manager, not directly to the Executive; bypassing the Project Manager breaks the management hierarchy. Option B is wrong because authorizing a new stage is the responsibility of the Project Board via the 'Authorizing a Stage' activity in the Directing a Project process, not the Team Manager. Option C is wrong because closing the project and handing over products occurs in the Closing a Project process, not in Managing Product Delivery.

Full explanation →

124

MCQmedium

A PRINCE2 project is implementing a sustainable manufacturing plant. The Project Manager needs to ensure that the project's progress tracking mechanisms include metrics for both financial expenditure and environmental resource consumption. How should the Progress practice be tailored?

A.Exempt the project from progress reporting because sustainability cannot be measured.

B.Delegate all progress monitoring to the Senior Supplier.

C.Replace Highlight Reports with the Risk Register.

D.Tailor Highlight Reports and dashboards to include sustainability and ESG resource consumption metrics alongside financial metrics.

AnswerD

Tailoring Highlight Reports and dashboards to include ESG resource consumption metrics alongside financial data satisfies the stem's constraint that progress tracking covers both expenditure and environmental consumption, embedding sustainability into the Progress practice's reporting mechanisms.

Why this answer

Tailoring Highlight Reports and dashboards to include sustainability and ESG resource consumption metrics alongside financial metrics is the correct approach because the Progress practice should be adapted to the project's context. This ensures that progress tracking reflects both financial and environmental performance, aligning with the project's sustainability objectives.

Exam trap

PRINCE2-PRACTITIONER often tests the idea that tailoring means adapting, not abandoning, practices; candidates may think that sustainability cannot be measured or that progress reporting should be removed, but the correct answer is to tailor the reports to include relevant metrics.

How to eliminate wrong answers

Option A is wrong because exempting the project from progress reporting is not acceptable; sustainability can be measured through metrics like carbon footprint, energy usage, and waste reduction. Option B is wrong because delegating all progress monitoring to the Senior Supplier abdicates the Project Manager's responsibility and ignores broader progress aspects. Option C is wrong because replacing Highlight Reports with the Risk Register is inappropriate; the Risk Register is for risks, not progress reporting, and Highlight Reports are a key progress tool.

Full explanation →

125

MCQmedium

A Project Manager is executing the Starting up a Project process. They need to appoint the management team for the initiation stage. Who formally appoints the Project Manager for this process?

A.Corporate or Program Management

B.The Executive

C.Project Assurance

D.Lead Team Manager

AnswerA

During Starting up a Project, the Project Manager is appointed by corporate or programme management, since that layer owns the mandate and authorises the project's initiation. The Project Board itself is only appointed later, at the first Initiating a Project activity.

Why this answer

In PRINCE2, corporate or programme management appoints the Project Manager during the Starting up a Project process. The Executive is appointed first (also by corporate/programme management), and the Executive then appoints the other project management team roles such as the Senior User(s) and Senior Supplier(s). The Project Manager is therefore appointed by corporate or programme management, not by the Executive, Project Assurance, or a Team Manager.

Exam trap

PRINCE2-Practitioner often tests the distinction between who appoints the Executive (corporate/programme management) and who appoints the Project Manager (also corporate/programme management), versus who appoints the Senior Users and Senior Suppliers (the Executive) — candidates frequently assume the Executive appoints everyone.

How to eliminate wrong answers

Option B is wrong because the Executive appoints the Senior Users and Senior Suppliers, and may be involved in selecting the Project Manager, but the formal appointment of the Project Manager during SU is made by corporate or programme management. Option C is wrong because Project Assurance is a monitoring role that provides independent oversight on behalf of the Project Board — it does not appoint anyone. Option D is wrong because the Lead Team Manager is a delivery role appointed later (often during Initiating a Project or stage planning), and has no authority to appoint the Project Manager.

Full explanation →

126

MCQmedium

A PRINCE2 project is subject to strict environmental regulations. The Quality Manager wants to ensure that all deliverables undergo regulatory compliance testing before being presented to the user. Where should these regulatory testing requirements be documented?

A.The Daily Log

B.The Communication Management Approach

C.The Risk Register

D.The individual Product Descriptions' quality criteria section

AnswerD

Quality criteria sit within each Product Description, so embedding regulatory compliance testing there binds the requirement to the specific deliverable. This satisfies the Quality Manager's need for mandatory testing before user presentation, since quality review methods and criteria are defined per product.

Why this answer

In PRINCE2, quality criteria for each product are documented in the Product Description, which includes the quality specifications, quality methods, and quality responsibilities. Regulatory compliance testing is a quality criterion that must be met before the product is accepted. Therefore, these requirements belong in the individual Product Descriptions' quality criteria section.

Exam trap

The trap is assuming that quality requirements belong in a centralized document like the Quality Register or Communication Management Approach, but PRINCE2 specifically places product-specific quality criteria in the Product Description.

How to eliminate wrong answers

Option A is wrong because the Daily Log is a personal journal for the Project Manager to record informal notes, actions, and events; it is not a formal repository for quality requirements. Option B is wrong because the Communication Management Approach defines how information will be exchanged, not the quality criteria for products. Option C is wrong because the Risk Register records risks and responses, not quality testing requirements.

Full explanation →

127

MCQhard

A PRINCE2 7 project is nearing the end of a stage, and the Project Manager is preparing for the 'Managing a Stage Boundary' process. The Project Manager wants to ensure that the team's performance and well-being are considered in the End Stage Report. Which statement best reflects how PRINCE2 7 addresses the 'People' aspect in this context?

A.The Project Manager should review team performance and well-being as part of the stage boundary, and include any significant issues or lessons in the End Stage Report to inform the next stage.

B.The 'People' aspect is only relevant during the 'Initiating a Project' process when the team is first formed, and should not be revisited in later stage boundaries.

C.The End Stage Report should focus exclusively on product delivery and business case viability, as people-related matters are outside the scope of PRINCE2.

D.The 'People' aspect is managed separately by the Project Board, so the Project Manager does not need to include team performance in the End Stage Report.

AnswerA

PRINCE2 7 integrates the 'People' aspect into all processes, including 'Managing a Stage Boundary'. The End Stage Report is an opportunity to reflect on team performance, morale, and any people-related issues that may affect the next stage. By including these in the report, the Project Manager provides the project board with a holistic view and can propose actions to address any concerns, ensuring the team is set up for success in the next stage.

Why this answer

The 'People' aspect in PRINCE2 7 is not confined to a single process; it is a continuous consideration. During 'Managing a Stage Boundary', the Project Manager should assess team performance and well-being, and reflect this in the End Stage Report. This ensures that the project board is aware of any people-related risks or issues that could affect the next stage.

It also aligns with the principles of 'Learn from experience' and 'Tailor to suit the project environment' by adapting to the team's current state.

Exam trap

The trap here is believing that the 'People' aspect is only relevant during team formation or initiation, when PRINCE2 7 expects it to be managed continuously, including at stage boundaries.

Full explanation →

128

MCQeasy

What is the primary output of the Initiating a Project (IP) process?

A.End Project Report

B.Project Initiation Documentation (PID)

C.Work Package Description

D.Project Brief

AnswerB

The PID consolidates the business case, project plan, risk and quality approaches, and controls into a single baseline. It satisfies the stem's requirement for the primary output by providing the documented foundation the Project Board authorises, enabling the project to proceed to the next stage boundary.

Why this answer

The primary output of the Initiating a Project (IP) process is the Project Initiation Documentation (PID). The PID consolidates the Business Case, project plan, strategies, controls, and other key documents, and is used to gain Project Board authorization to proceed. It is the baseline against which the project's progress and viability are assessed.

Exam trap

PRINCE2-Practitioner often confuses outputs of different processes, especially the Project Brief (SU) versus PID (IP), and candidates may pick the Project Brief as the output of IP.

How to eliminate wrong answers

Option A is wrong because the End Project Report is produced during Closing a Project, not IP. Option C is wrong because Work Package Descriptions are created during Controlling a Stage when work is delegated. Option D is wrong because the Project Brief is an input to IP, produced during Starting up a Project, not its output.

Full explanation →

129

MCQeasy

In the PRINCE2 Business Case practice, what term describes the measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders?

A.Tolerance

B.Benefit

C.Risk threshold

D.Output

AnswerB

A benefit is the measurable improvement resulting from an outcome that stakeholders perceive as an advantage, matching the stem's definition precisely. Benefits are expressed in the Business Case with measures, owners and expected timing, and are later reviewed against the benefits management approach.

Why this answer

In PRINCE2 7, a benefit is defined as the measurable improvement resulting from an outcome that is perceived as an advantage by one or more stakeholders. Benefits are documented in the Business Case (benefits management approach, benefit profiles) and are distinct from outputs (the products delivered) and outcomes (the resulting change in business operations). The measurable, stakeholder-perceived advantage is the defining characteristic.

Exam trap

The trap is conflating outputs with benefits: candidates pick 'Output' because the project delivers products, but PRINCE2-PRACTITIONER expects you to recognize that a benefit is the measurable, stakeholder-perceived improvement, not the deliverable itself.

How to eliminate wrong answers

Option A is wrong because tolerance is the permissible deviation from a plan (time, cost, scope, quality, risk, benefit) allowed without escalating to the next management level — it is a control parameter, not an improvement. Option C is wrong because a risk threshold is the level of risk appetite or exposure that triggers a response; it is not a benefit. Option D is wrong because an output is the tangible product or deliverable produced by the project (e.g., a new CRM system), whereas a benefit is the measurable improvement that output enables (e.g., 15% faster customer onboarding).

Full explanation →

130

MCQhard

During the Closing a Project process, the Project Manager is preparing the End Project Report. Which of the following should be included as a specific section in this report?

A.A copy of the project's risk register with all risks closed.

B.A detailed financial audit of all project expenditures.

C.An evaluation of the project's performance against its original Project Plan.

D.A list of all project team members and their individual performance ratings.

AnswerC

The End Project Report includes an evaluation of the project's overall performance against the Project Plan, covering scope, schedule, cost, and quality. This helps the Project Board assess whether the project delivered what was intended and provides lessons for future projects. It is a required section that summarises the project's achievements and deviations.

Why this answer

The End Project Report includes an evaluation of the project's performance against the Project Plan, covering aspects such as scope, schedule, cost, and quality. This evaluation is essential for the Project Board to assess the project's success and to capture lessons learned. Other items like financial audits or individual performance ratings are not part of this report, as they fall outside its purpose of providing a high-level project performance summary.

Exam trap

The trap here is thinking that the End Project Report contains detailed audits or personnel evaluations, when it actually focuses on project-level performance against the plan.

Full explanation →

131

MCQmedium

A PRINCE2 project is utilizing a stage-gate approach. At the end of Stage 2, the Project Board meets to review the End Stage Report and the updated Business Case before authorizing Stage 3. What PRINCE2 principle is primarily demonstrated by this activity?

A.Tailor to suit the project context

B.Manage by exception

C.Learn from experience

D.Manage by stages

AnswerD

Stage boundaries force the Project Board to review the End Stage Report and Business Case before committing further resources, so authority is granted one stage at a time. This directly satisfies the stem's stage-gate constraint, embodying the manage by stages principle.

Why this answer

The activity described — the Project Board reviewing the End Stage Report and updated Business Case at the end of Stage 2 before authorizing Stage 3 — is the direct embodiment of the 'Manage by Stages' principle. This principle requires the project to be planned, monitored, and controlled on a stage-by-stage basis, with a Project Board decision point (End Stage Assessment) at each boundary. It ensures the project remains viable and aligned with the Business Case before committing further resources.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between 'Manage by Stages' (the structural principle of stage boundaries and End Stage Assessments) and 'Manage by Exception' (the tolerance-based delegation principle), causing candidates to select the latter when a stage-gate review is described.

How to eliminate wrong answers

Option A is wrong because tailoring concerns adapting PRINCE2 to the project's size, complexity, and environment — it is not the principle demonstrated by a stage-gate review. Option B is wrong because 'Manage by exception' refers to delegating authority with defined tolerances so the Project Board only intervenes when tolerances are forecast to be breached; the stage-gate review is a planned control point, not an exception-driven escalation. Option C is wrong because 'Learn from experience' involves capturing and applying lessons throughout the project; while lessons may be discussed at a stage boundary, the core activity here is the stage-gate authorization itself.

Full explanation →

132

MCQhard

An enterprise project is facing deep-seated cultural resistance from end-users who fear automation will replace their jobs. The Project Manager is applying PRINCE2 7 change management guidance. Which action represents the most effective engagement strategy?

A.Conceal the automation plans until the final week before go-live to prevent early complaints.

B.Engage users transparently through workshops, addressing job security concerns, and co-designing training and transition pathways.

C.Replace all resistant staff members immediately before starting the project.

D.Dismiss the users' fears as groundless and proceed with the technical rollout without consultation.

AnswerB

Transparent workshops with co-designed training directly address the cultural resistance constraint by tackling job-security fears rather than ignoring them. This engagement approach builds ownership and reduces the resistance that purely procedural change controls would fail to resolve.

Why this answer

PRINCE2 7's people and change management guidance emphasises early, transparent engagement, addressing concerns openly, and involving affected users in designing the transition. Option B does exactly this by running workshops, tackling job-security fears, and co-designing training and transition pathways, which builds ownership and reduces resistance. This aligns with the 'tailor to the environment' and 'people' principles rather than imposing change top-down.

Exam trap

PRINCE2-Practitioner often tests the misconception that resistance should be managed by authority or concealment, when the correct answer is always transparent, early and inclusive engagement.

How to eliminate wrong answers

Option A is wrong because concealing plans until go-live maximises resistance and destroys trust, directly contradicting PRINCE2's emphasis on early stakeholder engagement. Option C is wrong because replacing resistant staff is coercive, damages morale and knowledge retention, and is not a recognised PRINCE2 engagement strategy. Option D is wrong because dismissing fears as groundless ignores legitimate stakeholder concerns and violates the 'learn from experience' and 'people' principles, guaranteeing active or passive resistance.

Full explanation →

133

Multi-Selectmedium

Which TWO of the following statements correctly describe the purpose and content of the Benefits Management Approach?

Select 2 answers

A.It serves as the formal register for logging project risks.

B.It details the daily work package schedules for team members.

C.It defines how and when the projected benefits of the project will be measured.

D.It includes post-project benefit reviews to ensure long-term value realization.

E.It replaces the Business Case once the project enters initiation.

AnswersC, D

The Benefits Management Approach specifies the measurements, timing and responsibilities for tracking projected benefits, defining how and when each will be measured against the Business Case. This satisfies the stem's requirement for describing measurement arrangements.

Why this answer

Option C is correct because the Benefits Management Approach in PRINCE2 defines the activities, responsibilities, and timing for measuring and verifying that the project's projected benefits are actually realized, specifying the metrics and methods to be used. Option D is correct because it explicitly includes post-project benefit reviews, which are scheduled after the project closes to confirm that the anticipated benefits (and any residual benefits) are being achieved and to enable corrective action if they are not. Option A is wrong because risk logging is handled by the Risk Register, not the Benefits Management Approach.

Option B is wrong because daily work package schedules belong to team plans and Work Packages, not to benefits management. Option E is wrong because the Business Case remains the document justifying the project and is updated throughout, not replaced by the Benefits Management Approach.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the Benefits Management Approach and other documents like the Risk Register or Business Case, leading candidates to select options that describe other artifacts.

Full explanation →

134

MCQhard

A multinational PRINCE2 project spans diverse geographical locations and cultures. The Project Manager notices misunderstandings and friction arising from differing communication norms across regions. How should the Project Manager adapt their leadership and communication approach?

A.Impose a single rigid communication style based solely on the Project Manager's home culture.

B.Abandon all structured communication and rely exclusively on unstructured local chats.

C.Establish cultural awareness, adapt communication channels and styles to suit regional contexts, and agree on shared team norms.

D.Outsource all international stakeholder interactions to external consultants without oversight.

AnswerC

Adapting channels and styles to regional contexts directly addresses the cross-cultural communication norms causing friction, while agreeing shared team norms gives the multinational team a common baseline. This satisfies the PRINCE2 principle of tailoring leadership to the project's geographical and cultural environment, resolving misunderstandings rather than imposing one region's conventions.

Why this answer

PRINCE2 7's people principles require the Project Manager to build cultural awareness, adapt communication channels and styles to regional contexts, and agree shared team norms so that diverse teams can collaborate effectively. Option C captures this adaptive, inclusive approach. It respects local norms while maintaining enough structure for the project to function.

Exam trap

PRINCE2-Practitioner often tests the misconception that one communication style fits all cultures, when the correct approach is adaptive, culturally aware communication with agreed shared norms.

How to eliminate wrong answers

Option A is wrong because imposing a single rigid home-culture communication style ignores cultural differences and will alienate international stakeholders. Option B is wrong because abandoning structured communication for unstructured local chats removes the governance and reporting that PRINCE2 requires. Option D is wrong because outsourcing all international stakeholder interactions without oversight abdicates the Project Manager's responsibility for stakeholder engagement and communication.

Full explanation →

135

MCQeasy

A project is initiated to build a new corporate headquarters. During project preparation, the executive team establishes that the project must deliver a positive return on investment within three years. Which PRINCE2 principle underpins this requirement?

A.Manage by stages

B.Continued business justification

C.Defined roles and responsibilities

D.Focus on products

AnswerB

Continued business justification requires a justifiable reason to start and continue the project, expressed through the business case. The three-year positive return on investment is that justification, so this principle underpins the executive's requirement and mandates ongoing viability review.

Why this answer

The requirement that the project must deliver a positive return on investment within three years is a statement of business justification — the 'why' behind the project. The PRINCE2 principle 'Continued business justification' requires that a project has a justifiable business case at initiation and that this justification is reviewed and remains valid throughout the project lifecycle. ROI is a core component of the Business Case, so this principle directly underpins the requirement.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between principles that sound similar — candidates may confuse 'Continued business justification' with 'Manage by exception' when financial thresholds are mentioned, but ROI is fundamentally about the Business Case, not tolerance delegation.

How to eliminate wrong answers

Option A is wrong because 'Manage by stages' is about dividing the project into manageable stages with decision points, not about financial justification. Option C is wrong because 'Defined roles and responsibilities' concerns the organizational structure and accountability (e.g., Executive, Senior User, Senior Supplier), not ROI. Option D is wrong because 'Focus on products' is about defining and delivering products that meet quality criteria, not about the financial rationale for the project.

Full explanation →

136

MCQmedium

During the Initiating a Project (IP) process, the Project Manager needs to establish the project's schedule and resource requirements. Where should these be compiled?

A.In the Highlight Report

B.In the Project Management Plan

C.In the Project Brief

D.In the End Project Report

AnswerB

The Project Management Plan is the single document that collates the project's schedule and resource requirements during Initiating a Project, satisfying the stem's constraint that these be compiled together. PRINCE2 treats it as the overarching plan containing the subsidiary schedule and resource components, so both are captured within it.

Why this answer

During the Initiating a Project (IP) process, the Project Manager compiles the project's schedule and resource requirements into the Project Management Plan. This plan integrates all subsidiary plans, including the schedule and resource management, and is approved by the Project Board before the project proceeds.

Exam trap

PRINCE2-Practitioner often tests the confusion between documents created in different processes, and candidates may incorrectly associate the Project Brief (an input) with the output of IP.

How to eliminate wrong answers

Option A is wrong because the Highlight Report is used during stage execution to report progress to the Project Board, not to establish initial plans. Option C is wrong because the Project Brief is a pre-project document that outlines the project's foundation and is an input to IP, not an output. Option D is wrong because the End Project Report is created during Closing a Project to evaluate performance, not to plan.

Full explanation →

137

MCQhard

A project manager is configuring the Progress practice for a high-risk project. The Project Board wants to ensure that management by exception is fully operational. Which parameter must be explicitly agreed upon between the Project Board and Corporate Management to establish the Project Board's authority?

A.Daily task schedules

B.Project-level tolerances

C.Team-level work package tolerances

D.Individual team member KPIs

AnswerB

Project-level tolerances define the delegated authority the Project Board holds from Corporate Management, so management by exception can operate. Without these agreed limits, the Board cannot approve stage tolerances or escalate breaches correctly, undermining the high-risk project's governance.

Why this answer

Project-level tolerances define the delegated authority boundaries the Project Board agrees with Corporate/Programme Management, enabling management by exception at the board level. Once set, the Board can allow the project to proceed without escalation as long as forecast remains within these six tolerance areas (time, cost, scope, quality, risk, benefit). This is the parameter that establishes the Board's own authority to direct the project without constant upward referral.

Exam trap

PRINCE2-Practitioner often tests the confusion between project-level tolerances (Board ↔ Corporate) and stage/work-package tolerances (Board ↔ PM, PM ↔ Team Manager), so candidates pick the wrong delegation layer.

How to eliminate wrong answers

Option A is wrong because daily task schedules are operational planning artefacts, not governance authority parameters, and PRINCE2 does not mandate daily schedules. Option C is wrong because team-level work package tolerances are agreed between the Project Manager and Team Manager, not between the Project Board and Corporate Management. Option D is wrong because individual team member KPIs are performance metrics, not a PRINCE2 tolerance construct, and they do not establish board-level authority.

Full explanation →

138

Multi-Selectmedium

During the Starting up a Project process, the Project Manager must design and appoint the project management team. Which TWO roles must be defined and filled during this process?

Select 2 answers

A.The Executive

B.Independent external auditors

C.Corporate Change Champions

D.The Project Manager

E.Specialist Team Managers for all delivery stages

AnswersA, D

The Executive is appointed during Starting up a Project, owning the business case and ensuring the project delivers value. This satisfies the stem's requirement for a role defined and filled in that process, alongside the Project Manager, before the project board is fully established.

Why this answer

In PRINCE2, the Starting up a Project (SU) process requires the Project Manager to design and appoint the project management team, and the two roles that must be defined and filled at this point are the Executive (A) and the Project Manager (D). The Executive (A) is essential because this role owns the Business Case and represents the business interest on the Project Board, and the project cannot be properly initiated without this appointment. The Project Manager (D) must also be appointed during SU because this person is responsible for carrying out the activities of Starting up a Project and preparing the Project Initiation Documentation.

Independent external auditors (B) are not part of the PRINCE2 project management team structure and are typically engaged separately for assurance or audit purposes. Corporate Change Champions (C) are not a defined PRINCE2 role and are not required during Starting up a Project. Specialist Team Managers for all delivery stages (E) are appointed later, during the Initiating a Project or Managing a Stage Boundary activities, and only for stages where specialists are needed, so they are not mandatory at SU.

Exam trap

PRINCE2-Practitioner often tests the timing of role appointments, causing candidates to select roles like Senior User or Senior Supplier that are appointed later in Initiating a Project, or to confuse Project Assurance with external audit.

Full explanation →

139

MCQmedium

A project is in the Starting up a Project process (SU). The Executive wants to know how long SU should take and what its primary output is. Which statement is correct?

A.SU is executed by the Project Board to write the detailed Project Plan.

B.SU lasts for the duration of the first delivery stage and delivers the final product.

C.SU is a pre-project process whose main output is the Project Brief and the Initiation Stage Plan.

D.SU replaces the Initiating a Project process for small projects.

AnswerC

SU is a pre-project process, running before the Initiation Stage, and its principal output is the Project Brief, supported by the Initiation Stage Plan. This directly answers the Executive's question about duration and primary output.

Why this answer

Starting up a Project (SU) is a pre-project process that occurs before the project is formally initiated. Its primary outputs are the Project Brief and the Initiation Stage Plan, which together provide the basis for the Project Board to authorize the Initiation Stage. SU is not a delivery stage and does not produce the final product.

Exam trap

PRINCE2-Practitioner often tests whether candidates know that SU is a pre-project process with specific outputs (Project Brief and Initiation Stage Plan) — the trap is confusing SU with Initiating a Project or with a delivery stage.

How to eliminate wrong answers

Option A is wrong because SU is not executed by the Project Board — the Project Board authorizes the project, but SU is performed by the Project Manager and the project team, and it does not produce a detailed Project Plan (that is done in Initiating a Project). Option B is wrong because SU is a pre-project process, not a delivery stage, and it does not deliver the final product. Option D is wrong because SU does not replace Initiating a Project — both processes exist, and Initiating a Project is still required to develop the PID and authorize the project.

Full explanation →

140

MCQmedium

In the Controlling a Stage (CS) process, how does the Project Manager handle ad-hoc requests for change originating from stakeholders?

A.Capture the request in the Issue Register, assess its impact, and process it according to the Change Control Approach.

B.Reject all change requests automatically to prevent scope creep.

C.Implement the change immediately to satisfy the stakeholder without logging it.

D.Forward the change request directly to the Team Manager with instructions to build it without approval.

AnswerA

Ad-hoc change requests are treated as issues, so capturing them in the Issue Register and applying the Change Control Approach's impact assessment and approval route satisfies the CS process's requirement to control changes within the stage boundary.

Why this answer

In the Controlling a Stage process, ad-hoc change requests from stakeholders are captured in the Issue Register, assessed for impact, and processed according to the Change Control Approach. This ensures that changes are evaluated and approved before implementation, maintaining control over scope and other project aspects.

Exam trap

PRINCE2-Practitioner often tests the change control process by presenting options that bypass assessment or approval, so candidates must remember that all change requests must be logged, assessed, and processed according to the Change Control Approach.

How to eliminate wrong answers

Option B is wrong because automatically rejecting all changes is not aligned with PRINCE2; changes should be assessed on their merits. Option C is wrong because implementing changes immediately without logging or approval bypasses change control and can lead to scope creep and loss of control. Option D is wrong because forwarding a change request directly to the Team Manager without assessment and approval violates the change control process.

Full explanation →

141

MCQeasy

Which PRINCE2 process ensures that project closure is orderly and controlled, preventing lingering unfinished work?

A.Starting up a Project

B.Closing a Project

C.Managing a Stage Boundary

D.Controlling a Stage

AnswerB

Closing a Project provides the controlled shutdown the stem demands: it verifies the project has delivered its products, obtains acceptance, reviews benefits and lessons, and confirms no work remains outstanding before disbanding the team. This orderly, authorised closure prevents the lingering unfinished work the question asks about.

Why this answer

Closing a Project (CP) is the process designed to ensure that the project closes in an orderly and controlled manner, confirming acceptance of the project's products, evaluating the project, and ensuring no unfinished work lingers. It addresses the 'continued business justification' principle by formally confirming that the project has delivered what it set out to deliver (or documenting why not). CP is triggered by the 'Authorize project closure' activity in Directing a Project and produces the End Project Report and Lessons Report.

Exam trap

PRINCE2-Practitioner often tests the distinction between Managing a Stage Boundary (end of intermediate stages) and Closing a Project (end of the final stage or premature termination), catching candidates who assume stage-boundary activities also close the project.

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 appoints the project management team — it has nothing to do with closure. Option C is wrong because Managing a Stage Boundary is used at the end of each delivery stage (except the final one) to plan the next stage and update the Business Case; it is not the process that closes the overall project. Option D is wrong because Controlling a Stage is the day-to-day delivery-control process used by the Project Manager during a stage, not the closure process.

Full explanation →

142

MCQhard

A project is in the Closing a Project (CP) process. The Project Board is evaluating whether to authorize closure. Which of the following conditions must be met for the Project Board to authorize project closure?

A.The Project Manager has received a performance bonus from the Senior Supplier.

B.All risks in the risk log have been completely eliminated with zero residual risk.

C.Project objectives have been achieved, products handed over, and follow-on action recommendations documented.

D.All benefits have been fully realized and measured in the operational environment.

AnswerC

Authorising closure requires that project objectives are achieved, products are handed over, and follow-on action recommendations are documented. These conditions satisfy the stem's criteria for the Project Board to approve closure during the Closing a Project process.

Why this answer

For the Project Board to authorize project closure in PRINCE2, the project must have achieved its objectives (as defined in the Project Initiation Documentation), the products must have been handed over to the appropriate operational and maintenance environment, and follow-on action recommendations must be documented. These conditions ensure that the project has delivered what it set out to do and that any remaining actions are captured for the future.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between project outputs and outcomes, leading candidates to believe that benefits must be fully realized before closure, when in fact benefits are typically realized post-project.

How to eliminate wrong answers

Option A is wrong because a performance bonus is not a PRINCE2 condition for closure; it is irrelevant to the project's completion criteria. Option B is wrong because risks do not need to be completely eliminated; residual risks are acceptable and should be documented in the Risk Register and passed on. Option D is wrong because benefits are often realized after the project closes; the project only needs to demonstrate that the products are capable of delivering the benefits, not that they have been fully realized and measured.

Full explanation →

143

MCQhard

During risk identification in a PRINCE2 project, the team identifies a risk where a key supplier might fail to meet sustainability targets, leading to reputational damage. The team decides to establish joint monitoring committees and share best practices with the supplier to help them succeed. Which risk response category is this?

A.Transfer

B.Mitigate

C.Exploit

D.Avoid

AnswerB

Mitigate reduces probability or impact of the supplier risk. Joint monitoring committees and shared best practices lower the likelihood of missed sustainability targets, cutting reputational damage exposure. This proactive supplier collaboration is mitigation, not avoidance, transfer or acceptance.

Why this answer

Mitigate is the PRINCE2 risk response that reduces the probability and/or impact of a threat. Here the team is actively working with the supplier — establishing joint monitoring committees and sharing best practices — to lower the likelihood that the supplier fails to meet sustainability targets. This proactive reduction of the threat's likelihood is the defining characteristic of mitigation.

Exam trap

PRINCE2-Practitioner often tests the distinction between Mitigate and Transfer, so the trap is picking Transfer whenever a third party (supplier) is involved, even though the team is actively reducing the risk rather than shifting its financial impact.

How to eliminate wrong answers

Option A is wrong because Transfer involves shifting the financial impact of a risk to a third party, typically through insurance or contractual arrangements, which is not what joint monitoring committees do. Option C is wrong because Exploit is a response for opportunities (positive risks), not threats, and it aims to ensure the opportunity is realized. Option D is wrong because Avoid involves changing the project scope or approach to eliminate the risk entirely, whereas here the team is retaining the risk but reducing its likelihood.

Full explanation →

144

MCQhard

A project is undergoing the Closing a Project process. The Project Board requests confirmation that all project benefits have been fully realized before giving final approval to close. According to PRINCE2, why is this request problematic at this exact moment?

A.Benefits are managed exclusively by Team Managers during Managing Product Delivery.

B.The Project Board has no authority to review benefits.

C.Benefits realization reviews occur post-project and cannot be completed during the Closing a Project process.

D.The Project Manager is prohibited from measuring benefits.

AnswerC

Benefits realization reviews are scheduled after the project closes, once the products have been in operational use long enough to generate measurable outcomes. The Closing a Project process can only assess whether benefits are forecast, not realised, so the Board's request cannot be satisfied at this point.

Why this answer

In PRINCE2, the Closing a Project process focuses on verifying that the project has delivered its products and that the original justification (Business Case) remains valid, but it does not wait for benefits to be fully realized. Benefits typically accrue after the project has closed, during the post-project period, and are reviewed as part of a benefits realization plan. Therefore, requesting confirmation of fully realized benefits at the point of closing is problematic because such confirmation cannot be completed within the Closing a Project process—it is a post-project activity.

Exam trap

PRINCE2-Practitioner often tests the misconception that all benefits must be realized before a project can close, confusing project closure with benefits realization, which typically occurs post-project.

How to eliminate wrong answers

Option A is wrong because benefits management is not exclusively a Team Manager responsibility; in PRINCE2, the Project Manager and Project Board (especially the Business Executive) are involved in benefits management, and Team Managers focus on delivering products. Option B is wrong because the Project Board has clear authority and responsibility to review benefits as part of their role in ensuring the project remains aligned with the Business Case. Option D is wrong because the Project Manager is not prohibited from measuring benefits; they are actively involved in benefits management, including defining and monitoring benefits in the Business Case and Benefits Management Approach.

Full explanation →

145

MCQeasy

Which document is created during the Initiating a Project process to define the mechanisms for measuring whether the project's expected outcomes have been achieved post-project?

A.Benefits Management Approach

B.Project Brief

C.Stage Plan

D.End Project Report

AnswerA

The Benefits Management Approach defines how the project's expected benefits and outcomes will be measured, reviewed, and realised after the project closes. It is produced during Initiating a Project, satisfying the requirement for post-project measurement mechanisms rather than in-project controls.

Why this answer

The Benefits Management Approach is the PRINCE2 document created during the Initiating a Project process that defines how the project's expected benefits will be measured, reviewed, and realized after the project closes. It specifies the mechanisms, roles, timing, and criteria for post-project benefit reviews, ensuring the Business Case's promised outcomes can be verified. It is a key output of the 'Prepare the Benefits Management Approach' activity within Initiating a Project.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between documents that report on benefits (End Project Report, Business Case) and the document that defines how benefits will be measured post-project (Benefits Management Approach).

How to eliminate wrong answers

Option B is wrong because the Project Brief is a pre-project document created during Starting up a Project; it outlines the project's foundation but does not define post-project benefit measurement mechanisms. Option C is wrong because a Stage Plan covers the detailed planning of a single management stage's products, activities, and resources — it is not concerned with post-project benefit realization. Option D is wrong because the End Project Report is produced at the end of the project (Closing a Project) to evaluate performance against the Project Initiation Documentation; it reports on benefits but does not define the measurement mechanisms.

Full explanation →

146

MCQeasy

In the PRINCE2 Organizing practice, what is the purpose of the Project Brief?

A.To record final lessons learned at project closure.

B.To provide a solid foundation and overview of the project during initiation before the PID is produced.

C.To schedule team work packages.

D.To provide a full, detailed baseline for project execution throughout all stages.

AnswerB

The Project Brief provides a foundation and overview during initiation, capturing the project's purpose, scope and justification before the PID is produced. It satisfies the stem's constraint of establishing a solid basis prior to detailed planning.

Why this answer

The Project Brief is used during the Initiating a Project process to provide a solid foundation and overview of the project before the Project Initiation Documentation (PID) is produced. It captures the project's purpose, objectives, scope, and justification, and is used to gain approval to proceed with initiation.

Exam trap

Candidates often confuse the Project Brief with the PID. The trap is selecting an option that describes the PID's purpose (full detailed baseline) instead of the Project Brief's purpose (foundation during initiation).

How to eliminate wrong answers

Option A is wrong because lessons learned at project closure are recorded in the Lessons Log or End Project Report, not the Project Brief. Option C is wrong because scheduling team work packages is part of managing product delivery, not the purpose of the Project Brief. Option D is wrong because the full detailed baseline for execution is the PID, not the Project Brief.

Full explanation →

147

MCQhard

During a project stage, a major regulatory change occurs that mandates an immediate alteration to the project's design standards to meet new environmental laws (ESG). The Project Manager assesses that this will breach cost and time stage tolerances. What should the Project Manager do?

A.Stop the project immediately without notifying the Project Board.

B.Ignore the regulatory change if it was not in the original Business Case.

C.Absorb the cost by reducing testing quality.

D.Raise an Exception Report and prepare an Exception Plan for the Project Board.

AnswerD

Breaching stage tolerances removes the Project Manager's delegated authority, so the deviation must be escalated. An Exception Report informs the Project Board of the regulatory change and forecast breach, while the Exception Plan proposes recovery options for their decision.

Why this answer

When a major regulatory change threatens to breach stage tolerances, the Project Manager must escalate by raising an Exception Report to the Project Board and preparing an Exception Plan. The Exception Report describes the deviation, and the Exception Plan proposes how to recover or adjust. The Project Board then decides whether to approve the Exception Plan or take other action.

Exam trap

PRINCE2-PRACTITIONER often tests tolerance escalation; the trap is choosing to absorb or ignore the impact instead of raising an Exception Report and preparing an Exception Plan for the Project Board.

How to eliminate wrong answers

Option A is wrong because stopping the project without notifying the Project Board bypasses governance and the Board's authority. Option B is wrong because ignoring a regulatory change is unacceptable and could have legal consequences; the Business Case must be updated. Option C is wrong because absorbing cost by reducing testing quality compromises the project's quality criteria and is not a valid response.

Full explanation →

148

MCQhard

An organization is applying PRINCE2 7 to a complex transformation program. The Executive realizes that the project's benefits realization schedule has drifted by 6 months due to operational delays in adopting the new systems. Who is accountable for ensuring that the Benefits Management Approach is executed post-project?

A.Project Assurance

B.The Project Manager

C.Corporate management and operational owners, as defined in the Benefits Management Approach

D.The Senior Supplier

AnswerC

Post-project benefit realisation sits outside the project's life, so accountability transfers to corporate management and the operational owners named in the Benefits Management Approach. This satisfies the stem's six-month drift, since only those owners can act once the project has closed.

Why this answer

In PRINCE2 7, the Benefits Management Approach defines how and by whom benefits will be measured and managed after the project closes. Accountability for executing this approach typically rests with corporate management and operational owners, as they are responsible for realising benefits in the business-as-usual environment. The Project Manager is only responsible for setting up the approach, not for post-project execution.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between project-level and post-project responsibilities; candidates may incorrectly assume the Project Manager remains accountable for benefits after the project, but the correct answer is corporate management and operational owners.

How to eliminate wrong answers

Option A is wrong because Project Assurance is responsible for monitoring the project's compliance with PRINCE2 and business case, not for executing post-project benefits management. Option B is wrong because the Project Manager's responsibility ends with the project; they may be involved in post-project benefits reviews but are not accountable for executing the Benefits Management Approach. Option D is wrong because the Senior Supplier represents the supplier interests and is not accountable for benefits realisation, which is a business responsibility.

Full explanation →

149

Multi-Selecthard

When integrating sustainability and ESG into the PRINCE2 Organizing and Plans practices, which TWO of the following practices must be tailored to ensure compliance?

Select 2 answers

A.Replacing the Project Board with external auditors.

B.Organizing practice, by incorporating ESG and sustainability expertise into governance structures and stakeholder roles.

C.Daily Log management, by recording employee vacation dates.

D.Eliminating all Stage Plans in favor of informal chats.

E.Plans practice, by incorporating environmental milestones and sustainability reviews into Product Descriptions and schedules.

AnswersB, E

Embedding ESG expertise into governance structures and stakeholder roles lets the project board and senior responsible owner obtain the sustainability competence needed to direct and authorise the work, satisfying the compliance requirement that accountability for ESG sits with defined roles rather than being delegated informally.

Why this answer

Option B is correct because the Organizing practice defines the project's governance structure, roles, and responsibilities, so embedding ESG and sustainability expertise into the Project Board, Project Manager, Team Manager, and stakeholder roles ensures that sustainability accountability and decision-making authority are properly established for compliance. Option E is correct because the Plans practice governs the production of the Project Plan, Stage Plans, and Team Plans, so environmental milestones and sustainability reviews must be built into Product Descriptions, product breakdown structures, and schedules to make ESG commitments measurable and auditable. Option A is wrong because replacing the Project Board with external auditors destroys the PRINCE2 accountability model (Business, User, and Supplier interests) rather than tailoring it.

Option C is wrong because the Daily Log records day-to-day events, actions, and risks, not employee vacation dates, and it is not a governance vehicle for ESG compliance. Option D is wrong because eliminating Stage Plans removes the management-stage boundary and tolerance controls that PRINCE2 requires for effective governance and compliance.

Exam trap

PRINCE2-Practitioner often tests tailoring by presenting extreme or irrelevant options, so candidates must identify which practices logically require adaptation to meet specific compliance needs like ESG.

Full explanation →

150

MCQhard

An R&D project has high uncertainty regarding whether the final technology can be successfully developed. To mitigate risk, the Project Manager recommends dividing the project into very short, high-frequency stages with explicit go/no-go decision gates. Which PRINCE2 principle is being leveraged most directly to control this uncertainty?

A.Manage by exception

B.Manage by stages

C.Continued business justification

D.Tailor to suit the project

AnswerB

Manage by stages divides the work into discrete management stages, each authorised by the project board and closed before the next begins. Very short stages with go/no-go gates let the board stop funding if the technology proves unviable, directly controlling uncertainty.

Why this answer

Manage by stages is the principle that requires the project to be planned, monitored, and controlled on a stage-by-stage basis, with a Project Board decision (go/no-go) at each stage boundary. Dividing an uncertain R&D project into short, high-frequency stages with explicit decision gates is the textbook application of this principle to control uncertainty. It allows the project to be stopped or redirected at each boundary based on the latest viability assessment.

Exam trap

PRINCE2-Practitioner often tests the overlap between Manage by stages and Manage by exception — candidates pick Manage by exception because 'go/no-go decision gates' sound like escalation, but the principle that mandates staged control and decision boundaries is Manage by stages.

How to eliminate wrong answers

Option A is wrong because Manage by exception is about delegating tolerances and escalating only when forecasts breach them — it does not by itself create stage boundaries or go/no-go gates. Option C is wrong because Continued business justification is about whether the project remains viable, which is assessed at stage boundaries but is not the principle that prescribes the staged structure. Option D is wrong because Tailor to suit the project is about adapting the method to the project's context, not about the control mechanism of staged decision gates.

Full explanation →

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