PRINCE2 Foundation PRINCE2F Questions 1051–1125 | Page 15/16

1051

MCQhard

A Team Manager identifies a quality problem in a product that is being delivered. What should the Team Manager do?

A.Record the problem and inform the Project Manager

B.Update the Checkpoint Report and ignore the problem

C.Reject the product and stop all work

D.Fix the product immediately to meet quality criteria

AnswerA

The Team Manager records the quality problem in the daily log and informs the Project Manager, since quality issues affecting a Work Package fall outside the Team Manager's authority and require Project Manager assessment against stage tolerances.

Why this answer

When a Team Manager identifies a quality problem, PRINCE2 requires them to record it (typically in the Quality Register) and inform the Project Manager, who owns the Quality Register and decides on corrective action. The Team Manager does not have authority to change scope, quality tolerances, or the product's specification unilaterally. Escalating ensures the issue is handled within the project's quality and change control framework.

Exam trap

The trap is assuming the Team Manager should 'just fix it' or 'reject the product' — PRINCE2 emphasizes escalation and formal recording over unilateral action, and candidates often pick the most decisive-sounding option rather than the role-appropriate one.

How to eliminate wrong answers

Option B is wrong because ignoring a quality problem is never acceptable; the Checkpoint Report may mention progress, but the issue must be formally recorded and escalated. Option C is wrong because rejecting the product and stopping all work exceeds the Team Manager's authority and would disrupt the stage without Project Manager or board involvement. Option D is wrong because fixing the product immediately may breach the agreed quality criteria or baseline, and any change must go through the Project Manager and, if necessary, change control.

Full explanation →

1052

Drag & Dropmedium

Drag and drop the steps to manage a risk 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

The PRINCE2 risk management procedure follows: identify, assess, plan responses, implement, and monitor.

Full explanation →

1053

MCQeasy

A project is in the Initiation Stage. The Project Manager is preparing the Project Initiation Documentation and needs to include the project's quality management approach. Which document defines how the project will ensure that products meet their quality requirements?

A.The Project Plan

B.The Product Description

C.The Quality Management Approach

D.The Quality Register

AnswerC

The Quality Management Approach defines the quality standards, procedures, and responsibilities for the project. It describes how quality will be planned, controlled, and assured, including the use of quality criteria, quality methods, and quality registers. It is a key component of the Project Initiation Documentation and ensures that products meet their requirements.

Why this answer

The Quality Management Approach defines how the project will ensure that products meet their quality requirements. It includes quality standards, procedures, and responsibilities, and is part of the Project Initiation Documentation. Product Descriptions, the Quality Register, and the Project Plan support quality management but do not replace the overall approach.

Exam trap

The trap here is selecting the Quality Register or a Product Description because they are quality-related, but only the Quality Management Approach defines the project-wide quality framework.

Full explanation →

1054

MCQeasy

When should the Project Board meet?

A.At stage boundaries and when an exception occurs

B.Only at the end of the project

C.Daily

D.Weekly

AnswerA

PRINCE2 mandates Project Board meetings at each stage boundary to authorise the next stage, and whenever an exception is raised, so the Board can decide how to recover. This satisfies the stem's governance requirement for decision points rather than continuous attendance.

Why this answer

The Project Board is responsible for key decision points in the PRINCE2 methodology. It meets at stage boundaries to review progress, approve the next stage plan, and ensure continued business justification. It also meets when an exception occurs (i.e., when a stage plan deviates beyond tolerance) to decide on corrective action, such as approving an exception plan or prematurely closing the project.

Exam trap

A common misconception is that the Project Board meets regularly (e.g., weekly or daily) like a Scrum daily stand-up, but PRINCE2 specifically limits board meetings to stage boundaries and exception events to preserve management by exception.

How to eliminate wrong answers

Option B is wrong because the Project Board does not only meet at the end of the project; it must meet at stage boundaries and during exceptions to provide ongoing governance. Option C is wrong because daily meetings would be impractical and unnecessary for a board that focuses on strategic decisions, not operational management. Option D is wrong because weekly meetings are not prescribed by PRINCE2; the board meets only at defined control points (stage boundaries and exceptions) to avoid micromanagement.

Full explanation →

1055

MCQmedium

In which process are Work Packages authorized and progress reviewed by the Project Manager?

A.Directing a Project

B.Controlling a Stage

C.Managing a Stage Boundary

D.Managing Product Delivery

AnswerB

Controlling a Stage is where the Project Manager authorises Work Packages, monitors progress, reviews completed work and handles issues and risks. Managing Product Delivery is the Team Manager's process, so authorisation and progress review sit squarely within Controlling a Stage.

Why this answer

The Controlling a Stage process is where the Project Manager authorizes Work Packages to Team Managers and reviews their progress against the stage plan. This process ensures that work is executed, monitored, and controlled within the current stage, with the Project Manager managing day-to-day activities and escalating issues as needed.

Exam trap

The trap here is confusing the Project Manager's role in Controlling a Stage with the Team Manager's role in Managing Product Delivery, where candidates mistakenly think Work Package authorization happens in the latter process instead of the former.

How to eliminate wrong answers

Option A is wrong because Directing a Project is the process for the Project Board to make key decisions, authorize the project, and provide overall direction, not for authorizing Work Packages or reviewing progress at the detailed level. Option C is wrong because Managing a Stage Boundary focuses on planning the next stage and updating the business case, not on authorizing or reviewing Work Packages. Option D is wrong because Managing Product Delivery is the process where the Team Manager accepts and executes Work Packages and reports progress to the Project Manager, but the authorization and review of Work Packages are done by the Project Manager in Controlling a Stage.

Full explanation →

1056

MCQhard

A Project Manager is leading a project in which the Senior User is unable to attend Project Board meetings regularly. The Project Manager needs a decision on a change to a product's specification that affects the user community. Who should the Project Manager approach to ensure that user interests are represented in the decision?

A.The Executive, because they are ultimately accountable for the project

B.The Senior Supplier, because they represent the supplier's interests

C.The Senior User's delegated representative, if one has been appointed

D.The Project Assurance role, because they monitor all aspects of the project

AnswerC

The Senior User is accountable for specifying the needs of those who will use the project's products and for ensuring that the solution meets those needs. If the Senior User cannot attend, PRINCE2 allows them to delegate their responsibilities to a representative. That representative can then provide the user perspective on the change, ensuring user interests are considered. This is the correct approach when the Senior User is unavailable.

Why this answer

The Senior User is accountable for representing the user community and specifying their needs. When the Senior User cannot attend, PRINCE2 permits delegation of their responsibilities to a representative. That representative can then make decisions or provide input on changes affecting users, ensuring that user interests are properly represented without requiring the Senior User's personal attendance.

Exam trap

The trap here is assuming that the Executive or Project Assurance can substitute for the Senior User, when only a formally delegated representative carries the user authority.

Full explanation →

1057

MCQmedium

Which process ensures that the project's products are formally handed over to the operational environment?

A.Controlling a Stage

B.Directing a Project

C.Closing a Project

D.Managing Product Delivery

AnswerC

Closing a Project covers the formal handover of products to the operational environment, confirming acceptance and transferring ownership. It is the process where the project manager verifies the products are delivered, accepted and transitioned, then archives the project.

Why this answer

The Closing a Project process is responsible for ensuring that the project's products are formally handed over to the operational environment, as it includes the 'Hand over Products' activity. This process verifies that acceptance criteria are met, obtains formal acceptance, and transfers ownership to the operational team, aligning with PRINCE2's focus on controlled closure.

Exam trap

PRINCE2 candidates often confuse Managing Product Delivery with Closing a Project for the handover; however, Managing Product Delivery only covers delivery of products within the project, not the formal transfer to operations, which is exclusive to Closing a Project.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage focuses on day-to-day management of a stage, including monitoring progress and handling issues, not on the formal handover of products to operations. Option B is wrong because Directing a Project is the decision-making layer for the Project Board, covering authorization and oversight, but it does not execute the operational handover itself. Option D is wrong because Managing Product Delivery is about creating and delivering products within a work package, not about the final handover to the operational environment, which occurs after delivery is complete.

Full explanation →

1058

Multi-Selecthard

A project is being initiated to develop a new customer relationship management (CRM) system. The Project Manager is applying the PRINCE2 principle 'learn from experience'. Which two actions should she take to ensure this principle is applied effectively? (Choose two.)

Select 2 answers

A.Review the lessons log from previous projects to identify relevant lessons that could affect the CRM project.

B.Include a lesson learned in the End Stage Report about the effectiveness of the risk management approach used during the stage.

C.Ensure that the project's Business Case is updated at each stage boundary with actual progress and revised forecasts.

D.Delegate authority to the Project Manager to manage the stage within agreed tolerances.

E.Define the quality criteria for the CRM system's key products in the Product Descriptions.

AnswersA, B

Reviewing the lessons log from previous projects is a key action for applying the learn from experience principle. It ensures that the project benefits from past successes and failures, avoiding repeated mistakes and leveraging proven practices. This is a direct application of the principle, as it involves seeking out and using lessons from similar projects to inform the current project's approach.

Why this answer

The learn from experience principle requires that lessons are sought, recorded, and acted upon throughout the project. Reviewing lessons logs from previous projects ensures that relevant knowledge is considered from the start. Including a lesson learned in the End Stage Report captures current experience for future use.

These two actions directly apply the principle, whereas updating the Business Case, delegating authority, and defining quality criteria relate to other principles.

Exam trap

The trap here is selecting actions that are important in PRINCE2 but belong to other principles, such as continued business justification or focus on products, instead of actions that specifically capture and apply lessons.

Full explanation →

1059

MCQeasy

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

A.To ensure the project idea is viable and the team is in place

B.To authorize the project to proceed

C.To produce the Project Initiation Documentation

D.To plan the entire project in detail

AnswerA

Starting up a Project confirms the project idea is viable and worth initiating, and that the necessary roles and people are available. It produces the Project Brief and appoints the Project Board, satisfying the stem's requirement to check viability and secure the team.

Why this answer

The Starting up a Project process ensures that the project idea is viable and that the necessary team members are in place before any significant work begins. It checks that the project has a clear business justification and that the required resources, including the project manager and key stakeholders, are available to proceed. This process does not authorize the project or produce detailed plans; it simply confirms that the project is worth considering and can be started.

Exam trap

The trap here is that candidates often confuse the Starting up a Project process with the Initiating a Project process in PRINCE2, mistakenly thinking that detailed planning or authorization occurs during startup, when in fact startup only confirms viability and assembles the team.

How to eliminate wrong answers

Option B is wrong because authorizing the project to proceed is the purpose of the Directing a Project process, not Starting up a Project. Option C is wrong because producing the Project Initiation Documentation is the purpose of the Initiating a Project process, which occurs after Starting up a Project. Option D is wrong because planning the entire project in detail is not done in Starting up a Project; detailed planning occurs during the Initiating a Project and subsequent processes, with the Starting up a Project process only creating the Project Brief and Stage Plan for initiation.

Full explanation →

1060

MCQhard

A project manager is preparing the Business Case for a new project. The expected benefits are $500,000, and the expected costs are $400,000. However, there is a high risk that the benefits may be only $300,000 due to market uncertainty. According to PRINCE2 practices, how should the project manager reflect this in the Business Case?

A.Include a cost-benefit analysis showing a range of benefits ($300,000-$500,000) and a risk assessment explaining the market uncertainty.

B.Use the lower benefit estimate of $300,000 to be conservative.

C.Use the expected benefits of $500,000 as the primary figure, with a note that benefits may vary.

D.Omit the risk from the Business Case to avoid discouraging stakeholders.

AnswerA

PRINCE2 requires the Business Case to present benefits and dis-benefits alongside associated risks and their impact. Showing a benefit range of $300,000-$500,000 with a risk assessment captures the market uncertainty, satisfying the practice of justifying continued viability.

Why this answer

PRINCE2 requires the Business Case to be a living document that reflects realistic projections, including uncertainties. By showing a range of benefits ($300,000–$500,000) and a corresponding risk assessment, the project manager provides a balanced view that supports informed decision-making, aligning with the 'continued business justification' principle.

Exam trap

The trap here is that candidates often choose a single 'conservative' estimate (Option B) thinking it is prudent, but PRINCE2 requires transparency through a range and risk assessment rather than hiding uncertainty or oversimplifying the analysis.

How to eliminate wrong answers

Option B is wrong because using only the lower benefit estimate ($300,000) is overly conservative and does not reflect the full potential upside, which could lead to rejecting a viable project; PRINCE2 advocates for a range or sensitivity analysis rather than a single pessimistic figure. Option C is wrong because using $500,000 as the primary figure with only a note downplays the significant risk, failing the PRINCE2 requirement to explicitly evaluate and document risks in the Business Case. Option D is wrong because omitting the risk entirely violates the 'continued business justification' principle and the PRINCE2 requirement that the Business Case must include a risk assessment to support ongoing viability checks.

Full explanation →

1061

MCQhard

What is the key difference between a Request for Change (RFC) and an Off-specification (Off-spec)?

A.An RFC is raised by the Project Board; an Off-spec is raised by the Project Manager

B.There is no difference; they are two names for the same thing

C.An RFC suggests a change to what is specified; an Off-spec reports that something does not meet its specification

D.An RFC is always urgent; an Off-spec is not

AnswerC

An RFC proposes altering the baselined specification, whereas an Off-spec documents a product that has already failed to meet it. The axis is intent: proactive change request versus reactive non-conformance report, so each triggers different PRINCE2 change control handling.

Why this answer

An RFC proposes a modification to an agreed baseline, while an Off-spec is a product not meeting its specification (a deviation).

Full explanation →

1062

MCQeasy

Which role is responsible for implementing the risk responses?

A.The risk actionee

B.The change authority

C.The risk owner

D.The Project Manager

AnswerA

The risk actionee implements agreed risk responses, satisfying the stem's requirement for the role accountable for putting responses into effect. Unlike the risk owner, who monitors and manages the risk overall, the actionee performs the specific tasks assigned within the risk management approach, ensuring planned responses are actually executed.

Why this answer

In PRINCE2, the risk actionee is the person responsible for implementing the risk responses that have been agreed upon. This role is assigned by the risk owner to carry out specific actions to mitigate, transfer, avoid, or accept the risk. The risk actionee reports back to the risk owner on the progress and effectiveness of the response.

Exam trap

Candidates often confuse the risk owner (accountable) with the risk actionee (responsible for implementation). In PRINCE2, the risk owner is accountable for managing the risk, but the risk actionee is the one who actually implements the agreed responses.

How to eliminate wrong answers

Option B is wrong because the change authority is responsible for authorizing changes to project baselines, not for implementing risk responses. Option C is wrong because the risk owner owns the risk and is accountable for managing it, but the actual implementation of responses is delegated to the risk actionee. Option D is wrong because the Project Manager is responsible for the day-to-day management of the project and for ensuring risks are managed, but they do not personally implement every risk response; that task is assigned to the risk actionee.

Full explanation →

1063

MCQhard

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

A.The risk owner is a member of the Project Board; the risk actionee is a team member

B.The risk owner is accountable for the risk; the risk actionee performs the risk response actions

C.The risk owner identifies the risk; the risk actionee implements the response

D.They are the same role

AnswerB

The risk owner is accountable for managing the risk and its response, while the risk actionee carries out the specific response actions assigned to them. Accountability and execution are the distinguishing axis between the two roles.

Why this answer

In PRINCE2, the risk owner is the person accountable for managing a specific risk, including selecting and monitoring the response. The risk actionee is the person assigned to carry out the actual response actions, often under the risk owner's direction. They are distinct roles, though in small projects they may be the same person.

Exam trap

The trap here is conflating accountability with execution — candidates often assume the risk owner performs the response actions, but PRINCE2 separates the accountable owner from the actionee who does the work.

How to eliminate wrong answers

Option A is wrong because neither role is defined by Project Board membership; a risk owner can be any appropriate person, not necessarily a Board member. Option C is wrong because identifying a risk is part of the risk management approach and can be done by anyone, not specifically the risk owner; the risk owner is accountable for managing it, not just identifying it. Option D is wrong because PRINCE2 explicitly distinguishes the two roles: the owner is accountable, the actionee executes.

Full explanation →

1064

Multi-Selectmedium

Which TWO of the following are outputs of the Starting Up a Project process?

Select 2 answers

A.Project Brief

B.Benefits Management Approach

C.Project Initiation Documentation

D.Daily Log

E.End Stage Report

AnswersA, D

The Project Brief is a required output of Starting Up a Project, produced from the Project Mandate and refined by the Project Manager. It satisfies the stem's constraint by being created before the Initiating a Project process begins, establishing the project's baseline definition for subsequent approval by the Project Board.

Why this answer

Option A (Project Brief) is correct because Starting Up a Project (SU) creates the Project Brief as its primary output, capturing the project's outline business case, scope, objectives, and tolerances to feed into Initiating a Project. Option D (Daily Log) is correct because SU also establishes the Daily Log, which the Project Manager uses to record informal issues, actions, and notes throughout the project. Option B (Benefits Management Approach) is not correct because it is produced during Initiating a Project (IP), not SU.

Option C (Project Initiation Documentation) is not correct because the PID is assembled in the Initiating a Project process. Option E (End Stage Report) is not correct because it is created in the Managing a Stage Boundary process at the end of a stage.

Exam trap

PRINCE2F often tests which process owns which product — candidates confuse Starting up a Project with Initiating a Project and incorrectly assign the Benefits Management Approach or PID to the earlier process.

Full explanation →

1065

MCQeasy

In PRINCE2, what is the purpose of the Risk Register?

A.To record lessons learned

B.To record quality review results

C.To record all identified risks and their management

D.To record all issues raised during the project

AnswerC

The Risk Register captures each identified risk, its probability, impact, proximity, owner and planned response, and is maintained throughout the project. This satisfies the stem by providing the single repository through which PRINCE2 manages uncertainty.

Why this answer

The Risk Register in PRINCE2 is the central repository for recording all identified risks (both threats and opportunities) and their ongoing management actions, including analysis, response planning, and status updates. It is a key management product that supports the continuous management of risk throughout the project lifecycle, ensuring that risks are formally captured, assessed, and controlled.

Exam trap

The trap here is that candidates confuse the Risk Register with the Issue Register, as both involve logging and tracking items, but PRINCE2 strictly separates risks (uncertain future events) from issues (current problems or requests for change).

How to eliminate wrong answers

Option A is wrong because lessons learned are recorded in the Lessons Log (and later the Lessons Report), not the Risk Register. Option B is wrong because quality review results are documented in the Quality Register, which tracks quality inspections and their outcomes. Option D is wrong because issues (such as problems, change requests, or off-specifications) are recorded in the Issue Register, not the Risk Register.

Full explanation →

1066

MCQeasy

In a PRINCE2 project, the Project Manager is preparing the Benefits Review Plan. Which of the following best describes the purpose of this document?

A.It defines how and when the project's benefits will be measured and reviewed, both during the project and after project closure.

B.It outlines the project's budget and the forecast costs associated with delivering each benefit.

C.It records the project's risks and the countermeasures to protect the expected benefits from being eroded.

D.It lists the project's products and the quality criteria that must be met to achieve the expected benefits.

AnswerA

The Benefits Review Plan describes the activities to verify that the project's outcomes deliver the expected benefits. It includes timing, responsibilities, and methods for measuring benefits during the project and in the post-project period. This ensures that the Business Case remains valid and that benefits realisation is actively managed beyond the project lifecycle.

Why this answer

The Benefits Review Plan is a PRINCE2 document that specifies how and when benefits will be measured and reviewed, including post-project activities. It ensures that the Business Case is validated through actual benefit realisation. It does not define product quality criteria, budgets, or risks, as those are covered by other management products.

Exam trap

The trap here is confusing the Benefits Review Plan with the Business Case or Quality Management Strategy, leading to the inclusion of cost or quality data that does not belong there.

Full explanation →

1067

Multi-Selecthard

Which TWO of the following statements about the Executive role are correct?

Select 2 answers

A.The Executive chairs the Project Board

B.The Executive approves all Work Packages

C.The Executive manages the project on a day-to-day basis

D.The Executive is responsible for the Business Case

E.The Executive is appointed after the project brief is approved

AnswersA, D

The Executive chairs the Project Board, owning the Business Case and holding ultimate accountability for the project's success. As chair, the Executive drives decision-making and represents the business interest, ensuring the project remains justified and aligned with corporate strategy.

Why this answer

Option A is correct because in PRINCE2 the Executive is the senior responsible owner who chairs the Project Board, owning the 'business' perspective and being accountable for the project's success. Option D is correct because the Executive is specifically accountable for the Business Case, ensuring it demonstrates continuing business justification and viability throughout the project. Option B is incorrect because approving Work Packages is delegated to the Project Manager, not the Executive.

Option C is incorrect because day-to-day management is the Project Manager's responsibility, not the Executive's. Option E is incorrect because the Executive is appointed by the commissioning organization before the project starts, during the Starting up a Project process, not after the Project Brief is approved.

Exam trap

PeopleCert often tests the distinction between the Executive's strategic accountability and the Project Manager's operational responsibility, leading candidates to confuse who approves Work Packages or manages daily tasks.

Full explanation →

1068

MCQhard

In PRINCE2, who owns the risk?

A.Project Manager

B.Executive

C.Risk actionee

D.Risk owner

AnswerD

The risk owner is the named individual accountable for managing a specific risk, its mitigation actions and monitoring. PRINCE2 assigns this role explicitly, distinct from the risk actionee who performs the tasks, ensuring clear ownership within the risk management approach.

Why this answer

In PRINCE2, the risk owner is the person responsible for managing, monitoring, and controlling a specific risk, including implementing the agreed risk response. This role is explicitly defined in the Risk theme and is distinct from the person who performs the response actions. The risk owner is accountable for the risk's management throughout its lifecycle.

Exam trap

PRINCE2F often tests the distinction between risk owner (accountable) and risk actionee (responsible for actions) — candidates conflate the two because both sound like 'the person dealing with the risk'.

How to eliminate wrong answers

Option A is wrong because the Project Manager is responsible for overall risk management across the project but is not the owner of every individual risk — ownership is assigned per risk. Option B is wrong because the Executive is accountable for the business case and overall project success, not for owning individual risks (though they may own strategic risks). Option C is wrong because the risk actionee is the person who carries out the response actions assigned by the risk owner — they implement, but do not own, the risk.

Full explanation →

1069

MCQmedium

The Project Manager has produced an End Stage Report for the current stage. According to PRINCE2, what is the next step?

A.Update the Business Case and close the project

B.Distribute the report to stakeholders and continue to the next stage

C.Seek approval from the Executive to continue

D.Submit the report to the Project Board for a decision on whether to proceed

AnswerD

The End Stage Report goes to the Project Board, which reviews stage performance and authorises the next stage or closure. This satisfies the stem's requirement because only the Board holds the authority to approve progression, exercising the Directing a Project decision point.

Why this answer

In PRINCE2, the End Stage Report is produced by the Project Manager to provide the Project Board with a summary of the stage's performance. The next step is to submit this report to the Project Board, which then decides whether to authorize the next stage, amend the project, or stop the project. Option D correctly reflects this governance checkpoint, as the Project Board holds the authority to approve continued investment.

Exam trap

A common misconception in the PRINCE2 exam is that the Project Manager can unilaterally proceed to the next stage after producing the End Stage Report, when in fact PRINCE2 mandates that the Project Board must formally authorize the next stage.

How to eliminate wrong answers

Option A is wrong because the Business Case is not updated solely from an End Stage Report; it is reviewed and updated as part of the Managing a Stage Boundary process, and closing the project occurs only after the final stage. Option B is wrong because distributing the report to stakeholders is not the immediate next step; the report must first go to the Project Board for a decision, and continuing to the next stage requires explicit authorization. Option C is wrong because approval from the Executive alone is insufficient; PRINCE2 requires collective decision-making by the entire Project Board, not just one member.

Full explanation →

1070

MCQmedium

During the 'Controlling a Stage' process, the Project Manager is monitoring progress. Which of the following is a specific responsibility of the Project Manager in this process?

A.Authorising Work Packages.

B.Appointing the Project Board members.

C.Producing the End Project Report.

D.Approving the Project Initiation Documentation.

AnswerA

Authorising Work Packages is a key responsibility of the Project Manager during the Controlling a Stage process. This involves agreeing the Work Package with the Team Manager, ensuring it includes the necessary product descriptions, quality criteria, and constraints. By authorising Work Packages, the Project Manager delegates work while maintaining control and ensuring that the team has clear instructions.

Why this answer

In the Controlling a Stage process, the Project Manager is responsible for authorising Work Packages, which involves delegating work to Team Managers while ensuring that the work is clearly defined and controlled. This is a core activity that enables the Project Manager to manage progress, deal with issues, and report to the Project Board, maintaining control throughout the stage.

Exam trap

The trap here is confusing responsibilities from different processes, such as approving the Project Initiation Documentation or producing the End Project Report, which occur in other processes.

Full explanation →

1071

MCQmedium

During the Managing Product Delivery process, a Team Manager discovers that a product cannot meet its quality criteria without significant extra work. What should the Team Manager do?

A.Modify the quality criteria to match what can be achieved

B.Raise an issue to the Project Manager for direction

C.Proceed with the work and report the variance in the next Checkpoint Report

D.Inform the Project Board directly

AnswerB

A Work Package that cannot meet its tolerances or quality criteria must be escalated, so the Team Manager raises an issue to the Project Manager, who decides on corrective action within stage tolerances or escalates to the Project Board. The Team Manager cannot unilaterally change agreed scope, cost or quality.

Why this answer

In PRINCE2, the Team Manager works within the constraints set by the Project Manager. When a product cannot meet its quality criteria without significant extra work, the Team Manager must escalate this as an issue to the Project Manager, who has the authority to decide on changes to scope, quality, or budget. This aligns with the 'Manage by Exception' principle and the defined roles in the Managing Product Delivery process.

Exam trap

The trap here is that candidates often think the Team Manager should directly inform the Project Board (Option D) because quality is a board-level concern, but PRINCE2 strictly requires escalation through the Project Manager first.

How to eliminate wrong answers

Option A is wrong because modifying quality criteria without authorization violates the agreed baselines and the Project Manager's authority; only the Project Manager can approve changes to quality criteria. Option C is wrong because proceeding with work that cannot meet quality criteria and deferring reporting to the next Checkpoint Report would hide a critical deviation, violating the principle of timely issue management and exception reporting. Option D is wrong because the Team Manager reports to the Project Manager, not directly to the Project Board; the Project Board is only informed via exception reports escalated by the Project Manager.

Full explanation →

1072

Multi-Selectmedium

Which TWO documents are produced during the Closing a Project process?

Select 2 answers

A.Project Brief

B.Lessons Report

C.Stage Plan

D.End Project Report

E.Project Initiation Documentation (PID)

AnswersB, D

The Lessons Report is created during Closing a Project, capturing lessons learned throughout the project for the organisation's lessons log. It fulfils the process's requirement to pass on improvement knowledge before the project team disbands.

Why this answer

The Lessons Report (B) is produced during Closing a Project as part of the 'Evaluate the project' activity, capturing lessons learned for the organization's lessons log. The End Project Report (D) is also produced in Closing a Project, providing a final assessment of the project's performance against its baselines and confirming the project's outcome. The Project Brief (A) is created in Pre-Project during Starting up a Project, not at closure.

The Stage Plan (C) is produced during Managing a Stage Boundary for the next stage, not in Closing a Project. The Project Initiation Documentation (E) is assembled during Initiating a Project, well before closure.

Exam trap

PRINCE2F often tests confusion between management products produced at different process stages — candidates must map each document to its originating process, not just its general purpose.

Full explanation →

1073

MCQhard

During a project, the Senior User reports that the expected benefits are now unlikely to be achieved because a new regulation invalidates the original business rationale. The Executive asks the Project Manager to prepare information for a decision on whether to continue. What should the Project Manager do FIRST?

A.Raise an Exception Report and wait for the Project Board to instruct the Project Manager on the next steps.

B.Request that the Senior User revise the Benefits Review Plan to reflect the new regulation.

C.Update the Business Case with the revised costs, risks, and forecast benefits, and present it to the Project Board for a decision.

D.Immediately close the project because the original business rationale is no longer valid.

AnswerC

When assumptions behind the Business Case change, the Business Case must be updated with the new costs, risks, and benefit forecasts so the Project Board can decide whether the project remains viable. This is the first step before any continuation, change, or closure action is taken.

Why this answer

A change in the business rationale means the Business Case must be reassessed and updated with revised costs, risks, and benefit forecasts. Presenting the updated Business Case to the Project Board allows the Executive and other board members to decide whether to continue, change, or stop the project.

Exam trap

The trap here is jumping to closure or to an Exception Report when the real requirement is to refresh the Business Case so the board can make an informed continuation decision.

Full explanation →

1074

MCQmedium

You are the Project Manager of a project that has just completed its first delivery stage. At the End Stage Assessment, the Project Board reviews the Business Case and notes that the forecast costs have risen by 12 percent while the expected benefits remain unchanged. The Board asks what the project should do to maintain alignment with the Business Case. Which action is MOST appropriate?

A.Proceed to the next stage as planned because the business case tolerance for benefits has not been exceeded.

B.Update the Business Case with the new cost forecast and continue, treating the increase as a normal variance within stage tolerances.

C.Stop the project immediately because the cost increase invalidates the original Business Case and no further work can be justified.

D.Review the Business Case to confirm the project remains viable and, if necessary, escalate the decision to the Project Board for a continue, change or stop decision.

AnswerD

The Business Case must be reviewed at each End Stage Assessment and whenever a significant change occurs. A 12 percent cost increase with unchanged benefits may undermine the investment appraisal, so the Project Manager should reassess the Business Case and present the findings to the Project Board, which decides whether to continue, change or stop the project. This maintains the continued business justification principle.

Why this answer

The Business Case must be reviewed at each End Stage Assessment and on significant changes. A 12 percent cost increase with unchanged benefits can undermine the investment appraisal, so the Project Manager should reassess viability and escalate to the Project Board for a continue, change or stop decision, preserving the continued business justification principle.

Exam trap

The trap here is treating a significant cost increase as an ordinary variance within stage tolerances rather than a trigger for reassessing the Business Case and seeking a Project Board decision.

Full explanation →

1075

MCQmedium

In which process are the Project Board's key decisions made, such as authorizing initiation and authorizing stage plans?

A.Starting Up a Project

B.Directing a Project

C.Initiating a Project

D.Controlling a Stage

AnswerB

Directing a Project is where the Project Board exercises its decision-making authority, authorising initiation, stage plans, and project closure. It satisfies the stem's requirement for the process containing the Board's key authorisation decisions, operating at the directing layer above the day-to-day managing layer.

Why this answer

Directing a Project is the PRINCE2 process owned by the Project Board that provides overall direction and management control throughout the project. It is where the Project Board makes key decisions such as authorizing initiation (via the 'Authorize Initiation' activity), authorizing each stage plan (via 'Authorize a Stage or Exception Plan'), and authorizing project closure. The process runs from project start to finish, in parallel with the other processes, and acts as the interface between the corporate/programme level and the project manager.

Exam trap

PRINCE2F often tests the confusion between the process where a document is produced (e.g., Initiating a Project produces the PID) and the process where the Project Board authorizes it (Directing a Project), so candidates must distinguish preparation from authorization.

How to eliminate wrong answers

Option A is wrong because Starting Up a Project is a pre-project process performed by the Project Manager and Executive to create the Project Brief and appoint the Project Board; it does not contain Project Board authorization decisions. Option C is wrong because Initiating a Project is where the Project Manager prepares the Project Initiation Documentation (PID) for the Board to approve, but the actual authorization decision is made in Directing a Project. Option D is wrong because Controlling a Stage is the Project Manager's day-to-day process for managing work packages, monitoring progress, and handling issues within an already-authorized stage, not for Board-level authorization decisions.

Full explanation →

1076

Multi-Selecthard

A project is in the Initiation Stage. The project manager is assembling the Project Initiation Documentation (PID). Which TWO components are created during the Initiating a Project process and included in the PID? (Choose two.)

Select 2 answers

A.Project Brief

B.Project Plan

C.Business Case

D.Lessons Log

E.End Stage Report

AnswersB, C

The Project Plan is created during the Initiating a Project process. It provides the project's overall plan, including the product breakdown structure, activities, resources, and schedule. It is a key component of the PID and is used by the Project Board to authorise the project. It is distinct from the Stage Plan, which is created later.

Why this answer

The Project Plan and Business Case are both created during the Initiating a Project process and are key components of the Project Initiation Documentation. The Project Plan defines how the project will deliver its products, and the Business Case justifies the project.

Exam trap

The trap here is confusing inputs to initiation, such as the Project Brief, or products from other processes, such as the End Stage Report, with components created during initiation and included in the PID.

Full explanation →

1077

MCQhard

A project is approaching the end of its final stage. The Project Manager has confirmed that all products have been delivered and accepted, and the Benefits Review Plan has been updated. Which activity belongs to the Closing a Project process rather than to the final stage's Controlling a Stage activities?

A.Authorising a new Work Package for a remaining specialist deliverable.

B.Preparing the End Project Report for the Project Board.

C.Taking corrective action after a Checkpoint Report shows a schedule slippage.

D.Reviewing Work Package status and updating the Stage Plan during the final stage.

AnswerB

The End Project Report is produced specifically during Closing a Project. It summarises project performance against the Project Initiation Documentation, records the final version of the Business Case and confirms whether the project has delivered what it set out to achieve. Preparing it is a dedicated closure activity, not part of the routine monitoring and control performed while the final stage is still running.

Why this answer

Closing a Project contains its own set of activities that confirm acceptance, review the Business Case, prepare the End Project Report, capture lessons learned and plan benefits realisation. Producing the End Project Report is unique to this process, whereas reviewing Work Packages, authorising work and reacting to Checkpoint Reports are all routine activities of Controlling a Stage during delivery.

Exam trap

The trap here is treating all end-of-project paperwork as generic project administration, when the End Project Report is a specific product of the Closing a Project process, distinct from the ongoing control products used during the final stage.

Full explanation →

1078

MCQmedium

A project is being set up to deliver a new customer portal. The project manager is defining the roles and responsibilities. The executive wants to know who will be accountable for the overall success or failure of the project. According to PRINCE2, which role is ultimately accountable for the project's success?

A.The Project Manager, because they manage the day-to-day delivery and report progress to the board.

B.The Project Board as a collective, because decisions are made jointly by the Executive, Senior User, and Senior Supplier.

C.The Senior User, because they represent the interests of the users who will benefit from the project outputs.

D.The Executive, because they are ultimately accountable for the project and represent the business interests.

AnswerD

In PRINCE2 the Executive is the single point of accountability for the project and represents the business perspective on the project board. They ensure that the project remains aligned with business objectives and that the business case is valid, making them the correct answer for who is ultimately accountable.

Why this answer

PRINCE2 assigns ultimate accountability for the project to the Executive, who represents the business interest on the project board. The Executive ensures the business case is valid and that the project delivers the expected benefits, while the Project Manager handles day-to-day delivery and other board members represent user and supplier interests.

Exam trap

The trap here is confusing the Project Manager's delivery responsibility with the Executive's ultimate accountability for the project.

Full explanation →

1079

MCQmedium

In which process is the End Stage Report produced?

A.Closing a Project

B.Directing a Project

C.Managing a Stage Boundary

D.Controlling a Stage

AnswerC

The End Stage Report is assembled by the Project Manager while Managing a Stage Boundary, reviewing stage performance and preparing the next Stage Plan for the Project Board's authorisation. It is not produced in Controlling a Stage, which handles day-to-day delivery.

Why this answer

The End Stage Report is produced during the Managing a Stage Boundary process, which occurs at the end of each stage (except the final stage, where Closing a Project takes over). It summarises the stage's performance against its plan, including results, issues, and lessons, and is used by the Project Board to decide whether to approve the next stage.

Exam trap

PRINCE2F often tests the confusion between the End Stage Report (produced in Managing a Stage Boundary) and the End Project Report (produced in Closing a Project), since both are end-of-phase reports but apply to different scopes.

How to eliminate wrong answers

Option A is wrong because Closing a Project produces the End Project Report, not the End Stage Report, and it covers the entire project rather than a single stage. Option B is wrong because Directing a Project is the Project Board's process for making key decisions; it does not produce the End Stage Report itself. Option D is wrong because Controlling a Stage is the day-to-day management process during a stage, not the boundary process where the End Stage Report is created.

Full explanation →

1080

MCQmedium

According to PRINCE2, what is the definition of quality?

A.Conformance to specification

B.Fit for purpose

C.Customer satisfaction

D.Zero defects

AnswerB

PRINCE2 defines quality as the degree to which a product fulfils its requirements, expressed as fit for purpose. This means the product meets the user's stated needs and the agreed acceptance criteria, rather than merely conforming to specification or exceeding expectations.

Why this answer

PRINCE2 defines quality as 'fit for purpose', meaning the product must satisfy the user's stated or implied needs.

Full explanation →

1081

Multi-Selectmedium

Which THREE of the following are components of the Business Case?

Select 3 answers

A.Major risks

B.Project Plan

C.Lessons learned

D.Expected benefits

E.Dis-benefits

AnswersA, D, E

Major risks form part of the Business Case because they directly affect the viability of the investment. PRINCE2 requires the Business Case to record risks that could undermine the benefits, costs or timescales, satisfying the stem's demand for a genuine component rather than a separate management product.

Why this answer

In PRINCE2, the Business Case is the document that justifies the project by capturing the business justification, and it explicitly includes the expected benefits (Option D), which describe the measurable improvements or outcomes the project will deliver, and the dis-benefits (Option E), which are the negative consequences or outcomes stakeholders must accept as a trade-off. It also includes the major risks (Option A), since the Business Case must record the significant uncertainties that could affect the viability of the justification, alongside costs, timescales, and the investment appraisal. Options B and C are not components of the Business Case: the Project Plan is a separate management product within the Plans theme that defines products, activities, and resources, while Lessons learned is a separate PRINCE2 management product (or a lessons log/report) captured throughout the project rather than a constituent part of the Business Case.

Full explanation →

1082

MCQmedium

The Project Board wants to provide ad-hoc direction to the Project Manager regarding a critical issue. Which process should the Project Board use?

A.Managing Product Delivery

B.Initiating a Project

C.Controlling a Stage

D.Directing a Project

AnswerD

Directing a Project is the process where the Project Board gives ad-hoc direction and decisions to the Project Manager, including authorising responses to critical issues outside normal stage boundaries. Managing a Stage Boundary handles planned stage transitions, not ad-hoc direction.

Why this answer

Directing a Project is the PRINCE2 process used by the Project Board to provide ad-hoc direction and make key decisions throughout the project, including authorising stages, tolerances, and handling exceptions. When the Project Board needs to give direction on a critical issue outside the normal stage boundary cycle, this is the process they use. It runs from project start to project closure in parallel with the other processes.

Exam trap

PRINCE2F often tests confusion between Controlling a Stage (Project Manager's process) and Directing a Project (Project Board's process) — candidates pick Controlling a Stage because it sounds like the right level of control, missing that the question specifies the Project Board.

How to eliminate wrong answers

Option A is wrong because Managing Product Delivery is the process used by the Project Manager and Team Manager to manage the delivery of products — it is not a Project Board process. Option B is wrong because Initiating a Project is a one-time process at the start of the project to develop the PID, not for ad-hoc direction during execution. Option C is wrong because Controlling a Stage is the Project Manager's process for day-to-day management of a stage, not the Project Board's process for providing direction.

Full explanation →

1083

MCQeasy

Which process is responsible for authorizing work to be done within a stage?

A.Directing a Project

B.Controlling a Stage

C.Initiating a Project

D.Managing Product Delivery

AnswerB

Controlling a Stage is the project manager's day-to-day process that authorises and monitors work packages within an approved stage. It satisfies the stem's constraint of authorising work inside a stage, whereas Directing a Project authorises the stage itself at its boundary.

Why this answer

The 'Controlling a Stage' process is responsible for authorizing work to be done within a stage. It involves the day-to-day management of the stage, including authorizing work packages, monitoring progress, and taking corrective action. This process ensures that the stage stays on track and delivers the required products.

Exam trap

PRINCE2F often tests the confusion between 'Controlling a Stage' and 'Managing Product Delivery', where candidates might think that 'Managing Product Delivery' authorizes work, but it actually receives authorization from 'Controlling a Stage'.

How to eliminate wrong answers

Option A is wrong because 'Directing a Project' is the process used by the Project Board to make key decisions and provide overall direction, but it does not authorize work within a stage. Option C is wrong because 'Initiating a Project' is the process that sets up the project and develops the Project Initiation Documentation, but it does not manage stage work. Option D is wrong because 'Managing Product Delivery' is the process used by the Team Manager to accept and execute work packages, but it is not responsible for authorizing work within a stage; that authorization comes from 'Controlling a Stage'.

Full explanation →

1084

MCQmedium

During the Controlling a Stage process, a Work Package is authorized by the Project Manager. Who is responsible for delivering the Work Package?

A.Senior Supplier

B.Project Support

C.Team Manager

D.Project Manager

AnswerC

The Team Manager accepts the Work Package from the Project Manager and is accountable for its delivery, directing team members and reporting progress, quality and forecast through Checkpoint Reports. This matches PRINCE2's defined responsibility for Work Package execution.

Why this answer

In PRINCE2, the Team Manager is the role responsible for delivering the Work Package authorized by the Project Manager during the Controlling a Stage process. The Team Manager coordinates the team's work, ensures the products meet the agreed quality criteria, and reports progress back to the Project Manager.

Exam trap

The trap here is that candidates often confuse the Project Manager's role of authorizing the Work Package with the responsibility for its delivery, leading them to select the Project Manager instead of the Team Manager.

How to eliminate wrong answers

Option A is wrong because the Senior Supplier is responsible for providing supplier resources and expertise, not for directly delivering the Work Package. Option B is wrong because Project Support provides administrative and advisory services, such as configuration management and reporting, but does not deliver the Work Package. Option D is wrong because the Project Manager authorizes the Work Package and manages the stage, but the actual delivery is delegated to the Team Manager.

Full explanation →

1085

MCQhard

Which process is the Project Board primarily responsible for, according to PRINCE2?

A.Directing a Project

B.Managing Product Delivery

C.Controlling a Stage

D.Managing a Stage Boundary

AnswerA

Directing a Project is the process owned by the Project Board, which makes key decisions at decision points rather than managing daily work. It satisfies the stem by naming the process for which the Board holds primary responsibility under PRINCE2.

Why this answer

The Project Board is primarily responsible for the 'Directing a Project' process, which covers the overall management and decision-making from project initiation through closure. This process includes authorizing the project, providing key decisions, and ensuring that the project remains viable and aligned with business objectives. The Board does not execute day-to-day management or delivery tasks, which belong to other roles.

Exam trap

The trap here is that candidates often confuse the Project Board's strategic oversight with the Project Manager's operational responsibilities, leading them to select 'Controlling a Stage' or 'Managing a Stage Boundary' because they involve decision-making, but those are executed by the Project Manager, not the Board.

How to eliminate wrong answers

Option B is wrong because 'Managing Product Delivery' is the responsibility of the Team Manager, who coordinates the work of the project team to create the project's products, not the Project Board. Option C is wrong because 'Controlling a Stage' is the responsibility of the Project Manager, who monitors progress, manages issues, and reports to the Board during each stage. Option D is wrong because 'Managing a Stage Boundary' is also the responsibility of the Project Manager, who prepares the end-stage report and next stage plan for the Board's approval.

Full explanation →

1086

MCQmedium

A project is in the Initiation Stage. The Project Manager has drafted the Project Plan and the Business Case, but the Project Board has not yet approved the Project Initiation Documentation. The Project Manager is asked to produce the next Stage Plan. Which statement best describes the appropriate timing and authority for producing the next Stage Plan?

A.The next Stage Plan can be produced as part of the Initiating a Project process, but it cannot be approved until the Project Board has authorised the project and the Project Initiation Documentation.

B.The next Stage Plan must be produced only after the Project Board has approved the Project Initiation Documentation and authorised the project, as part of Managing a Stage Boundary.

C.The next Stage Plan is produced by the Project Board during the Directing a Project process, because the Board owns all stage-level planning.

D.The next Stage Plan is not needed until the first delivery stage begins, because the Project Plan already contains sufficient detail for day-to-day control.

AnswerA

In PRINCE2, the next Stage Plan is prepared during Initiating a Project so the Project Board can authorise the project and the first stage together. However, the Stage Plan itself is only baselined when the Project Board approves the Project Initiation Documentation and authorises the project. Producing it early supports informed decision-making, but it remains a draft until that authorisation.

Why this answer

The first Stage Plan is normally produced during Initiating a Project so that the Project Board can authorise both the project and its first stage. It is not approved until the Project Initiation Documentation is approved. Producing it later, or assigning it to the Board, misplaces both the timing and the responsibility defined in PRINCE2.

Exam trap

The trap here is assuming the Stage Plan must wait until after project authorisation, when it is actually prepared during Initiating a Project to support that authorisation decision.

Full explanation →

1087

MCQhard

Which of the following statements best describes the difference between a Request for Change (RFC) and an Off-Specification (Off-spec)?

A.An RFC is handled by the Change Authority, while an Off-spec is handled by the Project Manager

B.An RFC always results in a change to the Baseline, while an Off-spec always results in a concession

C.An RFC proposes a change to an approved product or process, while an Off-spec identifies a product that does not meet its specification

D.An RFC is raised by the Senior User, while an Off-spec is raised by the Project Manager

AnswerC

An RFC seeks approval to alter a baselined product or process, whereas an Off-spec records a product that fails to meet its agreed specification. The axis of difference is intent: one requests change, the other reports non-conformance.

Why this answer

A Request for Change (RFC) is a formal proposal to modify a product, baseline, or process that has been approved, while an Off-Specification (Off-spec) is a formal notification that a product does not meet its agreed specification. In PRINCE2, an RFC seeks to change what is required, whereas an Off-spec reports a failure to deliver what was required. This distinction is fundamental to the issue and change control procedure.

Exam trap

PeopleCert often tests the misconception that RFCs and Off-specs are handled by different roles or always lead to specific outcomes, when in reality both can be raised by anyone and their resolution depends on the change authority and the nature of the issue.

How to eliminate wrong answers

Option A is wrong because both RFCs and Off-specs can be handled by the Change Authority or the Project Manager depending on the delegation of authority and the severity of the issue; there is no fixed rule that RFCs go to the Change Authority and Off-specs go to the Project Manager. Option B is wrong because an RFC does not always result in a change to the baseline (it may be rejected), and an Off-spec does not always result in a concession (it may be resolved by a corrective action or a change request). Option D is wrong because an RFC can be raised by any stakeholder (not just the Senior User), and an Off-spec is typically raised by the person who identifies the non-conformance, which could be the Project Manager, team manager, or quality assurance, not exclusively the Project Manager.

Full explanation →

1088

MCQmedium

A project manager is reviewing the business case for a new software development project. The project is expected to generate significant revenue, but the initial investment is high. According to PRINCE2, which principle is MOST directly being applied when the project manager ensures that the business case remains viable throughout the project?

A.Manage by stages

B.Learn from experience

C.Continued business justification

D.Tailor to suit the project environment

AnswerC

Continued business justification requires the business case to remain valid and viable throughout the project, not merely at initiation. Reviewing revenue against investment continuously applies that principle directly, satisfying the stem's condition that viability is maintained.

Why this answer

The PRINCE2 principle of Continued Business Justification requires that the business case, which documents the project's justification, is reviewed and updated at key decision points (e.g., stage boundaries) to ensure the project remains viable. In this scenario, the project manager is actively verifying that the high initial investment is still justified by the expected revenue, directly applying this principle to avoid proceeding with an unviable project.

Exam trap

PeopleCert often tests the distinction between 'Continued Business Justification' and 'Manage by Stages,' where candidates mistakenly think stage boundaries are for business case review, but the principle itself is about ongoing viability, not the mechanism of stage management.

How to eliminate wrong answers

Option A is wrong because Manage by Stages is a principle about dividing the project into management stages for control, not about continuously validating the business case. Option B is wrong because Learn from Experience focuses on capturing and applying lessons from previous projects, not on ongoing business justification. Option D is wrong because Tailor to Suit the Project Environment is about adapting PRINCE2 processes to the project's context, not about ensuring the business case remains viable.

Full explanation →

1089

MCQmedium

Which role is responsible for independent assurance of the project?

A.Team Manager

B.Project Support

C.Project Manager

D.Project Assurance

AnswerD

Project Assurance independently monitors the project's performance and products on behalf of the Project Board, separate from the Project Manager's day-to-day control. This satisfies the stem's independence constraint, since the Project Manager cannot assure their own work objectively.

Why this answer

Project Assurance in PRINCE2 is the role responsible for independently monitoring all aspects of the project's performance and products on behalf of the Project Board. It provides the board with confidence that the project is being run correctly and that the Business Case remains viable. This independence distinguishes it from the Project Manager, who is responsible for day-to-day delivery.

Exam trap

PRINCE2F often tests whether candidates confuse Project Assurance with Project Support, so the trap is choosing Project Support because both are 'support' functions, when only Project Assurance provides independent board-level oversight.

How to eliminate wrong answers

Option A is wrong because the Team Manager focuses on producing products within a work package and reports to the Project Manager, not providing independent assurance. Option B is wrong because Project Support provides administrative and tooling support, not independent assurance. Option C is wrong because the Project Manager manages the project on a day-to-day basis and cannot independently assure their own work.

Full explanation →

1090

Multi-Selecthard

Which TWO of the following activities are performed in the Starting Up a Project process?

Select 2 answers

A.Appoint the Executive and the Project Manager

B.Produce the Project Initiation Documentation

C.Authorise the project

D.Plan the next management stage

E.Capture lessons from previous projects

AnswersA, E

Appointing the Executive and Project Manager occurs during Starting Up a Project, satisfying the stem's requirement for activities within that process. These appointments are pre-project activities that establish the project's leadership before the Project Board authorises initiation, distinguishing them from later process activities such as managing stage boundaries.

Why this answer

In PRINCE2, the Starting Up a Project (SU) process is the pre-project process whose purpose is to ensure the prerequisites for initiating a project are in place, and it includes the activity 'Appoint the Executive and the Project Manager' (option A) — the Executive is appointed first from the corporate/programme organization, then the Executive appoints the Project Manager, forming the minimum viable project board. SU also includes the activity 'Capture previous lessons' (option E), where the Project Manager gathers lessons from similar past projects (often via the Lessons Log) so they can inform the Project Brief and the Initiation Stage Plan. Option B (Produce the Project Initiation Documentation) belongs to the Initiating a Project (IP) process, not SU.

Option C (Authorise the project) is the decision taken by the Project Board at the end of IP, based on the PID, and is not an SU activity. Option D (Plan the next management stage) is performed in the Managing a Stage Boundary process, not during Starting Up a Project.

Exam trap

PRINCE2F often tests confusion between Starting Up a Project (pre-project, produces Project Brief) and Initiating a Project (produces PID and seeks authorisation) — candidates frequently assign PID creation or project authorisation to SU when both belong to IP.

Full explanation →

1091

MCQmedium

Which document describes the quality methods and tools to be used, and the responsibilities for quality throughout the project?

A.Project Plan

B.Business Case

C.Product Description

D.Quality Management Approach

AnswerD

The Quality Management Approach defines the quality methods, tools and responsibilities across the project, satisfying the stem's requirement for a single controlling document. It sits within the project initiation documentation and is tailored to the project's context, unlike generic quality policy or product descriptions.

Why this answer

The Quality Management Approach defines the quality methods, tools, and responsibilities for the project. The Project Plan includes timelines and costs. The Business Case covers justification.

The Product Description defines quality criteria for a specific product.

Full explanation →

1092

MCQmedium

Which document is the key output of the Initiating a Project process?

A.Project Plan

B.Project Initiation Documentation

C.Project Brief

D.Business Case

AnswerB

The Project Initiation Documentation is the key output of Initiating a Project, consolidating the Business Case, Project Plan, and approach documents. It satisfies the process's purpose of establishing a firm baseline before the Project Board authorises the project to proceed.

Why this answer

The Project Initiation Documentation (PID) is the key output of Initiating a Project.

Full explanation →

1093

MCQmedium

A project is in its final stage. The Project Manager has verified that all products have been accepted and operational support is in place. Which process should the Project Manager initiate next?

A.Closing a Project

B.Controlling a Stage

C.Directing a Project

D.Managing a Stage Boundary

AnswerA

Once products are accepted and operational support confirmed, the final stage's remaining activity is project closure. Closing a Project provides the controlled end, confirming acceptance, reviewing benefits and lessons, and releasing the project team and resources.

Why this answer

Closing a Project is the process used when the Project Manager confirms all products are accepted, operational support is in place, and the project can be formally closed. It confirms the project has delivered its objectives, obtains Project Board authorization to close, and hands over products and lessons. Since the final stage's products are accepted and support is arranged, this is exactly the trigger for Closing a Project.

Exam trap

PRINCE2F often tests the boundary between Managing a Stage Boundary and Closing a Project; candidates incorrectly pick Managing a Stage Boundary for the final stage, forgetting that no subsequent stage exists to plan.

How to eliminate wrong answers

Option B is wrong because Controlling a Stage is the day-to-day management of work within an active stage, not the final closure activity. Option C is wrong because Directing a Project is the Project Board's process for authorizing and providing direction — it is not initiated by the Project Manager as the next step here. Option D is wrong because Managing a Stage Boundary prepares the next stage plan and Exception Plan; at the end of the final stage there is no next stage to plan, so the boundary process is not the correct next step.

Full explanation →

1094

MCQmedium

A project is forecast to exceed its cost tolerance for the current stage. According to PRINCE2, what should the Project Manager do?

A.Increase the project budget to absorb the additional cost and continue with the current Stage Plan

B.Raise an Exception Report to the Project Board and await their direction

C.Close the project immediately as the Business Case is no longer viable

D.Continue with the current Stage Plan and report the cost overrun in the next Highlight Report

AnswerB

When a stage’s cost tolerance is forecast to be exceeded, the Project Manager must escalate because the deviation is beyond the delegated authority. PRINCE2 requires an Exception Report to the Project Board, who then decide on corrective action. This mechanism satisfies the *management by exception* principle, which limits the Project Manager’s authority to within the agreed tolerance for the current stage.

Why this answer

According to PRINCE2, when a stage is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board by raising an Exception Report. This triggers a formal decision process where the Board can authorize a revised Stage Plan or take other corrective action. Continuing without escalation violates the management by exception principle.

Exam trap

The trap here is that candidates assume cost overruns can be handled within the Project Manager's authority or that the Business Case is automatically invalid, when PRINCE2 mandates escalation to the Project Board for any forecast tolerance breach.

How to eliminate wrong answers

Option A is wrong because increasing the budget unilaterally bypasses the Project Board's authority and violates the delegated tolerance limits defined in the Stage Plan. Option C is wrong because exceeding cost tolerance does not automatically invalidate the Business Case; the Board must assess viability before closure. Option D is wrong because waiting for the next Highlight Report would delay escalation beyond the tolerance breach, which contradicts PRINCE2's requirement for immediate exception reporting.

Full explanation →

1095

MCQmedium

During the Initiating a Project (IP) process, which document is created to define how the project will be executed, monitored, and controlled?

A.Project Initiation Documentation

B.Project Brief

C.Project Plan

D.Business Case

AnswerA

The Project Initiation Documentation is assembled during Initiating a Project, containing the Project Plan, Business Case, risk and quality approaches. It satisfies the requirement to define how the project will be executed, monitored and controlled before the Project Board authorises the project.

Why this answer

The Project Initiation Documentation (PID) is the definitive document created during the Initiating a Project (IP) process. It consolidates all key information—including the Business Case, Project Plan, and controls—into a single source that defines how the project will be executed, monitored, and controlled throughout its lifecycle.

Exam trap

PRINCE2 often tests the distinction between documents created in different processes, and the trap here is confusing the Project Brief (from SU) with the Project Initiation Documentation (from IP), as both contain high-level project information but serve different purposes and are created at different stages.

How to eliminate wrong answers

Option B (Project Brief) is wrong because the Project Brief is created during the Starting Up a Project (SU) process as a preliminary outline of the project, not during IP, and it lacks the detailed execution and control definitions found in the PID. Option C (Project Plan) is wrong because the Project Plan is a component within the PID that focuses specifically on the schedule and resources, not the overarching governance, monitoring, and control mechanisms. Option D (Business Case) is wrong because the Business Case justifies the project's viability and is also a component of the PID, but it does not define how the project will be executed, monitored, and controlled.

Full explanation →

1096

MCQeasy

Based on the exhibit, what is the purpose of including expected dis-benefits in the Business Case?

A.To identify risks that could affect the project

B.To show the full cost of the project including ongoing operational costs

C.To provide a balanced view of the project's justification

D.To document the project's key performance indicators

AnswerC

Expected dis-benefits record the negative outcomes a project will cause, so including them alongside benefits gives decision-makers a balanced, honest view of justification. Omitting them would overstate value, so this satisfies the stem's purpose of balanced justification.

Why this answer

The PRINCE2 Business Case must include expected dis-benefits to provide a balanced view of the project's justification. Dis-benefits are measurable negative outcomes that, when weighed against benefits, allow the Senior User and Senior Supplier to make an informed go/no-go decision. Without documenting dis-benefits, the Business Case would present an incomplete picture, potentially leading to approval of a project with hidden negative impacts.

Exam trap

The trap here is that candidates often confuse dis-benefits with risks or costs, but PRINCE2 explicitly separates them: dis-benefits are certain negative outcomes, risks are uncertain events, and costs are financial expenditures.

How to eliminate wrong answers

Option A is wrong because dis-benefits are not risks; they are certain negative outcomes that will occur if the project is successful, whereas risks are uncertain events that may or may not happen. Option B is wrong because the full cost of the project including ongoing operational costs is captured in the 'Costs' section of the Business Case, not in the dis-benefits section. Option D is wrong because Key Performance Indicators (KPIs) are used to measure benefits achievement during and after the project, not to document expected dis-benefits.

Full explanation →

1097

MCQeasy

In PRINCE2, what is the purpose of Project Support?

A.To provide administrative support to the project.

B.To approve stage plans.

C.To independently assure the Project Board.

D.To manage the project's budget.

AnswerA

Project Support supplies administrative services to the project manager and team, such as maintaining the project filing structure, configuration records, and logs. It is a defined PRINCE2 role, distinct from project assurance and change control.

Why this answer

Project Support in PRINCE2 is a role that provides administrative and clerical services to the project management team, such as maintaining files, organizing meetings, and managing project documentation. It does not have decision-making authority over stage plans, assurance, or budget management, which are the responsibilities of other roles like the Project Manager, Project Assurance, and the Executive.

Exam trap

The trap here is that candidates confuse Project Support with Project Assurance, mistakenly thinking support includes oversight or approval functions, when in fact PRINCE2 strictly separates administrative support from independent assurance and management authority.

How to eliminate wrong answers

Option B is wrong because approving stage plans is the responsibility of the Project Board, not Project Support. Option C is wrong because independent assurance of the Project Board is the role of Project Assurance, which is separate from Project Support. Option D is wrong because managing the project's budget is a core duty of the Project Manager, not Project Support.

Full explanation →

1098

MCQhard

What is the primary difference between a Highlight Report and a Checkpoint Report?

A.A Highlight Report is sent to the Project Board; a Checkpoint Report is sent to the Project Manager

B.A Highlight Report is produced weekly; a Checkpoint Report is produced daily

C.A Highlight Report covers the entire project; a Checkpoint Report covers a stage

D.There is no difference; they are the same report with different names

AnswerA

The axis is audience and reporting flow: Highlight Reports provide progress information upward to the Project Board at agreed intervals, whereas Checkpoint Reports flow from team members to the Project Manager, typically at frequency set in the Work Package.

Why this answer

The defining difference is the audience and reporting line: a Highlight Report is produced by the Project Manager for the Project Board to summarize stage progress, while a Checkpoint Report is produced by the Team Manager for the Project Manager to report progress within a stage. This distinction is about who receives the report, not just frequency.

Exam trap

PRINCE2F often tests the audience/producer distinction; candidates are lured by plausible-sounding frequency or scope answers (weekly vs. daily, project vs. stage) instead of the correct sender-recipient relationship.

How to eliminate wrong answers

Option B is wrong because frequency is not the defining difference — Highlight Reports are typically produced at intervals defined in the Communication Management Strategy (often weekly or monthly), and Checkpoint Reports at frequencies set in the Work Package, so neither is fixed to 'weekly' or 'daily'. Option C is wrong because both reports cover stage-level progress; the Highlight Report summarizes the stage for the Board, and the Checkpoint Report covers work package progress within the stage — neither covers the entire project. Option D is wrong because they are distinct PRINCE2 management products with different purposes, producers, and audiences.

Full explanation →

1099

MCQmedium

In PRINCE2, who is responsible for ensuring that project assurance is independent of the Project Manager?

A.Project Board

B.Senior User

C.Project Manager

D.Project Support

AnswerA

The Project Board owns the project assurance responsibility and must ensure it remains independent of the Project Manager, since the Project Manager cannot objectively assure their own work. Board members appoint assurance roles that report to them, preserving that independence throughout the project lifecycle.

Why this answer

In PRINCE2, the Project Board is accountable for project assurance, ensuring it is independent of the Project Manager. The Board appoints assurance roles (Business, User, Supplier assurance) that monitor the project on its behalf, providing independent oversight. This independence is a core governance principle.

Exam trap

PRINCE2F often tests the principle that assurance must be independent of the Project Manager; candidates wrongly assign it to the Project Manager or Project Support because those roles are closest to day-to-day delivery.

How to eliminate wrong answers

Option B is wrong because the Senior User is a Project Board role focused on representing user interests and benefits realization, not on ensuring assurance independence across the project. Option C is wrong because the Project Manager cannot provide independent assurance over their own work — assurance must be independent of them. Option D is wrong because Project Support provides administrative and specialist support, not independent assurance; it may assist but does not own assurance.

Full explanation →

1100

MCQmedium

In PRINCE2, what is the role of the Senior User?

A.To specify the desired outcomes and benefits

B.To chair the Project Board

C.To manage the project on a day-to-day basis

D.To provide resources and expertise

AnswerA

The Senior User represents those who will use the project's outputs and is accountable for specifying the desired outcomes and benefits in the business case. This ensures the project delivers something fit for purpose, satisfying the user viewpoint PRINCE2 requires on the project board.

Why this answer

The Senior User in PRINCE2 is responsible for specifying the desired outcomes and benefits of the project, ensuring that the project delivers products that meet user needs and enable the expected benefits. This role represents the interests of those who will use the project's outputs and is accountable for defining the user requirements and acceptance criteria.

Exam trap

The trap here is that candidates often confuse the Senior User's focus on benefits and outcomes with the Project Manager's operational duties or the Senior Supplier's resource provision, leading them to select options that describe other roles on the Project Board.

How to eliminate wrong answers

Option B is wrong because chairing the Project Board is the responsibility of the Executive, not the Senior User; the Executive provides overall leadership and is accountable for the project's success. Option C is wrong because managing the project on a day-to-day basis is the role of the Project Manager, who handles planning, monitoring, and control. Option D is wrong because providing resources and expertise is primarily the role of the Senior Supplier, who represents those who design, develop, and supply the project's products.

Full explanation →

1101

Drag & Dropmedium

Drag and drop the steps to manage a configuration item 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

Configuration management: identify, control changes, record status, verify, and report.

Full explanation →

1102

MCQmedium

A programme manager has assigned a project manager to deliver a new customer portal. The programme manager will define the project mandate, but the project manager must create the project brief. According to PRINCE2, what is the primary purpose of the project brief?

A.It authorizes the project manager to start the first delivery stage and commit resources.

B.It serves as the contract between the supplier and the customer, defining the acceptance criteria and payment terms.

C.It documents the detailed business case, including benefits, costs, and risks, that will be baselined at the end of initiation.

D.It provides sufficient information for the project board to decide whether it is worthwhile to initiate the project.

AnswerD

The project brief is the pre-project document that gives the project board enough information to authorize the Initiating a Project process. It contains the project definition, outline business case, and project approach, allowing a go/no-go decision on whether to invest in the more detailed initiation work.

Why this answer

The project brief is created before the project starts and gives the project board the information it needs to decide whether to authorize the initiation stage. It includes the outline business case, project definition, and project approach, but not the detailed baselined products that come later in the project initiation documentation.

Exam trap

The trap here is confusing the project brief with the project initiation documentation, assuming the brief contains the detailed business case or authorizes delivery.

Full explanation →

1103

MCQmedium

During the Initiating a Project process, which document details how quality will be managed on the project?

A.Risk Management Approach

B.Business Case

C.Quality Management Approach

D.Project Plan

AnswerC

The Quality Management Approach defines the quality standards, procedures and responsibilities the project will adopt, and it is produced during Initiating a Project. It directly satisfies the stem's requirement for the document describing how quality will be managed, unlike the Project Initiation Documentation, which merely assembles it alongside other baselined products.

Why this answer

The Quality Management Approach is the PRINCE2 document produced during Initiating a Project that defines how quality will be managed, including the quality standards, roles, responsibilities, and techniques to be applied. It is one of the four Approaches (alongside Risk, Change, and Communication) created in the Initiating a Project process. It describes the project's quality management system and how products will be reviewed and approved.

Exam trap

PRINCE2F often tests the confusion between the four Approaches (Risk, Quality, Change, Communication) and other PID documents like the Business Case or Project Plan — candidates must remember that quality management is specifically covered by the Quality Management Approach.

How to eliminate wrong answers

Option A is wrong because the Risk Management Approach defines how risks will be identified, assessed, and controlled, not quality. Option B is wrong because the Business Case justifies the project's viability and benefits, not the quality management method. Option D is wrong because the Project Plan describes the products, activities, resources, and schedule, but does not itself define the quality management approach.

Full explanation →

1104

MCQmedium

Which role is responsible for producing the Highlight Report?

A.Project Support

B.Project Manager

C.Senior Responsible Owner

D.Team Manager

AnswerB

The Project Manager produces the Highlight Report, summarising progress, status and exceptions for the Project Board at the frequency agreed in the communication management approach, whereas the Project Board and Team Manager have other reporting duties.

Why this answer

The Highlight Report is a progress report that summarizes the status of a management stage for the Project Board. According to PRINCE2, the Project Manager is responsible for producing the Highlight Report at intervals defined in the Communication Management Strategy, typically to keep the Project Board informed of progress, exceptions, and forecasts.

Exam trap

The trap here is that candidates often confuse the Highlight Report with the Checkpoint Report, mistakenly assigning the Team Manager as the producer, when in fact the Team Manager produces the Checkpoint Report and the Project Manager produces the Highlight Report.

How to eliminate wrong answers

Option A is wrong because Project Support provides administrative and clerical assistance, such as maintaining files or distributing reports, but does not own the production of the Highlight Report. Option C is wrong because the Senior Responsible Owner (SRO) is the executive accountable for the business case and overall project success, not for producing operational progress reports like the Highlight Report. Option D is wrong because the Team Manager is responsible for producing the Checkpoint Report for their team, not the stage-level Highlight Report, which is a higher-level summary compiled by the Project Manager.

Full explanation →

1105

MCQhard

A project is in the Managing a Stage Boundary process. The Project Manager discovers that the stage is likely to overrun its time tolerance. The Project Board has not yet approved the next Stage Plan. What should the Project Manager do?

A.Raise an Exception Report to the Project Board.

B.Update the Project Plan to reflect the delay.

C.Close the project as the Business Case is invalid.

D.Continue with the current Stage Plan and submit the next Stage Plan as planned.

AnswerA

A forecast breach of stage time tolerance is a project-level exception, and PRINCE2 requires the Project Manager to escalate it to the Project Board via an Exception Report. The Board then decides how to proceed, since the next Stage Plan is not yet approved.

Why this answer

In PRINCE2, when a stage is forecast to exceed its time tolerance, the Project Manager must escalate by raising an Exception Report to the Project Board. This applies even during Managing a Stage Boundary, because the current stage's tolerance breach is a deviation from the approved Stage Plan that only the Board can authorize.

Exam trap

PRINCE2 Foundation often tests the management-by-exception principle, and candidates mistakenly think the PM can adjust the Project Plan or continue without escalation when a stage tolerance is breached.

How to eliminate wrong answers

Option B is wrong because updating the Project Plan alone does not address the tolerance breach — the Project Board must be informed and must decide on corrective action; the PM cannot unilaterally absorb an exception. Option C is wrong because a time overrun does not automatically invalidate the Business Case; closing the project requires a Board decision based on continued viability, not a single tolerance breach. Option D is wrong because continuing as planned and submitting the next Stage Plan ignores the exception — PRINCE2 requires escalation when tolerances are forecast to be exceeded, not silent continuation.

Full explanation →

1106

MCQmedium

You are the project manager of a PRINCE2 project to organize a major industry conference. The executive has asked you to prepare the business case for the project. Which of the following must be included in the business case according to PRINCE2?

A.The project's risk management approach and risk register

B.Reasons why the project is needed, expected benefits, and associated risks

C.The detailed stage plan for the first delivery stage

D.The project's organization structure and role descriptions

AnswerB

The business case in PRINCE2 must include the reasons why the project is needed, the expected benefits, and the associated risks. It also covers costs, timescales, and the investment appraisal. These elements together justify the project and demonstrate that it is desirable, viable, and achievable. This is essential for the project board to make informed decisions about continuing the project.

Why this answer

According to PRINCE2, the business case must include the reasons why the project is needed, the expected benefits, and the associated risks. It also includes costs, timescales, and an investment appraisal. These elements collectively justify the project and ensure it remains desirable, viable, and achievable.

The business case is a living document, updated at stage boundaries and in exception situations.

Exam trap

The trap here is assuming that organizational details or detailed plans are part of the business case, when they are separate documents within the project initiation documentation.

Full explanation →

1107

MCQhard

A project is in the Initiating a Project process. Which management product is defined as the key output of this process?

A.End Project Report

B.Benefits Review Plan

C.Project Brief

D.Project Initiation Documentation

AnswerD

The Project Initiation Documentation is the mandated output of the Initiating a Project process, consolidating the business case, plans, controls and project approach into a single baseline. It satisfies the stem's requirement by providing the Project Board with the information needed to authorise the project, and it is formally approved at the end of initiation.

Why this answer

The Project Initiation Documentation (PID) is the key management product produced by the Initiating a Project process in PRINCE2. It consolidates the business case, project plan, risk, quality, and communication approaches, and forms the baseline against which the project is directed and controlled.

Exam trap

PRINCE2F often tests whether candidates confuse inputs and outputs of adjacent processes — the Project Brief is the input to Initiating a Project, while the PID is its output, and the Benefits Review Plan is a component of the PID rather than a standalone key output.

How to eliminate wrong answers

Option A is wrong because the End Project Report is produced at the end of the project during Closing a Project, not during initiation. Option B is wrong because the Benefits Review Plan is created as part of the PID's contents but is not itself the key output of the Initiating a Project process — it is a component of the PID. Option C is wrong because the Project Brief is the input to Initiating a Project, produced during Starting Up a Project, not the output.

Full explanation →

1108

MCQeasy

Which process is responsible for authorizing a Work Package?

A.Managing Product Delivery

B.Managing a Stage Boundary

C.Controlling a Stage

D.Directing a Project

AnswerC

Controlling a Stage is where the Project Manager agrees and authorises Work Packages with the team managers, setting tolerances and reporting arrangements. Authorisation occurs at this level because the stage plan is being executed, not at project initiation or closure.

Why this answer

The Controlling a Stage process is where the Project Manager authorizes Work Packages, assigning work to the Team Manager and monitoring progress against the stage plan. It is one of the core activities of Controlling a Stage to authorize a Work Package once the stage is underway. This process ensures that work is only started when the Project Manager has confirmed it is within tolerance and properly defined.

Exam trap

PRINCE2F often tests the boundary between Controlling a Stage (Project Manager authorizes Work Packages) and Managing Product Delivery (Team Manager accepts and executes them) — candidates confuse the two because both involve Work Packages.

How to eliminate wrong answers

Option A is wrong because Managing Product Delivery is the process where the Team Manager accepts and executes the Work Package, not where it is authorized. Option B is wrong because Managing a Stage Boundary is about preparing for the next stage and reporting to the Project Board, not authorizing individual Work Packages. Option D is wrong because Directing a Project is the Project Board's process for overall project authorization and stage authorization, not for authorizing individual Work Packages.

Full explanation →

1109

MCQmedium

Which risk response is appropriate for an opportunity?

A.Exploit

B.Reduce

C.Transfer

D.Avoid

AnswerA

Exploit is the response that removes uncertainty and realises the opportunity outright, allocating resources to ensure it definitely happens. This satisfies the stem because it is the opportunity-focused counterpart to avoid, and is appropriate when the organisation wants to capture the upside.

Why this answer

In PRINCE2, risk responses are tailored to whether the risk is a threat or an opportunity. For opportunities, the appropriate responses are Exploit, Enhance, Share, and Accept. 'Exploit' is the correct response because it seeks to ensure the opportunity definitely happens, often by removing uncertainty and allocating resources to realize the benefit. This is distinct from threat responses such as Avoid, Reduce, Transfer, or Accept.

Exam trap

PRINCE2F often tests the confusion between threat and opportunity responses, as candidates may incorrectly apply threat responses like Reduce or Avoid to opportunities.

How to eliminate wrong answers

Option B is wrong because 'Reduce' is a threat response aimed at reducing the probability or impact of a negative risk, not an opportunity response. Option C is wrong because 'Transfer' is a threat response that shifts the financial impact of a threat to a third party, such as through insurance; it does not apply to opportunities. Option D is wrong because 'Avoid' is a threat response that eliminates the threat entirely, often by changing scope or approach, and is not used for opportunities.

Full explanation →

1110

MCQmedium

A project is developing a new customer relationship management (CRM) system. The Project Manager is preparing the Quality Management Strategy and needs to ensure it aligns with the project's approach to quality. According to PRINCE2, which of the following best describes the purpose of the Quality Management Strategy?

A.It specifies the detailed quality criteria for each product to be produced by the project.

B.It records the quality activities and results for each product as they are completed.

C.It outlines the project's approach to managing and controlling changes to product specifications.

D.It defines the quality techniques and standards to be applied and the responsibilities for achieving quality.

AnswerD

The Quality Management Strategy is a PRINCE2 document that describes the quality techniques, standards, and responsibilities for achieving quality within the project. It ensures that quality is planned and managed systematically, providing a common framework for all quality activities. This aligns with the PRINCE2 principle of focusing on products and defining quality criteria.

Why this answer

The Quality Management Strategy is a key PRINCE2 document that defines the quality techniques, standards, and responsibilities for the project. It ensures that quality is planned and managed consistently. The other options refer to different PRINCE2 documents or components, such as the Quality Register or Product Descriptions, which serve distinct purposes within the quality theme.

Exam trap

The trap here is confusing the Quality Management Strategy with the Quality Register or Product Descriptions, which have different roles in quality management.

Full explanation →

1111

MCQmedium

Which report is produced by the Team Manager and sent to the Project Manager on a regular basis?

A.Checkpoint Report

B.Highlight Report

C.End Stage Report

D.Exception Report

AnswerA

The Team Manager produces Checkpoint Reports at the frequency agreed in the Work Package, sending them to the Project Manager to report progress, issues and forecast. This matches the stem's requirement for a regular Team Manager-to-Project Manager report.

Why this answer

The Checkpoint Report is produced by the Team Manager and sent to the Project Manager at a frequency defined in the Work Package. It provides status information on the Work Package, including progress, issues, and risks. This is a standard PRINCE2 report.

Exam trap

PRINCE2F often tests the producer and recipient of each report, and candidates may confuse Checkpoint Reports with Highlight Reports.

How to eliminate wrong answers

Option B is wrong because the Highlight Report is produced by the Project Manager and sent to the Project Board, summarizing stage progress. Option C is wrong because the End Stage Report is produced by the Project Manager at the end of a stage. Option D is wrong because the Exception Report is produced by the Project Manager when tolerances are exceeded, and it is sent to the Project Board.

Full explanation →

1112

MCQhard

A project is in the Controlling a Stage process, and the Project Manager receives a Request for Change (RFC) from a stakeholder. What should the Project Manager do first?

A.Implement the change immediately to satisfy the stakeholder

B.Log the issue in the Issue Register

C.Escalate directly to the Project Board

D.Reject the change as it was not planned

AnswerB

Logging the RFC in the Issue Register first satisfies the Controlling a Stage requirement to capture all issues, including change requests, before assessing them. The register provides the audit trail and status tracking that subsequent impact analysis and Change Authority decisions depend upon, so nothing is actioned until the request is formally recorded.

Why this answer

In PRINCE2, any Request for Change is treated as an issue and must first be captured in the Issue Register before any assessment or action. The Controlling a Stage process requires the Project Manager to log the RFC, then assess its impact and decide whether it can be handled within stage tolerances or must be escalated. Logging first ensures traceability and prevents ad-hoc changes that bypass configuration management.

Exam trap

PRINCE2F often tests the sequence of change control — candidates who jump to escalation or implementation miss that logging in the Issue Register is always the mandatory first step before any assessment or decision.

How to eliminate wrong answers

Option A is wrong because implementing a change immediately violates PRINCE2's change control principle — all changes must be assessed for impact on the business case, and approved through the appropriate authority before implementation. Option C is wrong because escalation to the Project Board only happens if the change exceeds stage-level tolerances; the Project Manager must first log and assess the change to determine whether escalation is warranted. Option D is wrong because rejecting a change outright without assessment contradicts PRINCE2's principle of 'manage by exception' and the change control procedure — changes may be legitimate and beneficial, and must be evaluated, not dismissed.

Full explanation →

1113

MCQmedium

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

A.Issue an Exception Report to the Project Board

B.Update the Business Case to reflect the new cost

C.Close the project as it is no longer viable

D.Approve additional budget using contingency

AnswerA

Forecast breach of a cost tolerance is an exception, so the Project Manager escalates by issuing an Exception Report to the Project Board, which decides how to respond. This satisfies the stem's first action, since tolerances cannot be exceeded without Board authorisation.

Why this answer

In PRINCE2, when a project is forecast to exceed a tolerance (in this case cost tolerance), the Project Manager must escalate the deviation to the Project Board by producing an Exception Report. The Project Board then decides whether to approve a change, request more information, or take corrective action. This is the defined 'manage by exception' principle — the Project Manager does not unilaterally approve additional budget or change the Business Case.

Exam trap

PRINCE2F often tests the boundary between Project Manager and Project Board authority — candidates incorrectly pick 'approve additional budget' or 'update the Business Case' because those seem like logical next steps, but both are Board-level decisions, not PM actions.

How to eliminate wrong answers

Option B is wrong because updating the Business Case is a Project Board responsibility (the Business Case is owned by the Executive) and would only follow a Board decision, not precede it. Option C is wrong because closing the project is a Project Board decision based on continued business justification; the Project Manager cannot close a project simply because a tolerance is forecast to be exceeded. Option D is wrong because approving additional budget (drawing on contingency) is a Project Board authority, not the Project Manager's — the Project Manager's role is to report the exception and recommend options, not to authorize the spend.

Full explanation →

1114

MCQhard

A project has reached the point where the final product has been handed over to operations and the user has confirmed acceptance. The Project Manager is now performing the Closing a Project process. Which action is required as part of this process?

A.Prepare the next Stage Plan for approval by the Project Board

B.Authorise the Work Package for the final product and issue it to the Team Manager

C.Confirm that all project products have been handed over and that the operational and maintenance environment is prepared

D.Appoint the Executive and confirm the project mandate with corporate management

AnswerC

Closing a Project requires the Project Manager to confirm that the products have been handed over and accepted, and that the operational and maintenance arrangements are in place. This confirmation is a core activity of the process and ensures the project does not close while leaving the customer unable to operate and support the delivered products.

Why this answer

Closing a Project confirms that products have been handed over and accepted, that the operational and maintenance environment is prepared, and that the project can be brought to a controlled close. It also covers reviewing the Business Case, producing the End Project Report and Lessons Report, and planning benefits reviews. Preparing Stage Plans, appointing the Executive, or issuing Work Packages all belong to earlier processes.

Exam trap

The trap here is assuming any documentation-intensive activity belongs to Closing a Project, when several candidate actions actually belong to earlier lifecycle processes.

Full explanation →

1115

MCQhard

Which of the following is a characteristic of a project, as defined by PRINCE2?

A.It is a permanent organization with ongoing operations

B.It introduces no change to the organization

C.It is part of business as usual

D.It produces a unique product, service, or result

AnswerD

PRINCE2 defines a project as a temporary organisation created to deliver one or more business products according to an agreed Business Case. Uniqueness of the product, service or result is a defining characteristic, distinguishing projects from routine operational work.

Why this answer

PRINCE2 defines a project as a temporary organization created for the purpose of delivering one or more business products according to an agreed Business Case. A defining characteristic is that it produces a unique product, service, or result, and it is finite in duration with defined start and end points. Option D captures this core PRINCE2 principle that projects are distinct from business as usual because they deliver something new and unique.

Exam trap

PRINCE2F often tests the distinction between projects and business as usual, and candidates commonly confuse the temporary nature of projects with the permanence of operational organizations.

How to eliminate wrong answers

Option A is wrong because PRINCE2 explicitly defines a project as a temporary organization, not a permanent one — permanence is a characteristic of business as usual (BAU), not projects. Option B is wrong because projects inherently introduce change; PRINCE2's entire purpose is to manage the change from the current state to a desired future state. Option C is wrong because PRINCE2 draws a sharp distinction between projects and business as usual — projects are temporary endeavors that sit outside routine operations.

Full explanation →

1116

MCQmedium

A PRINCE2 project is midway through the 'Managing a Stage Boundary' process. The Project Manager is preparing the End Stage Report for the Project Board. The Board has asked for assurance that the project remains aligned with corporate strategy and that the Business Case is still viable. Which PRINCE2 principle is MOST directly supported by the Project Board's review of the updated Business Case at this point?

A.Learn from experience

B.Continued business justification

C.Tailor to suit the project environment

D.Manage by exception

AnswerB

The principle of continued business justification requires that a PRINCE2 project has a viable Business Case that is reviewed and updated at stage boundaries. The Project Board's review of the updated Business Case at 'Managing a Stage Boundary' directly supports this principle by ensuring the project remains aligned with corporate strategy and that benefits still outweigh costs and risks.

Why this answer

The Project Board's review of the updated Business Case at a stage boundary is a direct application of the continued business justification principle, which mandates that the project remains aligned with strategy and that the Business Case is viable. This principle ensures the project is stopped if justification disappears. The other principles are important but are not the primary focus of this specific activity.

Exam trap

The trap here is confusing the routine review of the Business Case at a stage boundary with the manage by exception principle, which is about tolerances and escalation rather than ongoing justification.

Full explanation →

1117

Multi-Selectmedium

Which THREE of the following are PRINCE2 practices (themes)?

Select 3 answers

A.Waterfall

B.Risk

C.Sprint Planning

D.Quality

E.Business Case

AnswersB, D, E

Risk is one of the seven PRINCE2 practices, alongside business case, organisation, plans, quality, change and progress. It satisfies the stem's requirement by being a recognised practice, governing how the project team identifies, assesses and controls uncertainty throughout each stage of the project lifecycle.

Why this answer

In PRINCE2, the seven themes (now called practices in PRINCE2 2017) describe aspects of project management that must be addressed continually, and Risk (B), Quality (D), and Business Case (E) are three of them. Risk (B) is correct because PRINCE2 requires a Risk theme/practice covering risk identification, assessment, and response throughout the project. Quality (D) is correct because the Quality theme/practice defines how the project will verify that products meet requirements and achieve fitness for purpose.

Business Case (E) is correct because the Business Case theme/practice ensures the project remains desirable, viable, and achievable, justifying continued investment. Waterfall (A) is not a PRINCE2 theme but a sequential development approach, and Sprint Planning (C) is a Scrum event, not a PRINCE2 practice.

Full explanation →

1118

MCQhard

A project is in the Initiation Stage. The project manager is creating the Project Plan and needs to define the project's products and activities. Which PRINCE2 principle should guide the level of detail included in the plan?

A.Manage by exception

B.Tailor to suit the project environment

C.Focus on products

D.Learn from experience

AnswerB

The principle 'Tailor to suit the project environment' means PRINCE2 should be adapted to the project's size, complexity, and risk. The level of detail in the Project Plan should be tailored accordingly. For a small, low-risk project, a less detailed plan may suffice, while a large, complex project requires more detail.

Why this answer

The PRINCE2 principle 'Tailor to suit the project environment' guides the level of detail in plans. It requires adapting the method to the project's specific needs, so the Project Plan's detail should reflect the project's size, complexity, and risk.

Exam trap

The trap here is selecting a principle that seems relevant to planning, such as 'Focus on products', when the question specifically asks about the level of detail, which is governed by tailoring.

Full explanation →

1119

Multi-Selectmedium

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

Select 2 answers

A.Project Board

B.Project Support

C.Senior Supplier

D.Project Manager

E.Change Authority

AnswersB, E

Project Support is optional because PRINCE2 permits the project manager to absorb its administrative duties, such as maintaining the project log and configuration records, when project scale or complexity does not justify a dedicated resource. The stem asks for optional roles, and Project Support is explicitly listed as such, unlike mandatory roles like Project Manager.

Why this answer

Project Support is an optional role in PRINCE2, providing administrative and advisory services to the project manager and team, but it is not mandatory for the project management team structure. Option E is correct because the Change Authority role is also optional, delegated by the Project Board to manage change requests and off-specifications, and is only established if needed for change control.

Exam trap

PeopleCert often tests the misconception that all roles listed in the PRINCE2 management team are mandatory, leading candidates to incorrectly select roles like Project Support or Change Authority as required, when they are actually optional and only established when needed.

Full explanation →

1120

MCQmedium

In which process are End Stage Reports produced?

A.Closing a Project

B.Controlling a Stage

C.Directing a Project

D.Managing a Stage Boundary

AnswerD

End Stage Reports are produced within Managing a Stage Boundary, where the Project Manager reviews stage performance and prepares information for the Project Board. This satisfies the stem by placing the report in the process that requests authorisation for the next stage.

Why this answer

The End Stage Report is produced during the Managing a Stage Boundary process. This process is triggered at the end of each management stage (except the final stage) to evaluate the current stage's performance, plan the next stage, and update the business case. The report is then provided to the Project Board for approval to proceed.

Exam trap

The trap here is that candidates often confuse the End Stage Report with the End Project Report, incorrectly selecting Closing a Project (Option A) because both reports have similar names, but the End Stage Report is specifically tied to stage boundaries, not project closure.

How to eliminate wrong answers

Option A is wrong because Closing a Project produces the End Project Report, not the End Stage Report; the End Stage Report is specific to stage boundaries. Option B is wrong because Controlling a Stage focuses on day-to-day management and produces Checkpoint Reports, not End Stage Reports. Option C is wrong because Directing a Project is the decision-making process for the Project Board, which receives the End Stage Report but does not produce it.

Full explanation →

1121

MCQhard

The Project Board is considering whether to approve an Exception Plan. Which process should they use to make this decision?

A.Managing a Stage Boundary

B.Directing a Project

C.Controlling a Stage

D.Closing a Project

AnswerB

Directing a Project is where the Project Board authorises Exception Plans, satisfying the stem's requirement that the Board approve one. Within this process, the "Authorise an Exception Plan" activity lets the Board review the plan and decide whether to permit the Stage or Project to proceed against revised tolerances.

Why this answer

The Project Board is responsible for making key decisions and exercising overall control over the project. When an Exception Plan is submitted, it is the Project Board's role to review and approve or reject it, which is a core activity of the 'Directing a Project' process. This process covers all high-level decision-making, including authorizing deviations from the plan.

Exam trap

The trap here is confusing the process that creates the Exception Plan (Managing a Stage Boundary) with the process that approves it (Directing a Project), leading candidates to select the wrong process for the Board's decision-making role.

How to eliminate wrong answers

Option A is wrong because 'Managing a Stage Boundary' is the process used by the Project Manager to prepare the Exception Plan and request its approval from the Project Board, not the process the Board uses to make the decision. Option C is wrong because 'Controlling a Stage' is the process used by the Project Manager to manage day-to-day work within a stage, not for Board-level decisions on exception plans. Option D is wrong because 'Closing a Project' is the process for formally decommissioning the project after completion, not for handling mid-project exceptions.

Full explanation →

1122

MCQmedium

Who chairs the Project Board meetings in PRINCE2?

A.Senior Supplier

B.Project Manager

C.Senior User

D.Senior Responsible Owner (Executive)

AnswerD

The Executive, now titled Senior Responsible Owner, chairs Project Board meetings, owning the business case and holding decision-making authority. This role ensures the board addresses exception situations and approves continued project viability, satisfying PRINCE2's governance structure.

Why this answer

The Executive (Senior Responsible Owner) chairs the Project Board meetings in PRINCE2 because they are ultimately accountable for the project's success and have the authority to make key decisions. This role ensures the project remains aligned with business objectives and provides strategic direction during board meetings.

Exam trap

The trap here is that candidates often confuse the Project Manager's role in facilitating meetings with the authority to chair the board, but PRINCE2 clearly separates management (Project Manager) from governance (Executive chairing the board).

How to eliminate wrong answers

Option A is wrong because the Senior Supplier represents the interests of those providing the project's products and does not chair the board; they focus on technical feasibility and supplier-side concerns. Option B is wrong because the Project Manager is responsible for day-to-day management and reporting to the board, not chairing it, as they lack the authority to make strategic decisions. Option C is wrong because the Senior User represents the needs of those who will use the project's outputs and does not chair the board; their role is to define requirements and ensure benefits realization.

Full explanation →

1123

MCQeasy

Which role is responsible for managing the day-to-day activities of the project within the tolerances set by the Project Board?

A.Project Manager

B.Project Assurance

C.Team Manager

D.Senior Responsible Owner (SRO)

AnswerA

The Project Manager owns day-to-day delivery, authorising work packages and monitoring progress against the stage tolerances delegated by the Project Board. This directly satisfies the stem's constraint: operational management within agreed tolerances, distinct from the Board's strategic direction and the Project Assurance role's independent oversight.

Why this answer

In PRINCE2, the Project Manager is the role responsible for managing the project on a day-to-day basis within the tolerances (e.g., time, cost, scope, risk) set by the Project Board. This includes planning, delegating, monitoring, and reporting progress, ensuring the project remains within agreed tolerances and escalating any deviations to the Project Board.

Exam trap

PRINCE2 often tests the distinction between the Project Manager (operational control) and the Project Board (strategic control), leading candidates to confuse Project Assurance (which is oversight, not management) or the Team Manager (which is a lower-level delivery role) with the day-to-day manager.

How to eliminate wrong answers

Option B is wrong because Project Assurance is an independent monitoring function that checks compliance with PRINCE2 standards and business justification, not a role that manages day-to-day activities. Option C is wrong because the Team Manager is responsible for delivering the work within a specific work package, not for overall project management or tolerance management. Option D is wrong because the Senior Responsible Owner (SRO) is a role in PRINCE2 Agile or other frameworks (e.g., Managing Successful Programmes), not a standard PRINCE2 role; in PRINCE2, the Executive is the business sponsor, not the day-to-day manager.

Full explanation →

1124

Multi-Selectmedium

Which THREE of the following are elements of the PRINCE2 project management team?

Select 3 answers

A.Project Board

B.Team Manager

C.Project Manager

D.User Group

E.Steering Committee

AnswersA, B, C

The Project Board is one of the three PRINCE2 project management team elements, sitting at the top and accountable for the project's overall direction and success. It comprises the Executive, Senior User and Senior Supplier, delegating day-to-day management to the Project Manager.

Why this answer

In PRINCE2, the project management team is defined by three core roles: the Project Board (A), which is accountable for the overall success of the project and provides the 'direction' level of management; the Project Manager (C), who runs the project on a day-to-day basis at the 'management' level; and the Team Manager (B), who is responsible for producing the specialist products at the 'delivery' level. These three roles form the standard PRINCE2 project management team structure, with the Project Board comprising the Executive, Senior User, and Senior Supplier. The User Group (D) is not a defined PRINCE2 role or team element — users are represented on the Project Board by the Senior User, though a user group may exist informally.

The Steering Committee (E) is not a PRINCE2 term; it is a generic governance body used in other frameworks, whereas PRINCE2 uses the Project Board for that purpose.

Exam trap

PRINCE2F often tests the difference between PRINCE2-defined roles and generic governance terms like 'Steering Committee' or 'User Group', so candidates who rely on general PM knowledge pick the non-PRINCE2 options.

Full explanation →

1125

MCQeasy

Which PRINCE2 process is triggered by the Project Mandate and produces the Project Brief?

A.Managing a Stage Boundary

B.Directing a Project

C.Initiating a Project

D.Starting Up a Project

AnswerD

Starting Up a Project is triggered by the Project Mandate and produces the Project Brief, along with the initiation stage plan. It precedes Initiating a Project, which then develops the Project Initiation Documentation from that brief.

Why this answer

The Starting Up a Project process is triggered by the Project Mandate and produces the Project Brief. This process ensures that the project has a viable business case and that the necessary resources and stakeholders are identified before any detailed planning begins. The Project Brief is the key output that summarizes the project's justification, scope, and approach, serving as the foundation for the Initiating a Project process.

Exam trap

The trap here is that candidates often confuse the Starting Up a Project process with Initiating a Project, mistakenly thinking the Mandate triggers the creation of the PID, but PRINCE2 explicitly separates the initial viability check (Starting Up) from detailed planning (Initiating).

How to eliminate wrong answers

Option A is wrong because Managing a Stage Boundary is triggered at the end of each management stage to plan the next stage and update the business case, not by the Project Mandate. Option B is wrong because Directing a Project is the process for the Project Board to make key decisions and monitor progress, not to produce the Project Brief from the Mandate. Option C is wrong because Initiating a Project uses the Project Brief to create the Project Initiation Documentation (PID), but it is not triggered by the Mandate; the Mandate triggers Starting Up a Project first.

Full explanation →

PRINCE2 Foundation (PRINCE2F) — Questions 1051–1125