Knowledge + Practice

PRINCE2 Foundation (PRINCE2F) — Questions 901–975

1189 questions total · 16pages · All types, answers revealed

Take a mock exam Exam hub

Page 13 of 16

901

MCQeasy

Which process is responsible for producing the Project Brief?

A.Directing a Project

B.Initiating a Project

C.Starting Up a Project

D.Controlling a Stage

AnswerC

Starting Up a Project produces the Project Brief as its primary output, alongside the daily log and outline business case. This process satisfies the stem's requirement by creating the brief before the project is formally initiated, ensuring the Project Board has sufficient information to authorise Initiation.

Why this answer

The Project Brief is produced during the Starting Up a Project process. This process ensures that the project has a viable business justification and that all necessary pre-project activities are completed before the project is formally initiated. The Project Brief is then used as input to the Initiating a Project process.

Exam trap

A common misconception in PRINCE2 is that the Project Brief is created during Initiating a Project, because candidates confuse the Project Brief with the more detailed Project Initiation Documentation that is produced later.

How to eliminate wrong answers

Option A is wrong because Directing a Project is the process that provides overall governance and decision-making for the project, but it does not produce the Project Brief; it approves or rejects it. Option B is wrong because Initiating a Project uses the Project Brief as input to develop the Project Initiation Documentation, but does not produce the Project Brief itself. Option D is wrong because Controlling a Stage focuses on day-to-day management of a stage after initiation, and has no role in producing the pre-initiation Project Brief.

Full explanation →

902

MCQhard

During a project, a key stakeholder raises a concern that the project scope has expanded significantly without formal approval. The project manager realizes that changes have been implemented informally. Which PRINCE2 principle has been violated?

A.Defined roles and responsibilities

B.Continued business justification

C.Manage by stages

D.Learn from experience

AnswerC

Changes must be managed within stage boundaries.

Why this answer

The scenario describes scope changes being implemented without formal approval, which violates the 'Manage by stages' principle. PRINCE2 requires that a project be planned, monitored, and controlled on a stage-by-stage basis, with each stage ending in a formal review and approval before proceeding. Implementing changes informally bypasses stage boundaries and the associated management controls, directly breaking this principle.

Exam trap

The trap here is that candidates confuse 'Manage by stages' with 'Defined roles and responsibilities' because they think the project manager should have formally approved the change, but the principle violated is specifically about stage-based control, not role definition.

How to eliminate wrong answers

Option A is wrong because 'Defined roles and responsibilities' focuses on clear assignment of project roles, not on the control of scope changes or stage boundaries. Option B is wrong because 'Continued business justification' ensures the project remains viable, but the issue here is about unauthorized scope changes, not a lack of business case validation. Option D is wrong because 'Learn from experience' involves capturing lessons throughout the project, but the core violation is the lack of formal stage-gate control over changes, not the failure to document lessons.

Full explanation →

903

MCQmedium

Which PRINCE2 management product is used to capture lessons throughout the project?

A.End Project Report

B.Quality Register

C.Lessons Log

D.Lessons Report

AnswerC

The Lessons Log is the PRINCE2 management product that records lessons as they arise throughout the project, rather than only at stage boundaries or closure. It satisfies the stem's requirement for continuous capture, feeding the Lessons Report at stage end.

Why this answer

The Lessons Log is the PRINCE2 management product specifically designed to capture lessons as they occur throughout the project lifecycle. It is a dynamic repository where the project team records both positive and negative experiences, ensuring that lessons are not lost and can be reviewed at key points, such as stage boundaries and project closure.

Exam trap

The trap here is that candidates often confuse the Lessons Log (the ongoing capture tool) with the Lessons Report (the formal summary), leading them to select the Lessons Report as the product used throughout the project.

How to eliminate wrong answers

Option A is wrong because the End Project Report is produced at project closure to summarize performance and provide a final assessment, not to capture lessons continuously during the project. Option B is wrong because the Quality Register records quality activities and results, such as inspections and audits, not lessons learned. Option D is wrong because the Lessons Report is a formal document created at the end of a stage or the project, summarizing key lessons from the Lessons Log, but it is not the product used for ongoing capture.

Full explanation →

904

MCQeasy

In PRINCE2, who is responsible for the Business Case?

A.The Senior Supplier

B.The Project Manager

C.The Senior User

D.The Executive

AnswerD

The Executive owns the Business Case in PRINCE2, as defined by the management-by-stage principle and the business justification theme. This satisfies the constraint that the Business Case must have a single, accountable owner who is ultimately responsible for ensuring the project remains viable and aligned with corporate objectives.

Why this answer

The Executive is the single individual responsible for the Business Case in PRINCE2. They own the project's justification and ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Business Case is the Executive's primary accountability, as defined in the PRINCE2 manual.

Exam trap

The trap here is that candidates often confuse the Project Manager's role in maintaining the Business Case with ownership, but PRINCE2 explicitly assigns accountability to the Executive, not the manager who writes or updates it.

How to eliminate wrong answers

Option A is wrong because the Senior Supplier represents the supplier's interests and is responsible for the quality of products, not the Business Case. Option B is wrong because the Project Manager manages the day-to-day creation and maintenance of the Business Case document but does not own it; accountability rests with the Executive. Option C is wrong because the Senior User represents the users' needs and is responsible for specifying benefits, but the overall Business Case ownership belongs to the Executive.

Full explanation →

905

MCQmedium

The Project Board is meeting to make decisions when the project is not meeting its tolerances. What type of meeting is this?

A.Stage boundary meeting

B.Monthly progress meeting

C.Daily stand-up meeting

D.Exception-driven meeting

AnswerD

Project Board meetings convened specifically because the project has breached or is forecast to breach tolerances are exception-driven, focused on corrective action. This matches the stem's trigger of tolerances not being met, rather than routine progress or ad-hoc direction meetings.

Why this answer

D is correct because when a project is forecast to exceed its tolerances, the Project Board must convene an Exception-driven meeting to assess the situation and decide on corrective action. This meeting is triggered by an Exception Report from the Project Manager, not by a scheduled management stage boundary or routine progress review.

Exam trap

The trap here is that candidates confuse an Exception-driven meeting with a Stage Boundary meeting, because both involve reviewing a plan, but the trigger (tolerance breach vs. end of stage) and the output (Exception Plan vs. Stage Plan) are fundamentally different.

How to eliminate wrong answers

Option A is wrong because a Stage Boundary meeting is held at the end of each management stage to review stage status and plan the next stage, not to address an in-flight tolerance breach. Option B is wrong because a Monthly Progress Meeting is a regular, scheduled event for reviewing progress against the plan, not an unscheduled meeting triggered by a tolerance deviation. Option C is wrong because a Daily Stand-up meeting is a team-level, operational coordination event, not a Project Board decision forum for handling exceptions.

Full explanation →

906

MCQmedium

Which risk response is appropriate for a threat that the project team decides to proactively manage by reducing the probability or impact?

A.Reduce

B.Avoid

C.Transfer

D.Accept

AnswerA

Reduce means taking action to lower probability or impact.

Why this answer

Reduce is the correct risk response because it involves implementing actions to lower the probability or impact of a threat while still accepting that the risk may occur. In PRINCE2, this is a proactive response where the project team actively manages the risk by, for example, adding redundancy or conducting more frequent testing to decrease the likelihood of failure. The key is that the risk is not eliminated entirely but its effects are mitigated.

Exam trap

In PRINCE2, the Reduce response is proactive but does not eliminate the risk, whereas Avoid eliminates the threat entirely. Candidates often confuse 'proactive management' with 'avoidance,' but Avoid means changing the plan to remove the risk source, not just reducing it.

How to eliminate wrong answers

Option B is wrong because Avoid is a risk response that involves changing the project plan to eliminate the threat entirely, such as by removing a high-risk feature, not by reducing its probability or impact. Option C is wrong because Transfer shifts the financial impact of a threat to a third party (e.g., through insurance or a fixed-price contract), but does not reduce the probability or impact of the risk itself. Option D is wrong because Accept means the project team acknowledges the threat and takes no proactive action, either because the risk is low or because the cost of mitigation is too high, which contradicts the proactive reduction described in the question.

Full explanation →

907

MCQmedium

A Project Manager receives a completed product from the Team Manager. Which process should the Project Manager use to verify that the product meets its quality criteria before acceptance?

A.Controlling a Stage

B.Managing a Stage Boundary

C.Managing Product Delivery

D.Initiating a Project

AnswerA

Controlling a Stage covers the Project Manager's work of accepting completed products from the Team Manager, checking them against their quality criteria and product description before approval. This is the process where product acceptance occurs within the stage boundary.

Why this answer

In PRINCE2, the 'Controlling a Stage' process is where the Project Manager monitors and controls the work of the stage, including receiving completed products from the Team Manager and verifying that they meet their quality criteria before acceptance. This process covers work package issuance, progress monitoring, and product acceptance within the current stage.

Exam trap

The trap here is confusing the Project Manager's product verification role in 'Controlling a Stage' with the Team Manager's delivery role in 'Managing Product Delivery,' or with end-stage activities in 'Managing a Stage Boundary.'

How to eliminate wrong answers

Option B is wrong because 'Managing a Stage Boundary' is used at the end of a stage to prepare for the next stage, not for verifying individual products during the stage. Option C is wrong because 'Managing Product Delivery' is the process used by the Team Manager to accept, execute, and deliver work packages, not by the Project Manager to verify products. Option D is wrong because 'Initiating a Project' is a pre-project process that establishes the project's baseline, not a process for product acceptance during execution.

Full explanation →

908

MCQhard

What is the primary difference between Starting Up a Project (SU) and Initiating a Project (IP)?

A.SU produces the Project Plan; IP produces the Stage Plan

B.SU is performed before the Project Board authorizes initiation; IP is performed after

C.SU is optional; IP is mandatory

D.SU appoints the Project Manager; IP appoints the Executive

AnswerB

Starting Up a Project assembles the outline Business Case and Project Brief so the Project Board can decide whether to authorise initiation. Initiating a Project then follows that authorisation, producing the Project Initiation Documentation; the sequence hinges on when Board authorisation occurs.

Why this answer

The primary difference is that Starting Up a Project (SU) is a pre-project process performed before the Project Board authorizes initiation, while Initiating a Project (IP) is the first process after the Project Board gives authorization. SU ensures the project is viable and creates the Project Brief, whereas IP develops the detailed Project Plan and Business Case for the Project Board's approval.

Exam trap

The trap here is confusing the outputs of SU and IP, specifically that SU produces the Project Brief (not the Project Plan) and that both processes are mandatory, not optional.

How to eliminate wrong answers

Option A is wrong because SU produces the Project Brief, not the Project Plan; the Project Plan is created during the IP process. Option C is wrong because both SU and IP are mandatory processes in PRINCE2; neither is optional. Option D is wrong because the Executive is appointed during SU, not IP; the Project Manager is also appointed during SU, not IP.

Full explanation →

909

MCQmedium

Which risk response is appropriate for a threat that can be mitigated by transferring the financial impact to a third party?

A.Avoid

B.Reduce

C.Transfer

D.Accept

AnswerC

Transfer shifts the financial consequence of a threat to a third party, typically via insurance or contractual arrangement, while the threat itself remains. This matches the stem's requirement to move financial impact rather than avoid, reduce or accept the risk.

Why this answer

Transfer is the PRINCE2 risk response that shifts the financial impact of a threat to a third party — typically via insurance, outsourcing, warranties, or contractual penalties. The threat still exists and may still occur, but the monetary consequence is borne by someone else, which is exactly what the question describes.

Exam trap

PRINCE2F often tests whether candidates confuse Transfer with Reduce — the trap is picking 'Reduce' because both involve action, when the distinguishing factor is that Transfer shifts the financial impact to a third party rather than lowering probability or impact.

How to eliminate wrong answers

Option A is wrong because Avoid eliminates the threat entirely by changing scope, approach, or requirements so the risk can no longer occur — it does not shift financial impact. Option B is wrong because Reduce (mitigate) lowers the probability or impact of the threat through proactive actions, but the organization still retains the residual risk and its financial consequences. Option D is wrong because Accept means the organization acknowledges the risk and budgets for it without taking action — the financial impact stays with the organization, which is the opposite of transferring it.

Full explanation →

910

MCQhard

A Project Manager is planning the next stage and updates the Project Plan. In which process is this activity performed?

A.Managing a Stage Boundary

B.Directing a Project

C.Initiating a Project

D.Controlling a Stage

AnswerA

Managing a Stage Boundary covers reviewing the current stage, updating the Project Plan and preparing the next Stage Plan for the project board's approval. Updating the Project Plan during stage planning therefore belongs to this process, not Controlling a Stage.

Why this answer

Updating the Project Plan when planning the next stage is a key activity in the Managing a Stage Boundary process. This process is specifically designed to provide the Project Board with information needed to approve the next stage, which includes updating the Project Plan to reflect the current stage's actuals and the revised plan for the remainder of the project.

Exam trap

The trap here is that candidates confuse 'Controlling a Stage' (which handles day-to-day work) with 'Managing a Stage Boundary' (which handles stage-end planning and plan updates), leading them to incorrectly select option D.

How to eliminate wrong answers

Option B (Directing a Project) is wrong because this process covers the Project Board's decision-making and overall project oversight, not the detailed planning and plan updates performed by the Project Manager. Option C (Initiating a Project) is wrong because this process creates the initial Project Plan and PID, but updating the plan during stage boundaries occurs later in the project lifecycle. Option D (Controlling a Stage) is wrong because this process focuses on day-to-day management of work packages and issue handling within a stage, not on planning the next stage or updating the Project Plan.

Full explanation →

911

MCQmedium

During the Managing Product Delivery process, who produces the Checkpoint Report?

A.Project Manager

B.Team Manager

C.Project Support

D.Project Board

AnswerB

The Team Manager produces Checkpoint Reports to update the Project Manager on work package progress, remaining effort and issues. This satisfies Managing Product Delivery, where the Team Manager controls work package delivery and reports at agreed frequency.

Why this answer

The Team Manager is responsible for producing Checkpoint Reports to inform the Project Manager of progress within a Work Package.

Full explanation →

912

MCQhard

A project is forecast to exceed its stage cost tolerance. What should the Project Manager do?

A.Continue and report in the next Highlight Report

B.Raise an Exception Report to the Project Board

C.Close the project

D.Increase the stage budget and continue

AnswerB

Breaching stage cost tolerance exceeds the Project Manager's delegated authority, so the deviation must be escalated. An Exception Report informs the Project Board of the forecast breach, enabling it to decide on corrective action, satisfying the stem's requirement for handling tolerance exceedance.

Why this answer

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

Full explanation →

913

MCQhard

A Project Manager is leading a project to develop a new software application. During a progress review, the Project Board notes that the project has been proceeding without a clear definition of the products to be delivered, leading to scope creep and rework. The Project Manager is asked to address this by applying a specific PRINCE2 principle. Which principle should be applied to resolve this issue?

A.Learn from experience

B.Manage by stages

C.Focus on products

D.Manage by exception

AnswerC

Focus on products requires that the project is driven by the definition and delivery of products, not just by activities. In this scenario, the lack of clear product definitions has caused scope creep and rework. Applying this principle means defining the products, their quality criteria, and their acceptance criteria upfront. This will provide a clear scope and reduce ambiguity, directly addressing the issue.

Why this answer

The principle of focus on products ensures that the project is defined and driven by its products. By clearly defining the products, their quality criteria, and acceptance criteria, the Project Manager can prevent scope creep and rework. This principle directly addresses the lack of product definitions described in the scenario.

The other principles are important but do not directly solve the root cause of the issue.

Exam trap

The trap here is thinking that manage by stages would solve scope creep, but it only provides control points; it is the product definitions that prevent scope creep.

Full explanation →

914

MCQhard

Which of the following describes the relationship between Project Assurance and Project Support?

A.Project Assurance is independent; Project Support provides admin services

B.Project Assurance reports to the Project Manager; Project Support reports to the Project Board

C.Project Assurance and Project Support are the same role

D.Project Assurance is part of Project Support

AnswerA

Project Assurance monitors the project independently of the Project Manager, reporting to the Project Board on viability and compliance. Project Support is a separate administrative function serving the Project Manager. The two are distinct roles, so Assurance's independence contrasts with Support's administrative service provision.

Why this answer

Project Assurance is an independent role that provides objective oversight to ensure the project remains viable and compliant with PRINCE2 principles, while Project Support is an administrative role that handles tasks like planning tools, filing, and configuration management. The independence of Project Assurance from the Project Manager is critical to avoid conflicts of interest, whereas Project Support serves the Project Manager and the team. This separation ensures that assurance activities are unbiased and that support services are efficient.

Exam trap

The trap here is that candidates confuse the reporting lines and independence of Project Assurance, mistakenly thinking it reports to the Project Manager or is part of Project Support, when in fact PRINCE2 mandates that Project Assurance must be independent and report to the Project Board.

How to eliminate wrong answers

Option B is wrong because Project Assurance reports to the Project Board, not the Project Manager, and Project Support reports to the Project Manager, not the Project Board. Option C is wrong because Project Assurance and Project Support are distinct roles with different objectives: assurance provides independent oversight, while support provides administrative services. Option D is wrong because Project Assurance is not a subset of Project Support; they are separate functions, and combining them would compromise the independence required for assurance.

Full explanation →

915

MCQmedium

Which process includes the activity of 'Authorize Work Packages'?

A.Directing a Project

B.Controlling a Stage

C.Managing Product Delivery

D.Starting Up a Project

AnswerB

Controlling a Stage covers work package authorisation: the Project Manager reviews the Work Package, confirms tolerances and resources, then issues it to the Team Manager. Authorising work packages sits here, not in Managing Product Delivery, which accepts and executes them.

Why this answer

'Authorize Work Packages' is an activity within the Controlling a Stage process. The Project Manager authorizes work packages to the Team Manager(s) after reviewing the Stage Plan, ensuring that the work is agreed and that the Team Manager has the necessary information to deliver the products. This activity is part of the day-to-day management of a stage.

Exam trap

PRINCE2F often tests process-activity mapping; the trap is confusing the Project Board's 'Directing a Project' authorization with the Project Manager's 'Controlling a Stage' authorization of work packages.

How to eliminate wrong answers

Option A is wrong because Directing a Project is the Project Board's process for authorizing the project, stage, or exception plans, not for authorizing individual work packages. Option C is wrong because Managing Product Delivery is the Team Manager's process that accepts and executes work packages; it does not include the authorization activity itself. Option D is wrong because Starting Up a Project is the pre-project process that creates the Project Brief and appoints the Project Manager, well before any work packages exist.

Full explanation →

916

MCQmedium

In PRINCE2, what is the purpose of the 'Directing a Project' process?

A.To plan and schedule the next stage

B.To manage the day-to-day activities of the project team

C.To create the project's products

D.To enable the Project Board to make key decisions and exercise overall control

AnswerD

'Directing a Project' enables the Project Board to be accountable for the project's success by making key decisions and exercising overall control, rather than performing day-to-day management. This satisfies the stem's requirement to identify the process's purpose: providing the decision-making and control layer that sits above the Managing a Stage Boundary and Controlling a Stage processes.

Why this answer

The 'Directing a Project' process in PRINCE2 is designed for the Project Board, not the project manager or team. Its purpose is to empower the Board to make key decisions (e.g., stage boundary approvals, exception plans) and exercise overall control from project initiation through closure, ensuring governance without involvement in day-to-day management.

Exam trap

PeopleCert often tests the misconception that 'Directing a Project' is about tactical management or product creation, when in fact it is exclusively about high-level governance and decision-making by the Project Board.

How to eliminate wrong answers

Option A is wrong because planning and scheduling the next stage is the responsibility of the 'Managing a Stage Boundary' process, not 'Directing a Project'. Option B is wrong because managing day-to-day activities is the purpose of the 'Managing Product Delivery' process, handled by the team manager. Option C is wrong because creating the project's products is the work of the 'Managing Product Delivery' process, executed by the project team, not the Project Board.

Full explanation →

917

MCQmedium

What is NOT covered by PRINCE2?

A.Risk management

B.Business Case management

C.Quality management

D.Human resource management

AnswerD

Human resource management covers line-management matters such as recruitment, contracts and appraisals, which PRINCE2 excludes. PRINCE2 addresses the organisation structure and role responsibilities for the project, but not the wider HR discipline, satisfying the stem's NOT requirement.

Why this answer

PRINCE2 is a process-based project management methodology that focuses on business justification, defined roles, and product-based planning. It explicitly covers risk management, business case management, and quality management as core themes, but it does not prescribe detailed human resource management practices; instead, it defines roles and responsibilities within the project management team.

Exam trap

The trap here is that candidates may assume PRINCE2 covers all aspects of project management, including human resource management, because it defines roles and responsibilities, but the exam specifically tests that PRINCE2 does not include detailed HR processes such as staff recruitment, training, or performance management.

How to eliminate wrong answers

Option A is wrong because PRINCE2 includes a dedicated 'Risk' theme that provides a systematic approach to identifying, assessing, and controlling risks throughout the project. Option B is wrong because the 'Business Case' theme is central to PRINCE2, ensuring the project remains viable and aligned with organizational objectives. Option C is wrong because the 'Quality' theme in PRINCE2 defines how quality is planned, controlled, and verified, including product-based quality criteria and quality registers.

Full explanation →

918

MCQmedium

During the Directing a Project process, the Project Board receives an Exception Report. What action should the Project Board take?

A.Authorize the next stage as planned

B.Request a new Project Brief

C.Assess the situation and, if appropriate, approve an Exception Plan

D.Instruct the Project Manager to continue with the current plan

AnswerC

An Exception Report triggers the Project Board to assess the deviation against tolerances and decide how to respond. Approving an Exception Plan authorises the Project Manager to replace the current Stage Plan or Project Plan, restoring the project to a controlled state within the Directing a Project process.

Why this answer

During Directing a Project, when the Project Board receives an Exception Report, they must assess the situation and decide whether to approve an Exception Plan. The Exception Plan outlines how to recover from the exception. This is a key responsibility of the Project Board.

Exam trap

The trap is thinking the Project Board can simply authorize the next stage or ignore the exception; they must address the exception by evaluating an Exception Plan.

How to eliminate wrong answers

Option A is wrong because authorizing the next stage as planned is not appropriate when an exception has occurred; the plan is no longer valid. Option B is wrong because requesting a new Project Brief is not part of Directing a Project; the Project Brief is created during pre-project. Option D is wrong because instructing the Project Manager to continue with the current plan ignores the exception and is not a valid action.

Full explanation →

919

MCQeasy

A project manager is leading a project to implement a new customer relationship management (CRM) system. The project board has defined tolerances for cost and time, and the project manager is authorized to manage the project within these tolerances. During a stage, the project manager discovers that a key supplier has increased prices, which will cause the stage to exceed its cost tolerance. According to PRINCE2 principles, what should the project manager do?

A.Adjust the project plan to absorb the cost increase within the stage.

B.Escalate the issue to the project board immediately.

C.Ask the supplier to honor the original price to avoid exceeding tolerance.

D.Update the business case to reflect the increased costs and continue.

AnswerB

The principle of manage by exception requires the project manager to escalate to the project board as soon as it is forecast that a tolerance will be exceeded. Since the cost tolerance is at risk, the project manager must inform the board and seek a decision, rather than attempting to resolve it independently or amending the business case without authority.

Why this answer

Manage by exception empowers the project manager to run the project within agreed tolerances, but when a tolerance is forecast to be exceeded, the issue must be escalated to the project board. This ensures that the board can make an informed decision about how to proceed, whether by providing additional funds, changing scope, or stopping the project.

Exam trap

The trap here is thinking that the project manager can take any action necessary to stay within tolerance, but the principle requires escalation when tolerances are threatened.

Full explanation →

920

MCQmedium

In which process does the Project Board authorize the next stage of a project?

A.Directing a Project

B.Managing a Stage Boundary

C.Initiating a Project

D.Controlling a Stage

AnswerA

Directing a Project is the process where the Project Board retains accountability, authorising each stage boundary via the 'authorise a stage or exception plan' activity. It satisfies the stem's requirement for the Board's stage authorisation, distinct from Managing a Stage Boundary, which merely prepares the next Stage Plan for approval.

Why this answer

The Project Board authorizes the next stage of a project during the Directing a Project process. In this process, the Project Board makes key decisions, including stage authorization, based on the Stage Plan prepared in the Managing a Stage Boundary process. Therefore, authorization is a direct responsibility of the Directing a Project process, not Managing a Stage Boundary.

Exam trap

The trap is that candidates may think Managing a Stage Boundary authorizes the next stage because it prepares the plan, but the actual authorization decision is made by the Project Board in Directing a Project.

How to eliminate wrong answers

Option A is wrong because Directing a Project is the process by which the Project Board makes key decisions and provides overall direction, but it does not specifically authorize the next stage; that authorization is given as a result of the Managing a Stage Boundary process. Option C is wrong because Initiating a Project is the process that produces the Project Initiation Documentation and authorizes the project itself, not the authorization of subsequent stages. Option D is wrong because Controlling a Stage is the process where the Project Manager manages the day-to-day work of a stage and reports progress to the Project Board, but it does not involve authorizing the next stage.

Full explanation →

921

MCQmedium

Which report is prepared by the Team Manager and sent to the Project Manager at regular intervals?

A.End Stage Report

B.Exception Report

C.Highlight Report

D.Checkpoint Report

AnswerD

The Checkpoint Report is produced by the Team Manager at the frequency agreed in the Work Package and sent to the Project Manager, covering progress, issues and next steps. This satisfies the stem's requirement for a regular Team Manager report, distinguishing it from Highlight and End Stage Reports.

Why this answer

The Checkpoint Report is prepared by the Team Manager and sent to the Project Manager at regular intervals (typically weekly or at agreed frequencies) to report on progress, status, and issues within the team. It is a PRINCE2 progress report that provides the Project Manager with visibility into team-level work. The Highlight Report, by contrast, is prepared by the Project Manager for the Project Board.

Exam trap

PRINCE2F often tests the confusion between the Checkpoint Report (Team Manager to Project Manager) and the Highlight Report (Project Manager to Project Board), so candidates who mix up the sender and recipient pick the wrong report.

How to eliminate wrong answers

Option A is wrong because the End Stage Report is prepared by the Project Manager at the end of a stage for the Project Board, not by the Team Manager at regular intervals. Option B is wrong because the Exception Report is prepared by the Project Manager when a tolerance is forecast to be exceeded, and it is escalated to the Project Board. Option C is wrong because the Highlight Report is prepared by the Project Manager for the Project Board at regular intervals, not by the Team Manager.

Full explanation →

922

MCQmedium

A Work Package has been completed and the products have passed quality checks. What should the Team Manager do next in the Managing Product Delivery process?

A.Raise an Exception Report

B.Update the Project Plan

C.Close the project stage

D.Deliver the Work Package to the Project Manager

AnswerD

With the Work Package complete and products passing quality checks, the Team Manager reports completion by delivering it to the Project Manager, who then accepts it and updates the relevant stage plan and product status.

Why this answer

In PRINCE2's Managing Product Delivery process, once a Work Package's products have passed quality checks, the Team Manager's next step is to deliver the completed Work Package to the Project Manager. This triggers the Project Manager to update the Stage Plan and check the Work Package against its tolerances. The Team Manager does not close the stage or update the Project Plan — those are Project Manager responsibilities.

Exam trap

PRINCE2F often tests the boundary between Team Manager and Project Manager responsibilities, so candidates who confuse 'deliver the Work Package' with 'update the Project Plan' or 'close the stage' pick the wrong role's action.

How to eliminate wrong answers

Option A is wrong because an Exception Report is raised when a Work Package is forecast to exceed its tolerances, not when it completes successfully. Option B is wrong because updating the Project Plan is the Project Manager's responsibility, not the Team Manager's, and the Project Plan is updated at stage boundaries, not per Work Package. Option C is wrong because closing a project stage is part of the Closing a Stage process owned by the Project Manager and Project Board, not the Team Manager in Managing Product Delivery.

Full explanation →

923

MCQhard

In the Closing a Project process, what is the Project Board's responsibility?

A.To produce the Lessons Report

B.To hand over the project products to the operational environment

C.To confirm the project has met its objectives and authorize closure

D.To release the project resources

AnswerC

The Project Board owns the decision to close, so it reviews the End Project Report and confirms the project has delivered its objectives before authorising closure. This satisfies the Closing a Project process requirement that closure is formally approved by the board, not the project manager.

Why this answer

In PRINCE2's Closing a Project process, the Project Board's responsibility is to confirm that the project has met its objectives and to authorize closure. This is done at the 'Authorize Project Closure' activity, where the Project Board reviews the End Project Report and approves closure. The Project Board does not produce the Lessons Report or hand over products — those are Project Manager and operational staff responsibilities.

Exam trap

PRINCE2F often tests the division of responsibilities between the Project Board and Project Manager, so candidates who assume the board produces documents or hands over products pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because the Lessons Report is produced by the Project Manager (with input from the team), not the Project Board. Option B is wrong because handing over products to the operational environment is the responsibility of the Project Manager and the operational/maintenance team, not the Project Board. Option D is wrong because releasing project resources is an operational task performed by the Project Manager after closure is authorized, not a Project Board responsibility.

Full explanation →

924

MCQmedium

A project is in the Closing a Project process. What should the Project Manager produce to recommend project closure?

A.Exception Report

B.End Project Report

C.End Stage Report

D.Project Brief

AnswerB

The End Project Report is the PRINCE2 product the Project Manager produces during Closing a Project to assess the project against its original baselines and recommend closure to the Project Board, satisfying the stem's requirement for a closure recommendation.

Why this answer

The End Project Report is the PRINCE2 management product produced during the Closing a Project process to recommend project closure. It summarizes the project's performance against the Project Initiation Documentation (PID), confirms acceptance of products, and provides the recommendation to the Project Board to close the project. It is the formal document that triggers the closure decision.

Exam trap

PRINCE2F often tests the confusion between End Stage Report (stage boundary) and End Project Report (project closure) — candidates pick End Stage Report because both contain 'End' and 'Report', but only the End Project Report recommends project closure.

How to eliminate wrong answers

Option A is wrong because an Exception Report is produced during a stage when a tolerance is forecast to be exceeded, not at project closure. Option C is wrong because an End Stage Report is produced at the end of each management stage (during Managing a Stage Boundary), not specifically to recommend project closure. Option D is wrong because the Project Brief is a pre-project document created during Starting Up a Project, long before closure.

Full explanation →

925

MCQmedium

What is the purpose of the Quality Review technique?

A.To approve the project's quality management approach

B.To update the quality register

C.To assess the quality of a product and identify defects

D.To define quality criteria for products

AnswerC

The Quality Review technique is used to review products against their quality criteria.

Why this answer

The Quality Review technique in PRINCE2 is a structured assessment of a product's fitness for purpose. Its primary purpose is to assess the quality of a product and identify any defects, ensuring that the product meets its agreed quality criteria before it is approved. This is a key part of the 'Manage Product Delivery' and 'Quality Management' processes.

Exam trap

The trap here is confusing the purpose of the Quality Review technique (assessing a product and finding defects) with the broader activities of quality management, such as defining criteria or updating registers, which are separate processes or outputs.

How to eliminate wrong answers

Option A is wrong because approving the project's quality management approach is the purpose of the 'Quality Management Strategy' document, not the Quality Review technique. Option B is wrong because updating the quality register is an administrative action that may result from a Quality Review, but it is not the technique's purpose; the technique itself focuses on product assessment. Option D is wrong because defining quality criteria for products is done during product planning (e.g., in Product Descriptions), not during the Quality Review, which assesses the product against those pre-defined criteria.

Full explanation →

926

Multi-Selecthard

Which THREE activities are part of the Controlling a Stage process?

Select 3 answers

A.Authorize Work Packages

B.Produce the Project Initiation Documentation (PID)

C.Review progress and update stage status

D.Approve the next Stage Plan

E.Escalate issues and risks that exceed stage tolerances

AnswersA, C, E

Authorising Work Packages sits within Controlling a Stage, where the Project Manager approves delegated work and confirms the Work Package's tolerances before the Team Manager begins delivery. This satisfies the stem's requirement for a Controlling a Stage activity, since authorisation occurs after stage authorisation and before progress monitoring.

Why this answer

In PRINCE2, the Controlling a Stage process covers the day-to-day management of a stage by the Project Manager, and it includes authorizing work packages (option A) so that agreed work is formally delegated to Team Managers with the required tolerances and interfaces. It also includes reviewing progress and updating stage status (option C), which is done through regular checkpoint and highlight reports, comparing actuals against the Stage Plan and Work Package tolerances. Escalating issues and risks that exceed stage tolerances (option E) is also part of Controlling a Stage, since the Project Manager must raise an Exception Report to the Project Board when stage-level tolerances are forecast to be breached.

Producing the Project Initiation Documentation (option B) belongs to Initiating a Project, and approving the next Stage Plan (option D) is a Project Board activity in Managing a Stage Boundary, so neither is part of Controlling a Stage.

Exam trap

PRINCE2F often tests the confusion between Controlling a Stage and Managing a Stage Boundary, tricking candidates into selecting activities like approving the next Stage Plan or producing the PID that belong to other processes.

Full explanation →

927

MCQmedium

Who receives Highlight Reports?

A.Project Board

B.Senior Supplier

C.Project Support

D.Team Manager

AnswerA

The Project Board needs Highlight Reports to monitor progress, compare actuals against the plan, and make informed decisions at stage boundaries. This satisfies the PRINCE2 principle of defined roles and responsibilities, ensuring the board maintains oversight without requiring detailed Checkpoint Reports, which are reserved for the Team Manager.

Why this answer

Highlight Reports are prepared by the Project Manager and sent to the Project Board (and possibly stakeholders) at regular intervals.

Full explanation →

928

MCQmedium

In a large program, the project manager is struggling to get timely decisions from the project board due to conflicting priorities. What is the best PRINCE2 approach to address this?

A.Delay decisions until the board reaches consensus on their own

B.Escalate the issue to the program management for resolution

C.Request the project board to hold a facilitated session to align their priorities

D.Redefine the project management team roles to reduce board involvement

AnswerC

A facilitated session directly targets the conflicting priorities causing delayed decisions, satisfying the stem's constraint of untimely project board decisions. PRINCE2 assigns the board collective decision-making authority, so aligning members' priorities through structured facilitation restores the timely decisions the project manager requires, rather than escalating or bypassing governance.

Why this answer

PRINCE2 emphasizes that the project board must provide unified direction and timely decisions. When conflicting priorities arise, a facilitated session is a recognized technique to align the board's priorities, ensuring effective governance without bypassing the board's authority. This approach directly addresses the root cause—misalignment—rather than delaying, escalating prematurely, or reducing board involvement.

Exam trap

The trap here is that candidates may confuse escalation (Option B) as the default PRINCE2 response to any issue, but PRINCE2 requires exhausting internal resolution mechanisms—like facilitated alignment—before escalating to program management.

How to eliminate wrong answers

Option A is wrong because delaying decisions until the board reaches consensus on their own violates the PRINCE2 principle of 'manage by stages' and can cause project delays, as the project manager should actively facilitate decision-making rather than passively wait. Option B is wrong because escalating to program management is premature; the project board is the decision-making body for the project, and the issue should first be resolved within the board before involving higher management. Option D is wrong because redefining roles to reduce board involvement undermines the PRINCE2 principle of 'defined roles and responsibilities' and the project board's accountability for key decisions, which cannot be delegated away.

Full explanation →

929

MCQmedium

Which document defines the quality criteria and acceptance methods for a project's products?

A.Product Description

B.Quality Management Approach

C.Business Case

D.Project Plan

AnswerA

The Product Description records, for each product, its quality criteria and the acceptance methods used to verify them. It therefore supplies the measurable tolerances and testing approach the stem requires, forming the baseline against which PRINCE2 quality control and acceptance are performed.

Why this answer

The Product Description defines the quality criteria, acceptance methods, and other details for each product. The Quality Management Approach defines the overall quality strategy, not the specific criteria for individual products.

Full explanation →

930

MCQmedium

You are managing a construction project. During the Initiation Stage, you are developing the Project Plan. The senior supplier informs you that the required steel will be delayed by 3 months due to a global shortage. This delay will push the project completion beyond the board's deadline. The project has a fixed completion date due to regulatory requirements. The senior user is unwilling to accept a delay. You have identified that using an alternative material could save 2 months but would increase costs by 15%. The project budget has a 10% contingency. What is the most appropriate course of action?

A.Reduce the project scope to meet the deadline

B.Switch to the alternative material and use the contingency to cover the cost increase

C.Accept the delay and update the Project Plan accordingly

D.Inform the board that the project cannot meet the deadline and request guidance

AnswerD

The delay exceeds the fixed regulatory deadline and the alternative material's 15% cost increase exceeds the 10% contingency, so the project manager cannot resolve it within tolerance. Escalating to the board for guidance satisfies the PRINCE2 principle of management by exception.

Why this answer

The project has a fixed completion date due to regulatory requirements, and the identified solution (alternative material) still results in a 1-month delay (3-month delay minus 2-month saving) and exceeds the 10% contingency (15% cost increase vs. 10% contingency). According to PRINCE2, when a stage plan or project plan cannot be achieved within agreed tolerances, the Project Manager must escalate the issue to the Project Board for a decision. The board is the only authority that can authorize a change to the project's scope, schedule, or budget beyond the delegated tolerances.

Exam trap

The trap here is that candidates may think the contingency is available to cover any cost overrun, but PRINCE2 requires that contingency use must be within agreed tolerances and that exceeding tolerances triggers escalation, not autonomous action.

How to eliminate wrong answers

Option A is wrong because reducing scope without board authorization violates PRINCE2's management by exception principle; the Project Manager does not have the authority to change scope beyond tolerances. Option B is wrong because the 15% cost increase exceeds the 10% contingency, meaning the budget tolerance would be breached, and the Project Manager must escalate rather than unilaterally use contingency funds. Option C is wrong because accepting the delay and updating the Project Plan without board approval would ignore the fixed regulatory deadline and the need for exception management; the board must decide whether to accept the delay or authorize a different approach.

Full explanation →

931

MCQmedium

During the Initiation Stage of a PRINCE2 project, the Project Manager is compiling the Project Initiation Documentation (PID). The Project Board has asked for assurance that the project will deliver the required products to the specified quality standards. Which component of the PID should the Project Manager include to provide this assurance?

A.Communication Management Approach

B.Project Plan

C.Quality Management Approach

D.Business Case

AnswerC

The Quality Management Approach describes how quality will be managed and controlled, including quality criteria, methods, and responsibilities. It provides the Board with assurance that the project's products will meet the required standards. It is a key component of the PID that addresses quality assurance and is directly relevant to the Board's request.

Why this answer

The Quality Management Approach is the PID component that details how quality will be managed, including standards, methods, and responsibilities. It gives the Project Board confidence that the project's products will meet requirements. Other components like the Project Plan and Business Case serve different purposes and do not provide the specific quality assurance requested.

Exam trap

The trap here is assuming that the Project Plan, because it includes products, covers quality assurance, but it does not detail the quality management methods.

Full explanation →

932

MCQhard

A project is nearing the end of a stage, and the Project Manager is preparing the End Stage Report. The Project Board has requested that the project be closed prematurely due to changing business priorities. What should the Project Manager do FIRST?

A.Update the Business Case to reflect the premature closure.

B.Close the project immediately and release all resources.

C.Prepare a Lessons Report to capture what went wrong.

D.Confirm the closure with the Project Board and then follow the 'Closing a Project' process.

AnswerD

When the Project Board decides to close the project prematurely, the Project Manager's first action is to confirm this decision and then initiate the 'Closing a Project' process. This process includes activities such as preparing the End Project Report, updating the Business Case, and capturing lessons. Confirming with the Project Board ensures that the decision is formally recorded and that the Project Manager has clear direction to proceed with closure.

Why this answer

The first action is to confirm the premature closure with the Project Board and then follow the 'Closing a Project' process. This process ensures that the project is closed in a controlled manner, with all necessary documentation and approvals. Confirming with the Project Board provides the authority to proceed and ensures that the decision is formally acknowledged.

The closure process includes preparing the End Project Report, updating the Business Case, and capturing lessons learned.

Exam trap

The trap here is jumping straight into closure activities like updating the Business Case or preparing a Lessons Report without first confirming the Project Board's decision and initiating the formal closure process.

Full explanation →

933

MCQeasy

In the Directing a Project process, which of the following is a key responsibility of the Project Board?

A.Producing Highlight Reports

B.Authorizing the next Stage Plan

C.Managing day-to-day work within a stage

D.Accepting Work Packages

AnswerB

Authorising the next Stage Plan sits with the Project Board because Directing a Project reserves stage-boundary decisions to that level, satisfying the stem's requirement for a Project Board responsibility. The Project Manager drafts the plan; the Board alone grants the authority to proceed, ensuring continued business justification before committing resources.

Why this answer

In PRINCE2, the Directing a Project process is the decision-making layer where the Project Board exercises overall control. A key responsibility is authorizing the next Stage Plan, which formally approves the detailed plan for the upcoming management stage and commits the resources required to execute it. This ensures the project remains viable and aligned with business justification before proceeding.

Exam trap

PeopleCert often tests the distinction between the Project Board's strategic control (authorizing stages) and the Project Manager's tactical execution (producing reports, managing daily work), leading candidates to confuse the two roles.

How to eliminate wrong answers

Option A is wrong because producing Highlight Reports is a responsibility of the Project Manager, not the Project Board; the Project Board receives these reports to monitor progress. Option C is wrong because managing day-to-day work within a stage is the responsibility of the Project Manager, who coordinates the team and handles operational issues. Option D is wrong because accepting Work Packages is a task performed by the Team Manager or team members, not the Project Board; the Project Board authorizes the stage plan that contains the work packages.

Full explanation →

934

Multi-Selectmedium

Which TWO of the following are types of issues in PRINCE2?

Select 2 answers

A.Request for Change

B.Change

C.Risk

D.Off-specification

E.Opportunity

AnswersA, D

An RFC is a type of issue.

Why this answer

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. A Request for Change (A) is a formal proposal for a modification to a product, baseline, or agreed scope, making it a standard type of issue. An Off-specification (D) is a type of issue that identifies a product that should be provided but is not, or that is provided but does not meet its specification, also making it a standard type of issue.

Exam trap

A common pitfall in PRINCE2 is confusing issue types with risk categories. 'Change' is not a formal issue type; the correct term is 'Request for Change'. Similarly, 'Opportunity' is a risk type, not an issue type. Know the three defined issue types: Request for Change, Off-specification, and Problem/Concern.

Full explanation →

935

MCQmedium

During the Controlling a Stage process, who is responsible for producing Checkpoint Reports?

A.Team Manager

B.Project Manager

C.Project Board

D.Project Support

AnswerA

The Team Manager produces Checkpoint Reports during Controlling a Stage, reporting work package progress, quality and tolerance status to the Project Manager. This satisfies the stem because Checkpoint Reports flow upward from team level, while Highlight Reports are the Project Manager's own output to the board.

Why this answer

Checkpoint Reports are produced by the Team Manager and sent to the Project Manager to inform about progress within a Work Package.

Full explanation →

936

MCQmedium

In PRINCE2, who is responsible for providing assurance that the project is being conducted properly?

A.Project Support

B.Project Manager

C.Project Board

D.Project Assurance

AnswerD

Project Assurance is a defined PRINCE2 role, separate from the Project Manager and the Project Board, specifically tasked with providing independent assurance that the project remains aligned with its business justification and is conducted properly according to PRINCE2 principles and tolerances. This satisfies the stem’s requirement for a role explicitly responsible for monitoring compliance and governance, not for managing or directing the project.

Why this answer

In PRINCE2, Project Assurance is the role responsible for independently monitoring and verifying that the project is being conducted properly — that it remains justified, viable, and aligned with the business case, and that the project management team is following PRINCE2 principles and tolerances. Project Assurance reports to the Project Board, not the Project Manager, preserving independence.

Exam trap

PRINCE2F often tests the confusion between Project Assurance (independent monitoring) and Project Support (administrative help), since both are support functions but only one provides independent assurance.

How to eliminate wrong answers

Option A is wrong because Project Support provides administrative and tooling support (e.g., maintaining the project filing structure, configuration management), not independent assurance. Option B is wrong because the Project Manager runs the project day-to-day and cannot independently assure their own work. Option C is wrong because the Project Board owns the project and makes decisions; it receives assurance but does not perform the assurance function itself.

Full explanation →

937

MCQhard

In the risk management procedure, what is the difference between a risk owner and a risk actionee?

A.Risk owner identifies risks; risk actionee assesses them

B.Risk owner manages the risk overall; risk actionee performs specific actions

C.Risk owner is the same as risk actionee in PRINCE2

D.Risk owner is on the Project Board; risk actionee is a team member

AnswerB

The risk owner is accountable for managing all aspects of a particular risk, while the risk actionee carries out the specific response actions assigned to them. This separation lets one person own the risk while others execute discrete tasks, satisfying the stem's distinction between overall management and action performance.

Why this answer

In PRINCE2's risk management procedure, the risk owner is responsible for managing, monitoring, and controlling all aspects of a risk, including ensuring that appropriate responses are implemented. The risk actionee, on the other hand, is assigned to carry out specific risk response actions. Option B correctly captures this distinction: the risk owner manages the risk overall, while the risk actionee performs specific actions.

Exam trap

The trap here is that candidates often confuse the risk owner with the risk actionee, assuming they are interchangeable or that the risk owner must be a senior stakeholder like a Project Board member, when in fact PRINCE2 explicitly separates these roles to clarify accountability and execution responsibilities.

How to eliminate wrong answers

Option A is wrong because the risk owner does not solely identify risks; risk identification is a shared activity involving the project manager and team, and the risk actionee does not assess risks—assessment is done by the risk owner with support from the project manager. Option C is wrong because the risk owner and risk actionee are distinct roles in PRINCE2; they are not the same, as the risk owner has overall accountability while the risk actionee executes specific tasks. Option D is wrong because the risk owner is not necessarily on the Project Board; the risk owner can be any competent individual (e.g., a team member or subject matter expert), and the risk actionee is not limited to being a team member—they could be external specialists or suppliers.

Full explanation →

938

MCQmedium

According to PRINCE2, which role is responsible for defining the project's tolerances?

A.Team Manager

B.Senior User

C.Project Manager

D.Project Board

AnswerD

The Project Board sets project-level tolerances for time, cost, scope, quality, risk and benefit, delegating authority within those limits to the Project Manager. This satisfies the question's requirement, as tolerances define the permissible deviation before escalation to the Board.

Why this answer

In PRINCE2, the Project Board is the authority that sets project-level tolerances for the six performance targets (time, cost, scope, quality, risk, benefit). Tolerances define the delegated authority limits within which the Project Manager can manage without escalation. The Project Board defines these at project initiation and reviews them at each stage boundary.

Exam trap

PRINCE2F often tests the confusion between who sets tolerances versus who works within them — candidates incorrectly assume the Project Manager defines tolerances because they create the plans.

How to eliminate wrong answers

Option A is wrong because the Team Manager works within tolerances assigned by the Project Manager for work packages and has no authority to define project-level tolerances. Option B is wrong because the Senior User represents user interests and specifies requirements but does not set tolerances. Option C is wrong because the Project Manager operates within tolerances set by the Project Board and may propose them, but does not have the authority to define them.

Full explanation →

939

MCQhard

During which process is the Project Plan created?

A.Initiating a Project

B.Managing a Stage Boundary

C.Starting Up a Project

D.Directing a Project

AnswerA

The Project Plan is produced during Initiating a Project, where the Project Initiation Documentation is assembled and the Project Board authorises the project. This satisfies the stem's question by distinguishing the project-level plan from the Stage Plan created later at Managing a Stage Boundary.

Why this answer

The Project Plan is created during Initiating a Project.

Full explanation →

940

MCQmedium

A Project Manager is midway through the Controlling a Stage process. The Stage Plan shows sufficient remaining time and budget to complete all work packages, but the Project Manager has just received an Exception Report from a Team Manager indicating that a work package will exceed its agreed tolerances. What should the Project Manager do FIRST?

A.Escalate the exception to the Project Board immediately by producing an Exception Report for the stage.

B.Assess the exception against the stage tolerances and consider corrective action before escalating.

C.Instruct the Team Manager to stop all work on the work package and await a new Work Package.

D.Authorize the Team Manager to continue and record the issue in the Issue Register without further action.

AnswerB

In Controlling a Stage, the Project Manager receives exceptions, assesses their impact against the stage tolerances and the Business Case, and takes corrective action if possible. Escalation to the Project Board only happens when the stage tolerances are forecast to be exceeded, so assessing and acting first is the correct sequence.

Why this answer

When a Team Manager raises an exception, the Project Manager must first assess it against the stage tolerances and decide whether corrective action can keep the stage within tolerance. Only if the stage tolerances are forecast to be exceeded does the Project Manager escalate to the Project Board. This ensures that manageable issues are resolved at the lowest appropriate level.

Exam trap

The trap here is assuming that any work package exception must be escalated immediately to the Project Board, when the Project Manager should first assess it against stage tolerances and take corrective action.

Full explanation →

941

MCQmedium

During the Initiating a Project process, which document is the key output that defines how the project will be managed?

A.Project Initiation Documentation

B.End Stage Report

C.Project Brief

D.Business Case

AnswerA

The Project Initiation Documentation (PID) is the mandated output of Initiating a Project, consolidating the Project Plan, business case, risk and quality approaches into a single baseline. It defines how the project will be managed, satisfying the stem's requirement for the key management-defining document.

Why this answer

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It consolidates all the information needed to manage the project, including the project plan, business case, risk register, and quality management approach. It serves as the baseline against which progress and changes are assessed.

Exam trap

PRINCE2F often tests the distinction between the Project Brief and the Project Initiation Documentation, as both are key documents but belong to different processes.

How to eliminate wrong answers

Option B is wrong because the End Stage Report is produced at the end of a stage, not during Initiating a Project; it summarizes performance and is used for the next stage's approval. Option C is wrong because the Project Brief is a pre-project document created during Starting Up a Project, providing the foundation for the PID. Option D is wrong because the Business Case is a component of the PID, not the overarching management document itself.

Full explanation →

942

MCQeasy

In PRINCE2, who is responsible for project assurance?

A.The Project Manager

B.The Senior Supplier

C.The Project Support

D.The Project Board

AnswerD

Project assurance in PRINCE2 sits with the Project Board, which is accountable for confirming the project remains viable and aligned with business justification. Board members independently monitor each project management level, ensuring the three stakeholder interests are represented throughout.

Why this answer

Project assurance is the responsibility of the Project Board, which provides independent assurance.

Full explanation →

943

MCQeasy

A project board is reviewing the PRINCE2 principles to ensure the project is compliant. They note that the project has a business case, but it was created at the start and has not been updated since. Which PRINCE2 principle is being violated?

A.Continued business justification

B.Manage by stages

C.Focus on products

D.Learn from experience

AnswerA

Continued business justification requires that a project has a valid business case that is reviewed and updated throughout the project. If the business case is not updated, the project may continue even if it no longer delivers value. This principle ensures that the project remains aligned with business objectives and should be stopped if justification is lost. The scenario directly violates this principle.

Why this answer

The principle of continued business justification mandates that a PRINCE2 project must have a justifiable business case that is reviewed and updated at key points, such as stage boundaries. A static business case that is not revisited can lead to a project continuing without valid justification. The scenario describes exactly that, so the violated principle is continued business justification.

Exam trap

The trap here is assuming that simply having a business case is enough, when the principle requires that it is continuously reviewed and updated.

Full explanation →

944

MCQeasy

A project is in the Initiation Stage. The Project Manager needs to define how the project will manage its products, including quality criteria, quality methods, and responsibilities. Which document should the Project Manager create as part of the Project Initiation Documentation (PID)?

A.The Benefits Review Plan

B.The Project Product Description

C.The Product Description

D.The Quality Management Approach

AnswerD

The Quality Management Approach is the PID component that defines the project's quality standards, procedures, techniques, and responsibilities. It specifies how products will be quality controlled and assured, including quality criteria and methods, directly addressing the Project Manager's need to manage products effectively.

Why this answer

The Quality Management Approach is the correct PID component because it establishes the project's quality standards, procedures, and responsibilities. It ensures that products meet their quality criteria through defined methods. The other options are either product-specific descriptions or unrelated plans that do not provide a project-wide quality framework.

Exam trap

The trap here is selecting a Product Description because it mentions quality criteria, but that document is product-specific and does not define the project's overall quality management approach.

Full explanation →

945

MCQmedium

A project is running late, and the Project Manager needs to decide whether to escalate an issue to the Project Board. The issue is within the stage tolerance for time but threatens to breach the project-level tolerance if not addressed. What should the Project Manager do?

A.Take corrective action within the stage tolerance and continue to monitor

B.Amend the Stage Plan to reflect the new forecast and proceed

C.Escalate the issue to the Project Board by submitting an Exception Report

D.Ask the Senior User to make a decision on the issue

AnswerC

When a project-level tolerance is forecast to be breached, the Project Manager must escalate to the Project Board by producing an Exception Report. The Board then decides how to proceed, for example by granting a tolerance, changing the project, or stopping it. This action is required because the issue is beyond the Project Manager's delegated authority, even though it is within the stage tolerance.

Why this answer

When a project-level tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board using an Exception Report. The Board is responsible for decisions that affect project-level tolerances, as these are beyond the Project Manager's delegated authority. Although the issue is within stage tolerance, the potential breach of project tolerance requires Board involvement to ensure the project remains justified and controlled.

Exam trap

The trap here is assuming that because the issue is within stage tolerance, the Project Manager can handle it alone, overlooking that project-level tolerances are the Board's authority.

Full explanation →

946

MCQmedium

In PRINCE2, who is responsible for preparing and updating the Highlight Report?

A.Team Manager

B.Project Support

C.Project Manager

D.Senior User

AnswerC

The Project Manager produces the Highlight Report, summarising project progress, status and issues for the Project Board at agreed intervals. This responsibility sits with the Project Manager rather than the Board or Team Manager, matching PRINCE2's defined roles for progress reporting.

Why this answer

In PRINCE2, the Project Manager is explicitly responsible for preparing and updating the Highlight Report, which is a progress report sent to the Project Board. The Highlight Report summarizes project status, including progress, issues, and risks, and is a key communication tool between the Project Manager and the Project Board. This responsibility is defined in the PRINCE2 'Progress' theme and the 'Managing a Stage Boundary' process.

Exam trap

PRINCE2F often tests the confusion between the Highlight Report and the Checkpoint Report, leading candidates to incorrectly attribute the Highlight Report to the Team Manager.

How to eliminate wrong answers

Option A is wrong because the Team Manager is responsible for producing Checkpoint Reports, which are internal to the team and feed into the Highlight Report. Option B is wrong because Project Support provides administrative assistance but does not own the Highlight Report. Option D is wrong because the Senior User represents user interests on the Project Board and receives the Highlight Report but does not prepare it.

Full explanation →

947

MCQmedium

A programme manager is setting up a new PRINCE2 project to develop a mobile banking app. The project will use a supplier to build the app, and the programme manager wants to ensure that the project has the right level of direction and management. Which PRINCE2 principle is being applied when the project is established with a defined organization structure that includes a Project Board with clear roles and responsibilities?

A.Defined roles and responsibilities

B.Manage by exception

C.Focus on products

D.Tailor to suit the project environment

AnswerA

This principle ensures that every project has a clear organizational structure with defined roles, such as the Project Board, Project Manager, and Team Manager. In this scenario, establishing a Project Board with clear roles directly applies this principle, ensuring accountability and direction for the mobile banking app project.

Why this answer

The defined roles and responsibilities principle ensures that projects have a clear organizational structure with defined roles, such as the Project Board, Project Manager, and Team Manager. By establishing a Project Board with clear roles, the programme manager applies this principle to provide direction and management for the mobile banking app project.

Exam trap

The trap here is confusing the defined roles and responsibilities principle with manage by exception, which is about tolerances and delegation, not about establishing roles.

Full explanation →

948

Multi-Selecteasy

Which TWO documents are produced during the Starting Up a Project process?

Select 2 answers

A.Project Initiation Documentation

B.End Stage Report

C.Stage Plan for the next stage

D.Initiation Stage Plan

E.Project Brief

AnswersD, E

The Initiation Stage Plan is drafted during Starting Up a Project, since the Project Manager must plan how the initiation stage itself will run before the Project Board authorises it. It is one of the process's defined outputs alongside the Project Brief.

Why this answer

In PRINCE2, the Starting Up a Project (SU) process is the pre-project process whose purpose is to ensure the prerequisites for initiating the project are in place, and its two key outputs are the Project Brief (E) and the Initiation Stage Plan (D). The Project Brief (E) is correct because it captures the project's baseline requirements, outline business case, and project definition, and it is the trigger for the Initiating a Project process. The Initiation Stage Plan (D) is correct because SU must plan the work needed to produce the Project Initiation Documentation during the initiation stage, including its activities, resources, and tolerances.

The Project Initiation Documentation (A) is not produced in SU; it is created during the Initiating a Project process. The End Stage Report (B) is produced during Managing a Stage Boundary, and the Stage Plan for the next stage (C) is also produced during Managing a Stage Boundary, not during Starting Up a Project.

Exam trap

PeopleCert often tests the distinction between outputs of Starting Up a Project versus Initiating a Project, specifically confusing the Project Brief (SU) with the Project Initiation Documentation (IP) and the Initiation Stage Plan (SU) with a Stage Plan for a subsequent stage (SB).

Full explanation →

949

MCQhard

A risk has been identified that could cause a delay to the project. The project team decides to purchase insurance to cover the financial impact. Which risk response type is this?

A.Transfer

B.Avoid

C.Accept

D.Reduce

AnswerA

Transfer shifts the financial impact of a risk to a third party. Purchasing insurance moves the potential cost of the delay to the insurer, so the risk response type is transfer, matching the scenario's insurance-based mitigation.

Why this answer

Transferring the financial impact to a third party (insurance) is a 'transfer' response. 'Reduce' would involve actions to lower probability or impact. 'Accept' would be to take the risk without action.

Full explanation →

950

Multi-Selectmedium

Which TWO roles are optional in the PRINCE2 project management team?

Select 2 answers

A.Senior User

B.Project Manager

C.Team Manager

D.Project Support

E.Change Authority

AnswersD, E

Optional administrative support role.

Why this answer

In PRINCE2, the Project Support role is optional because it provides administrative and advisory services to the project management team, but the project can operate without a dedicated person in this role if the Project Manager or other team members absorb those tasks. Similarly, the Change Authority is optional because it is only needed when the project delegates authority for change decisions; if the Project Board retains full change control, no separate Change Authority is required.

Exam trap

The trap here is that candidates often assume all roles listed in the PRINCE2 management team are mandatory, but PRINCE2 explicitly allows Project Support and Change Authority to be optional, while Team Manager is also optional but not part of the correct answer pair in this question.

Full explanation →

951

Multi-Selectmedium

Which TWO of the following are steps in the PRINCE2 risk management procedure?

Select 2 answers

A.Monitor

B.Implement

C.Assess

D.Control

E.Allocate

AnswersB, C

Implement is the fourth step of the PRINCE2 risk management procedure, following Identify, Assess and Plan. It covers assigning owners, executing the planned responses and monitoring their effect, satisfying the stem's requirement for a genuine procedure step rather than a general management activity.

Why this answer

In PRINCE2, the risk management procedure consists of five steps: Identify, Assess, Plan, Implement, and Communicate. Option B (Implement) is correct because it is the step where the planned risk responses are put into action, including assigning owners and executing the agreed actions. Option C (Assess) is correct because it covers the evaluation of risks by estimating their probability and impact and then evaluating their overall severity to prioritize them.

Option A (Monitor) is not a named step in the PRINCE2 risk procedure; monitoring is embedded within the Implement and Communicate steps rather than being a standalone step. Option D (Control) is not a PRINCE2 risk procedure step; it belongs to other frameworks or to the general concept of controlling a project, not this specific procedure. Option E (Allocate) is not a PRINCE2 risk procedure step; allocating risk ownership occurs within the Implement step, but 'Allocate' itself is not one of the five named steps.

Full explanation →

952

MCQhard

A project is nearing the end of a stage, and the Project Manager is preparing for the End Stage Report. The Project Board has requested assurance that the project remains viable. Which of the following should the Project Manager include in the End Stage Report to address this?

A.A detailed list of all risks that have been closed during the stage.

B.A summary of the stage's performance against its tolerances and an updated Business Case.

C.A copy of the Project Initiation Documentation with any changes highlighted.

D.The Quality Register showing all quality activities completed during the stage.

AnswerB

The End Stage Report should include a summary of the stage's performance against its tolerances and an updated Business Case to provide assurance that the project remains viable. The Business Case is reviewed at each stage boundary to confirm that the project is still justified. This addresses the Project Board's need for assurance on viability.

Why this answer

The End Stage Report should provide the Project Board with a summary of stage performance against tolerances and an updated Business Case. The Business Case is the key document for assessing whether the project remains viable and should continue. Other documents, such as the Quality Register or Risk Register, may be referenced but are not the primary means of providing assurance on viability.

Exam trap

The trap here is focusing on operational documents like the Quality Register or Risk Register instead of the Business Case, which is central to assessing project viability.

Full explanation →

953

MCQeasy

During the Initiating a Project process, the project manager is reviewing the Business Case. Which statement best describes the purpose of this review?

A.To confirm the project's scope and high-level risks before the project mandate is issued.

B.To authorize work packages for the first stage of the project.

C.To develop a detailed justification for the project and confirm it remains viable.

D.To obtain final approval from the project board before project execution begins.

AnswerC

Reviewing the Business Case during Initiating a Project develops the detailed justification that the outline Business Case only sketched, and confirms the project remains viable against the baseline. This satisfies the stem's requirement to establish the Business Case before the project board authorises the Project Initiation Documentation.

Why this answer

During the Initiating a Project process, the Business Case is reviewed to develop a detailed justification for the project and confirm it remains viable. This involves refining the outline Business Case from the Starting Up a Project process into a fully detailed document that justifies the project's continued existence based on costs, benefits, risks, and timescales. The review ensures the project is still aligned with corporate objectives and that the investment is worthwhile before proceeding to the next stage.

Exam trap

The trap here is that candidates often confuse the purpose of the Initiating a Project process with the Directing a Project process, mistakenly thinking that the Business Case review is for final approval rather than for developing and confirming viability.

How to eliminate wrong answers

Option A is wrong because the project scope and high-level risks are confirmed during the Starting Up a Project process, not during the Initiating a Project process, and the project mandate is issued before the Initiating a Project process begins. Option B is wrong because authorizing work packages for the first stage occurs during the Managing a Stage Boundary process or the Controlling a Stage process, not during the Initiating a Project process. Option D is wrong because obtaining final approval from the project board before project execution begins is the purpose of the Directing a Project process when the project board decides to authorize the project, not a review of the Business Case within the Initiating a Project process.

Full explanation →

954

MCQhard

During the Managing a Stage Boundary process, the Project Manager reviews the Business Case and finds that the expected benefits are no longer achievable. What should the Project Manager do?

A.Create an Exception Plan to revise the benefits

B.Continue with the next stage as planned and report the issue in the End Project Report

C.Recommend to the Project Board that the project should be closed as the Business Case is no longer viable

D.Close the project immediately without consulting the Project Board

AnswerC

When the Business Case is no longer viable, the Project Manager cannot unilaterally continue or amend it. Under PRINCE2, they must escalate by recommending project closure to the Project Board, which owns the decision to stop the project.

Why this answer

During Managing a Stage Boundary, if the Business Case is no longer viable because expected benefits cannot be achieved, the Project Manager must recommend closure to the Project Board. The Board is the only body with the authority to close the project, and the Project Manager's role is to provide the recommendation with supporting analysis. This upholds the PRINCE2 principle of continued business justification.

Exam trap

PRINCE2F often tests the misconception that the Project Manager can close a project or that an Exception Plan can revive an invalid Business Case, when in fact only the Project Board can close and viability must be recommended, not assumed.

How to eliminate wrong answers

Option A is wrong because an Exception Plan is used to address a forecast tolerance breach, not to revise benefits that are no longer achievable — if the Business Case is fundamentally invalid, an Exception Plan cannot fix it. Option B is wrong because continuing with the next stage when the Business Case is no longer viable violates the continued business justification principle and wastes resources. Option D is wrong because the Project Manager does not have the authority to close the project unilaterally; closure is a Project Board decision.

Full explanation →

955

MCQmedium

A Project Manager receives a forecast that a Work Package will exceed its tolerance. What should the PM do?

A.Discuss with the Team Manager to understand the situation and consider options

B.Inform the Senior Supplier and request additional resources

C.Immediately raise an Exception Report to the Project Board

D.Update the Stage Plan with the new forecast

AnswerA

Tolerance breaches are escalated, but the PM first works with the Team Manager to establish cause and evaluate corrective options. That discussion feeds an Exception Report to the Project Board, which decides; unilateral action exceeds the PM's authority.

Why this answer

In PRINCE2, when a Work Package is forecast to exceed its tolerance, the Project Manager must first discuss with the Team Manager to understand the situation and explore options. This aligns with the 'manage by exception' principle, where the PM is responsible for managing within stage tolerances and only escalates to the Project Board if the stage tolerance itself is threatened. The PM must gather detailed information before deciding on corrective actions or escalation.

Exam trap

The trap here is confusing Work Package tolerance with stage tolerance, leading candidates to immediately escalate to the Project Board (Option C) when the correct first step is to discuss with the Team Manager.

How to eliminate wrong answers

Option B is wrong because the PM should not directly inform the Senior Supplier or request additional resources without first understanding the situation and assessing options; the Senior Supplier is a Project Board role, and resource requests must be managed through the stage plan and exception process. Option C is wrong because an Exception Report is only raised when the stage tolerance is forecast to be exceeded, not a Work Package tolerance; the PM must first attempt to resolve within stage tolerance. Option D is wrong because updating the Stage Plan with the new forecast is premature and incorrect; the Stage Plan is a baseline that should only be changed via an approved Exception Plan.

Full explanation →

956

Drag & Dropmedium

Drag and drop the steps to manage a stage boundary in PRINCE2 into the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Managing a Stage Boundary: plan next stage, update project plan, update business case, report, and produce exception plan if required.

Full explanation →

957

MCQhard

What is the key difference between Project Assurance and quality review?

A.Project Assurance focuses on the Business Case; quality review focuses on the project plan

B.Project Assurance is a role; quality review is a technique

C.Project Assurance is performed by the Project Manager; quality review is performed by the team

D.Project Assurance is done at the end of a stage; quality review is done continuously

AnswerB

Project Assurance is a defined role with assigned responsibilities, whereas a quality review is a technique applied to products. This axis of difference — role versus technique — directly answers what distinguishes the two, rather than their timing, scope or who performs them.

Why this answer

In PRINCE2, Project Assurance is defined as a role (or set of responsibilities) assigned to individuals who monitor the project on behalf of the Business, User, and Supplier interests, ensuring the project remains viable and aligned with the Business Case. Quality review, by contrast, is a technique — specifically a quality inspection technique used within the 'Quality' theme to assess whether products meet their quality criteria. The distinction is therefore one of category: a role versus a technique, not a focus area, performer, or timing.

Exam trap

PRINCE2F often tests the categorical distinction between PRINCE2 elements — candidates lose marks by assuming Project Assurance is a process or activity rather than a role, and by confusing quality review with a phase gate rather than a technique.

How to eliminate wrong answers

Option A is wrong because Project Assurance does not focus solely on the Business Case — it monitors all aspects of the project (Business Case, plans, risks, quality) on behalf of the three stakeholder interests, and quality review does not focus on the project plan. Option C is wrong because Project Assurance is not performed by the Project Manager — PRINCE2 explicitly requires assurance to be independent of the Project Manager, and quality reviews can involve the Project Manager as well as team members. Option D is wrong because Project Assurance is a continuous activity throughout the project, not something done only at the end of a stage, and quality reviews occur at planned points when products are ready for assessment, not continuously.

Full explanation →

958

MCQmedium

Which of the following distinguishes a Highlight Report from a Checkpoint Report?

A.The Checkpoint Report is produced by the Project Manager, while the Highlight Report is produced by the Team Manager

B.The Highlight Report is produced at the end of each stage, while the Checkpoint Report is produced monthly

C.The Highlight Report includes a summary of risks, while the Checkpoint Report does not

D.The Highlight Report is sent to the Project Board, while the Checkpoint Report is sent to the Project Manager

AnswerD

Highlight Reports flow to the Project Board, satisfying the stem's requirement to distinguish the two by audience. Checkpoint Reports travel from Team Manager to Project Manager, covering work package progress at agreed frequencies. This recipient axis — Board versus Project Manager — is the defining difference, not content, timing or authorship.

Why this answer

In PRINCE2, the Highlight Report is a formal report from the Project Manager to the Project Board, providing a summary of progress, risks, and issues at predefined intervals during a stage. The Checkpoint Report is produced by the Team Manager for the Project Manager, detailing progress against the Work Package. This distinction in audience and purpose is a core PRINCE2 principle.

Exam trap

PeopleCert often tests the confusion between the producer and recipient of these reports, especially the misconception that the Checkpoint Report goes to the Project Board or that the Highlight Report is produced by the Team Manager.

How to eliminate wrong answers

Option A is wrong because it reverses the roles: the Checkpoint Report is produced by the Team Manager, while the Highlight Report is produced by the Project Manager. Option B is wrong because the Highlight Report is produced at intervals defined in the stage plan (not necessarily at the end of each stage), and the Checkpoint Report frequency is also defined in the Work Package (not necessarily monthly). Option C is wrong because both reports can include a summary of risks and issues; the Highlight Report always includes a risk summary, but the Checkpoint Report may also include risks relevant to the Work Package.

Full explanation →

959

MCQeasy

A project team is working on a complex infrastructure project. The project manager wants to ensure that the project is tailored appropriately. According to PRINCE2, which principle addresses the need to adapt PRINCE2 to the project's specific context?

A.Continued business justification

B.Focus on products

C.Manage by stages

D.Tailor to suit the project environment

AnswerD

Tailoring is the PRINCE2 principle requiring the method to be adapted to the project's size, complexity, importance, capability and risk. For a complex infrastructure project, this principle justifies scaling processes, roles and documentation to fit the specific context rather than applying PRINCE2 rigidly.

Why this answer

The 'Tailor to suit the project environment' principle directly addresses the need to adapt PRINCE2 to the specific context of the project, including its size, complexity, importance, capability, and risk. For a complex infrastructure project, this means adjusting management products, roles, and processes (e.g., simplifying the Business Case or using a more detailed Risk Register) to fit the project's unique technical and organizational environment, ensuring the method remains effective without being overly burdensome.

Exam trap

PeopleCert often tests the distinction between the 'Tailor to suit the project environment' principle and the 'Manage by stages' principle, as candidates may confuse adapting the method's processes with the structural decision to break the project into stages.

How to eliminate wrong answers

Option A is wrong because 'Continued business justification' ensures the project remains viable and aligned with business objectives, but it does not address the adaptation of PRINCE2 to the project's specific context. Option B is wrong because 'Focus on products' emphasizes defining and delivering products with agreed quality criteria, not tailoring the method itself. Option C is wrong because 'Manage by stages' involves planning, monitoring, and controlling the project in stages, which is a structural element of PRINCE2, not a principle about adapting the method to the project environment.

Full explanation →

960

Multi-Selecthard

Which THREE of the following are types of issue defined in PRINCE2?

Select 3 answers

A.Request for Change

B.Problem/Concern

C.Risk

D.Off-specification

E.Change request

AnswersA, B, D

A Request for Change is one of PRINCE2's three defined issue types, alongside Off-Specification and Problem/Concern. It formally proposes an alteration to baselined products, such as the project plan or business case, satisfying the stem's requirement to identify recognised issue categories rather than general project risks or informal queries.

Why this answer

In PRINCE2, issues are classified into three specific types: Request for Change (A), which proposes a modification to the baselined products or scope; Problem/Concern (B), which covers any other issue raised by a stakeholder that is not a change or an off-specification; and Off-specification (D), which describes a situation where a product will not meet its agreed requirements or specification. These three categories are explicitly defined in the PRINCE2 issue theme and are used to determine how each issue is managed through the issue and change control procedure. Risk (C) is incorrect because it is a separate PRINCE2 theme dealing with uncertainty, not a type of issue.

Change request (E) is incorrect because it is a generic term and not one of the formal PRINCE2 issue types; the formal type is Request for Change.

Full explanation →

961

MCQeasy

In a PRINCE2 project, the Project Manager is preparing the Quality Management Strategy. Which of the following best describes the purpose of this strategy?

A.To describe how the project will manage and control changes to products

B.To record the results of quality activities performed during the project

C.To define the quality methods, procedures, and responsibilities for the project

D.To document the quality checks to be performed for each product

AnswerC

The Quality Management Strategy defines the quality approach for the project, including the quality methods, procedures, techniques, and responsibilities. It ensures that quality is planned and controlled throughout the project, aligning with the PRINCE2 principle of focusing on products and defining quality criteria.

Why this answer

The Quality Management Strategy sets out the project's quality approach, including methods, procedures, and responsibilities. It is a key document in the Quality theme and ensures that quality is built into the project rather than inspected at the end. The other options describe other documents or registers.

Exam trap

The trap here is confusing the Quality Management Strategy with the Quality Register, which records quality activities and results.

Full explanation →

962

MCQmedium

During which process does the Project Board authorize the project to proceed?

A.Controlling a Stage

B.Starting Up a Project

C.Directing a Project

D.Initiating a Project

AnswerC

Directing a Project is the process in which the Project Board provides overall direction and authorises the project to proceed, including approval of the Project Initiation Documentation and each stage boundary. Authorisation to proceed therefore sits with the board during this process.

Why this answer

Directing a Project. This process is where the Project Board makes key decisions and authorizes the project to proceed. Specifically, after the Initiating a Project process produces the Project Initiation Documentation, the Project Board reviews it and gives authorization to proceed with the project during the Directing a Project process.

This formal authorization grants the Project Manager authority to start the first delivery stage.

Exam trap

Candidates often confuse the Initiating a Project and Directing a Project processes. They may think authorization to proceed occurs during Initiating a Project (where the Project Board approves the Initiation Stage Plan), but in PRINCE2, the formal authorization to proceed with the project is given during the Directing a Project process when the Project Board authorizes the Project Initiation Documentation.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage is the process for monitoring and managing work within an already-authorized stage, not for authorizing the project to start. Option B is wrong because Starting Up a Project is a pre-project process that only produces the Project Mandate and appoints the Executive and Project Manager, but does not include authorization to proceed; that occurs later. Option C is wrong because Directing a Project is the process that covers the Project Board's overall decision-making, including authorizations, but the specific authorization to proceed with the project happens during the Initiating a Project process, not as a standalone activity within Directing a Project.

Full explanation →

963

MCQmedium

A Project Manager is setting up the project's organization and assigns a colleague to provide independent scrutiny of the project's products and processes on behalf of the Senior User, ensuring the project meets the user's needs. Which PRINCE2 role has been assigned?

A.Project Assurance

B.Senior Supplier

C.Project Support

D.Team Manager

AnswerA

Project Assurance is the correct role. It provides independent oversight of the project on behalf of the Project Board, ensuring that the project's products and processes meet the interests of the Business, User, and Supplier. In this scenario, the colleague is acting specifically on behalf of the Senior User, which is a valid application of Project Assurance, and the role is independent of the Project Manager.

Why this answer

Project Assurance is the role that provides independent scrutiny of the project's products and processes on behalf of the Project Board, including the Senior User. The other roles are not focused on independent oversight: Project Support is administrative, Team Manager manages product delivery, and Senior Supplier represents the supplier's interests. Assigning a colleague to assure the project on behalf of the Senior User matches the Project Assurance role.

Exam trap

The trap here is confusing Project Assurance with Project Support, since both may involve checking project information, but only Project Assurance is an independent oversight role on behalf of the Project Board.

Full explanation →

964

MCQmedium

During the Initiating a Project process, which document is created that defines how the project will be controlled?

A.Business Case

B.Project Brief

C.Stage Plan

D.Project Initiation Documentation (PID)

AnswerD

The Project Initiation Documentation assembles the project definition, business case, plans and controls, and is the baseline against which the Project Board authorises and subsequently directs the project, satisfying the need for a single controlling document.

Why this answer

The Project Initiation Documentation (PID) is the key document created during the Initiating a Project process that defines how the project will be controlled. It consolidates the project's scope, objectives, and controls, including the management stages, tolerances, and reporting arrangements, providing a baseline for decision-making and governance throughout the project.

Exam trap

The trap here is confusing the Project Brief (a high-level outline created in Starting Up a Project) with the PID (the detailed control document created in Initiating a Project), as both contain similar elements but serve different purposes and are created at different process stages.

How to eliminate wrong answers

Option A is wrong because the Business Case is created earlier in the Starting Up a Project process and justifies the project's viability, not how it will be controlled. Option B is wrong because the Project Brief is also created in Starting Up a Project and provides a high-level overview of the project, but it does not define the detailed control mechanisms. Option C is wrong because the Stage Plan is created during the Initiating a Project process for the first management stage, but it is a component of the PID, not the overarching document that defines overall project control.

Full explanation →

965

MCQmedium

A project manager is leading a project to develop a new customer relationship management system. The Project Board has set tolerances for time and cost, and the project manager is expected to manage the project within these limits. Which PRINCE2 principle is being applied when the project manager only escalates issues that exceed these tolerances?

A.Manage by exception

B.Learn from experience

C.Tailor to suit the project environment

D.Continued business justification

AnswerA

Manage by exception is the principle that establishes tolerances for the six aspects of project performance (time, cost, scope, quality, risk, and benefits) and delegates authority to the project manager to manage within those tolerances. The project manager only escalates to the Project Board when an exception is forecast, which is exactly what is described in the scenario.

Why this answer

Manage by exception is the PRINCE2 principle that enables the Project Board to set tolerances and delegate authority to the project manager, who then manages within those limits and escalates only when an exception is forecast. This principle ensures efficient use of management time and provides clear escalation paths. In the scenario, the project manager is operating within the time and cost tolerances set by the Project Board, and only escalates issues that exceed these tolerances, which is a direct application of manage by exception.

Exam trap

The trap here is confusing manage by exception with continued business justification, as both involve the Project Board's oversight but address different aspects of governance.

Full explanation →

966

MCQmedium

A Project Manager is midway through a stage when the Team Manager for a work package reports that a specialist product will exceed its agreed tolerance by 15 percent. The stage-level tolerances are still intact. What should the Project Manager do FIRST?

A.Escalate directly to the Project Board by raising an Exception Report.

B.Instruct the Team Manager to stop all work on the work package immediately and await further instruction.

C.Record the deviation in the Issue Register and take corrective action within the stage, consulting the Team Manager.

D.Amend the Business Case to reflect the increased cost before any further work continues.

AnswerC

Because the stage-level tolerance remains intact, the deviation is a work package issue that the Project Manager can manage. Capturing it in the Issue Register preserves the audit trail, and taking corrective action with the Team Manager keeps delivery within the authorised stage boundary without unnecessary escalation.

Why this answer

Within a stage, the Project Manager owns the authority to handle issues that do not threaten stage or project tolerances. The correct approach records the deviation formally and applies corrective action with the Team Manager, keeping the response proportionate. Escalation, halting work, or rewriting the Business Case all overreact to a contained work package variance.

Exam trap

The trap here is assuming any reported deviation automatically requires an Exception Report, when escalation is only triggered by a forecast breach of stage or project tolerances.

Full explanation →

967

MCQmedium

The Project Board is meeting to authorize the start of a new stage. According to PRINCE2, how frequently should the Project Board meet?

A.At stage boundaries and when an exception is raised

B.Weekly

C.At the start and end of the project only

D.Monthly

AnswerA

PRINCE2 defines Project Board meetings as event-driven rather than scheduled: the Board convenes at each stage boundary to authorise the next stage, and whenever an exception is raised requiring a decision beyond the Project Manager's tolerance. Regular calendar intervals are not mandated by the method.

Why this answer

PRINCE2 does not mandate a fixed meeting cadence for the Project Board; instead, it specifies that the Board should meet at key decision points — primarily at stage boundaries to authorize the next stage, and additionally when an Exception Report is raised requiring a decision. This aligns with the 'manage by exception' principle, where the Board intervenes only at defined control points or when tolerances are threatened.

Exam trap

The trap is assuming PRINCE2 prescribes a calendar-based meeting frequency like weekly or monthly — candidates pick a familiar cadence, but PRINCE2 ties Board meetings to stage boundaries and exception events, not fixed intervals.

How to eliminate wrong answers

Option B is wrong because weekly meetings are not a PRINCE2 requirement and would contradict the manage-by-exception philosophy of minimizing Board involvement to decision points. Option C is wrong because the Board must authorize each stage, not just project start and closure — meeting only at project start/end would leave intermediate stages unauthorized. Option D is wrong because monthly meetings are an arbitrary cadence not prescribed by PRINCE2; frequency is driven by stage boundaries and exceptions, not the calendar.

Full explanation →

968

MCQeasy

You are a project manager for a PRINCE2 project to develop a new mobile application. The project board has asked you to clarify the roles and responsibilities for the project. Which PRINCE2 principle emphasizes that the project must have a defined organization structure with clear accountability?

A.Defined roles and responsibilities

B.Business justification

C.Tailor to suit the project environment

D.Manage by stages

AnswerA

Defined roles and responsibilities is one of the seven PRINCE2 principles. It requires that the project has a clear organizational structure with defined roles, responsibilities, and relationships. This ensures that all stakeholders know who is accountable for what, which is essential for effective decision-making and project governance. The project board, project manager, and team manager roles are key examples.

Why this answer

PRINCE2 includes seven principles, one of which is 'defined roles and responsibilities.' This principle ensures that a project has a clear organizational structure with defined roles, responsibilities, and relationships. It requires that all parties know what is expected of them and who is accountable for what. This is fundamental for effective governance and decision-making, and it is directly related to the project board, project manager, and team manager roles.

Exam trap

The trap here is confusing the principle of defined roles and responsibilities with other principles like business justification or manage by stages, which address different aspects of project management.

Full explanation →

969

MCQeasy

A project manager is leading a project to implement a new CRM system. The project board has defined roles and responsibilities, and the project manager is accountable for day-to-day management. Which PRINCE2 principle is being applied when the project manager ensures that the project has clearly defined roles and responsibilities for all stakeholders?

A.Defined roles and responsibilities

B.Manage by exception

C.Tailor to suit the project environment

D.Focus on products

AnswerA

This is correct because the principle of defined roles and responsibilities requires that all members of the project team, including the project board, project manager, team managers, and other stakeholders, have clearly defined roles and responsibilities. This ensures accountability and effective decision-making. In this scenario, the project manager is applying this principle by ensuring clarity of roles and responsibilities.

Why this answer

The correct answer is the principle of defined roles and responsibilities. PRINCE2 requires that every project has a clear organizational structure with defined roles, such as the project board, project manager, and team managers. This ensures that everyone knows what they are accountable for and who makes decisions.

The other principles address different aspects of project management, such as decision-making boundaries, product focus, and adaptation.

Exam trap

The trap here is confusing the principle of defined roles and responsibilities with manage by exception, as both involve clear accountability but focus on different aspects.

Full explanation →

970

MCQhard

Which PRINCE2 principle is being applied when the Project Manager escalates a forecast tolerance deviation to the Project Board?

A.Defined Roles and Responsibilities

B.Learn from Experience

C.Manage by Exception

D.Continued Business Justification

AnswerC

Manage by Exception defines tolerances for time, cost, scope, quality, risk and benefits, empowering the Project Board to set boundaries and requiring the Project Manager to escalate only when a forecast breach exceeds delegated authority.

Why this answer

The 'Manage by Exception' principle is applied when the Project Manager escalates a forecast tolerance deviation to the Project Board. This principle delegates decision-making authority within defined tolerances; only when a deviation is forecast to exceed those tolerances does the Project Manager escalate to the Project Board for a decision. The escalation triggers exception management, ensuring the board retains control at key decision points without micromanaging day-to-day activities.

Exam trap

The trap here is that candidates confuse 'Manage by Exception' with 'Defined Roles and Responsibilities', because escalation involves roles, but the principle specifically governing tolerance-based escalation is 'Manage by Exception', not role definition.

How to eliminate wrong answers

Option A is wrong because 'Defined Roles and Responsibilities' ensures each team member knows their duties and authority levels, but it does not specifically address the escalation of tolerance deviations; that is the function of 'Manage by Exception'. Option B is wrong because 'Learn from Experience' focuses on capturing and applying lessons throughout the project, not on the escalation mechanism for tolerance breaches. Option D is wrong because 'Continued Business Justification' requires ongoing validation that the project remains viable, but it does not prescribe the escalation process for tolerance deviations; that is handled by 'Manage by Exception'.

Full explanation →

971

MCQmedium

The Project Board has received an Exception Report from the Project Manager. What is the Project Board's next step?

A.Approve the Exception Report

B.Request a new Project Plan

C.Request an Exception Plan to assess options

D.Close the project

AnswerC

An Exception Report shows the stage or project will exceed tolerance, so the Project Board requests an Exception Plan describing the options and their implications. The Board then decides whether to approve, amend or stop the project.

Why this answer

When the Project Board receives an Exception Report, they typically request an Exception Plan to evaluate options. They then decide whether to approve the plan, which may involve changes to the project. A new Project Plan may be part of the Exception Plan, but the immediate step is to request the plan.

Full explanation →

972

MCQeasy

A project manager is setting up a new project and wants to ensure that the project has clearly defined roles and responsibilities. According to PRINCE2, which principle requires that the project has a defined organization structure with accountable roles?

A.Defined roles and responsibilities

B.Manage by stages

C.Tailor to suit the project environment

D.Learn from experience

AnswerA

Defined roles and responsibilities is the PRINCE2 principle that requires a clear organizational structure with defined roles, responsibilities, and relationships. It ensures that all stakeholders understand who is accountable for what, and that the project has the necessary decision-making bodies, such as the project board. This principle directly supports the need for accountable roles in the project organization.

Why this answer

The PRINCE2 principle 'defined roles and responsibilities' requires that the project has a clear organizational structure with defined roles, responsibilities, and relationships. It ensures that all parties know what is expected of them and that there is accountability for decisions. This principle is fundamental to establishing the project board and project manager roles, and it supports effective governance throughout the project lifecycle.

Exam trap

The trap here is confusing the principle of defined roles and responsibilities with other principles that also relate to project setup, such as manage by stages or tailor to suit the project environment.

Full explanation →

973

MCQeasy

A Project Manager is preparing the organization structure for a new project. The Executive has asked who will be responsible for representing the interests of the people who will use the project's products and for ensuring that the products will meet their needs. Which role should the Project Manager identify?

A.Project Assurance

B.Project Manager

C.Senior Supplier

D.Senior User

AnswerD

The Senior User is the Project Board role responsible for specifying the needs of the users and for monitoring that the solution will meet those needs within the constraints of the Business Case. This role represents the user community and ensures that the project delivers the expected outcomes. Therefore, the Senior User is the correct role to identify for this responsibility.

Why this answer

The Senior User is the Project Board role that represents the user community, specifies their needs, and monitors that the solution will meet those needs within the Business Case constraints. The Senior Supplier focuses on supplier interests, Project Assurance provides independent oversight, and the Project Manager handles day-to-day management. Thus, the Senior User is the correct role.

Exam trap

The trap here is confusing the Senior User's responsibility for user needs with the Senior Supplier's technical focus or the Project Manager's delivery focus.

Full explanation →

974

MCQmedium

What is the purpose of a Checkpoint Report?

A.To document lessons learned

B.To report progress of a Work Package from the Team Manager to the Project Manager

C.To inform the Project Board of stage progress

D.To escalate issues to the Project Board

AnswerB

The Team Manager owns the Work Package and reports its progress, status and issues to the Project Manager at each checkpoint. This satisfies the stem's requirement for reporting Work Package progress upward, distinct from Highlight Reports, which cover the whole project.

Why this answer

The Checkpoint Report is a PRINCE2 management product used by the Team Manager to report progress of a Work Package to the Project Manager. Its purpose is to provide regular, detailed progress updates on the work being performed by the team, ensuring the Project Manager can monitor delivery against the Work Package plan. This is distinct from higher-level reports like the End Stage Report or Highlight Report.

Exam trap

PeopleCert often tests the distinction between reports directed at different management levels; the trap here is confusing the Checkpoint Report (team-level to Project Manager) with the Highlight Report (Project Manager to Project Board).

How to eliminate wrong answers

Option A is wrong because lessons learned are formally captured in the Lessons Log and Lessons Report, not in a Checkpoint Report. Option C is wrong because informing the Project Board of stage progress is the purpose of the Highlight Report (or End Stage Report), not the Checkpoint Report. Option D is wrong because escalating issues to the Project Board is done via an Exception Report or Issue Report, not the Checkpoint Report.

Full explanation →

975

MCQhard

A PRINCE2 project is nearing the end of a stage. The project manager has received all Checkpoint Reports and completed the stage's products. The project manager now needs to prepare for the next stage. According to PRINCE2, which activity is performed in the Managing a Stage Boundary process?

A.Authorize a work package to the Team Manager for the next stage

B.Request authorization to start the next stage from the Project Board

C.Produce a Highlight Report for the Project Board

D.Produce an Exception Report if the stage is forecast to exceed its tolerances

AnswerB

Managing a Stage Boundary includes preparing the End Stage Report and Next Stage Plan, and requesting Project Board authorization to proceed to the next stage. This is a key activity that ensures the Project Board maintains control at stage boundaries.

Why this answer

In Managing a Stage Boundary, the project manager prepares the End Stage Report and Next Stage Plan, then requests the Project Board's authorization to start the next stage. This process ensures that the project remains viable and that the next stage is properly planned before work begins, maintaining the principle of manage by stages.

Exam trap

The trap here is mixing up the outputs of Controlling a Stage with those of Managing a Stage Boundary, such as confusing Exception Reports or Highlight Reports with the End Stage Report.

Full explanation →

Page 13 of 16

All pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Practice PRINCE2F by domain

Target a specific domain to shore up weak areas.

Overview of PRINCE2 and Principles PRINCE2 Practices Overview of PRINCE2 and the project environment Project Initiation and Stages Business Case and Organizing People: organizations, teams, and leadership PRINCE2 Processes

See all domains with question counts →