Courseiva

CCNA PRINCE2 Processes Questions

75 of 325 questions · Page 4/5 · PRINCE2 Processes · Answers revealed

226
MCQhard

Who is responsible for ensuring that project assurance is independent of the Project Manager?

A.The Team Manager
B.The Project Manager
C.The Project Support
D.The Project Board
AnswerD

The Project Board owns the project's assurance responsibilities and must ensure project assurance is independent of the Project Manager. It appoints assurance roles that report to the board rather than to the Project Manager, preserving objectivity and preventing the manager from reviewing their own work.

Why this answer

The Project Board is responsible for ensuring that project assurance is independent of the Project Manager. This is because the Project Board provides overall governance and oversight, and project assurance is a key function that must be objective and separate from the day-to-day management activities of the Project Manager. The PRINCE2 principle of 'defined roles and responsibilities' explicitly assigns this accountability to the Project Board to maintain the integrity of the assurance function.

Exam trap

The trap here is that candidates often confuse the Project Manager's responsibility for managing the project with the Project Board's responsibility for ensuring independent oversight, leading them to incorrectly select the Project Manager as the answer.

How to eliminate wrong answers

Option A is wrong because the Team Manager is responsible for delivering the work within a work package, not for ensuring the independence of project assurance. Option B is wrong because the Project Manager is the person being assured, so they cannot be responsible for ensuring the independence of the function that oversees them; that would create a conflict of interest. Option C is wrong because Project Support provides administrative and clerical services to the project, not the governance or independence of assurance.

227
MCQhard

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

A.SU is optional; IP is mandatory
B.SU is performed by the Project Board; IP is performed by the Project Manager
C.SU produces the Project Brief; IP produces the Project Initiation Documentation (PID)
D.SU includes detailed planning; IP only produces high-level plans
AnswerC

Starting Up a Project produces the Project Brief, the outline business case and project approach. Initiating a Project builds on that brief to produce the Project Initiation Documentation, which consolidates the detailed business case, plans, controls and risk approach. The axis of difference is outline versus detailed documentation.

Why this answer

The Starting Up a Project (SU) process is the pre-project activity that produces the Project Brief, which defines the project's rationale, scope, and approach at a high level. The Initiating a Project (IP) process then takes that brief and produces the Project Initiation Documentation (PID), which includes the detailed Business Case, plans, controls, and role descriptions. The distinction is one of scope and timing: SU sets up the project, IP formally authorizes and plans it.

Exam trap

PRINCE2F often tests the confusion between the Project Brief (SU output) and the PID (IP output) — candidates mix up which process produces which document, or assume SU is optional because it happens before the project formally starts.

How to eliminate wrong answers

Option A is wrong because both SU and IP are mandatory processes in PRINCE2 — SU is not optional; it is the first process and must be performed to produce the Project Brief before the project can be initiated. Option B is wrong because SU is performed by the Project Manager with the Project Board's approval of the Project Brief, while IP is also led by the Project Manager — the Project Board does not perform IP; it authorizes the project based on the PID. Option D is wrong because it reverses the planning detail: SU produces high-level information in the Project Brief, while IP produces the detailed plans (Project Plan, Stage Plan, Business Case) in the PID.

228
MCQeasy

Which process is triggered when the Project Manager needs to escalate an exception to the Project Board?

A.Controlling a Stage
B.Managing a Stage Boundary
C.Directing a Project
D.Managing Product Delivery
AnswerA

Controlling a Stage includes the "Escalate Exception" activity, which the Project Manager uses to refer a forecast breach of stage tolerances to the Project Board for a decision. It satisfies the stem's requirement to escalate an exception, since this process governs the Project Manager's day-to-day management of a stage.

Why this answer

Controlling a Stage is the process where the Project Manager monitors work, handles issues, and escalates exceptions to the Project Board when tolerances are forecast to be exceeded. Escalating an exception is a core activity within Controlling a Stage, which triggers the Project Board via the 'Directing a Project' process through an Exception Report. The Project Manager owns this escalation activity within the Controlling a Stage process.

Exam trap

PRINCE2F often tests the confusion between Controlling a Stage (PM's ongoing monitoring and escalation) and Managing a Stage Boundary (end-of-stage activities), causing candidates to pick the boundary process for exception escalation.

How to eliminate wrong answers

Option B is wrong because Managing a Stage Boundary occurs at the end of a stage to prepare the next Stage Plan and End Stage Report, not for mid-stage exception escalation. Option C is wrong because Directing a Project is the Project Board's process, not the Project Manager's — the Board receives the escalation, it doesn't trigger it. Option D is wrong because Managing Product Delivery is the Team Manager's process for accepting, executing, and delivering work packages, not for escalating exceptions.

229
MCQhard

What is the key difference between the Starting Up a Project process and the Initiating a Project process?

A.Starting Up a Project is performed before the project is formally initiated; Initiating a Project establishes the project baseline
B.Initiating a Project is optional; Starting Up a Project is mandatory
C.Starting Up a Project produces the Project Plan; Initiating a Project produces the Project Brief
D.Initiating a Project involves the Project Board; Starting Up a Project does not
AnswerA

Starting Up a Project is the pre-project process producing the Project Brief and Business Case outline before the Project Board authorises initiation. Initiating a Project then establishes the Project Initiation Documentation baseline, including plans, controls and the detailed Business Case.

Why this answer

The key difference is that Starting Up a Project (SU) is a pre-project process that occurs before the project is formally initiated, focusing on creating the Project Brief and appointing the Executive and Project Manager. Initiating a Project (IP) is the first process after the project is authorized, where the detailed Project Plan, Business Case, and Risk Register are developed, and the Project Initiation Documentation (PID) is created to establish the project baseline. Thus, SU sets the stage for IP, while IP formalizes the project's foundation.

Exam trap

The trap here is that candidates often confuse the outputs of the two processes, mistakenly thinking the Project Plan is created in Starting Up a Project or that the Project Brief is created in Initiating a Project, when in fact the Project Brief is the key output of SU and the Project Plan is a key output of IP.

How to eliminate wrong answers

Option B is wrong because both Starting Up a Project and Initiating a Project are mandatory processes in PRINCE2; neither is optional. Option C is wrong because Starting Up a Project produces the Project Brief, not the Project Plan; the Project Plan is created during the Initiating a Project process. Option D is wrong because the Project Board is involved in both processes: in Starting Up a Project, the Executive is appointed and may authorize the initiation, and in Initiating a Project, the full Project Board reviews and approves the PID.

230
MCQmedium

During the Closing a Project process, what must be produced to confirm that the project has delivered what was expected?

A.Lessons Report
B.Benefits Realisation Plan
C.End Project Report
D.Project Product Description
AnswerC

The End Project Report is the PRINCE2 baseline product of Closing a Project. It records actual versus planned performance and confirms the project delivered the expected products, satisfying the stem's requirement to verify delivery against expectations before the project closes.

Why this answer

The End Project Report is produced during Closing a Project and provides the Project Board with confirmation that the project has delivered what was expected, including a review of the Project Initiation Documentation and the Business Case. It summarizes performance against the project's baselines and confirms acceptance of the project product. This report is the formal mechanism for verifying delivery against expectations.

Exam trap

PRINCE2F often tests the confusion between the End Project Report (confirms delivery) and the Benefits Realisation Plan (describes future benefit measurement), causing candidates to pick the plan when asked about confirming delivery.

How to eliminate wrong answers

Option A is wrong because the Lessons Report captures lessons learned for future projects, not confirmation of delivery against expectations. Option B is wrong because the Benefits Realisation Plan is created during Starting Up a Project or Initiating a Project and describes how benefits will be measured post-project, not a closing confirmation. Option D is wrong because the Project Product Description defines the project product's customer quality expectations and acceptance criteria, created early in the project, not a closing report.

231
Multi-Selectmedium

Which TWO of the following are produced during the Initiating a Project process?

Select 2 answers
A.End Stage Report
B.Project Initiation Documentation (PID)
C.Project Brief
D.Risk Management Approach
E.Checkpoint Report
AnswersB, D

The Project Initiation Documentation is assembled during Initiating a Project, consolidating the business case, project plan, risk and quality approaches into a single baseline. This satisfies the process's purpose of establishing solid foundations before the project proceeds, giving the Project Board the evidence needed to authorise the next stage.

Why this answer

The Initiating a Project process in PRINCE2 assembles the Project Initiation Documentation (PID), so option B is correct: the PID is the consolidated baseline of the project's plans, controls, and business case produced at the end of this process. Option D is also correct because the Risk Management Approach is one of the four strategies (with Quality, Configuration Management, and Communication Management Approaches) created during Initiating a Project and then embedded within the PID. Option A, the End Stage Report, is produced during the Managing a Stage Boundary process, not Initiating a Project.

Option C, the Project Brief, is a pre-project input produced during Starting Up a Project, and option E, the Checkpoint Report, is produced during stage execution as part of Managing Product Delivery.

Exam trap

PRINCE2 Foundation often tests the distinction between outputs of Starting Up a Project (e.g., Project Brief) and Initiating a Project (e.g., PID), so candidates mistakenly select the Project Brief as a product of the Initiating a Project process.

232
MCQeasy

A Project Manager is preparing to close a project. The Project Board has confirmed that the project's products have been handed over to the operational and maintenance environment. Which activity is part of the Closing a Project process?

A.Authorising the next stage and updating the Project Plan with the latest actuals
B.Producing the End Project Report and evaluating the project against its Business Case
C.Producing the Stage Plan for the final stage and updating the Risk Register
D.Creating the Project Initiation Documentation and securing Project Board approval
AnswerB

Closing a Project includes activities to confirm handover, evaluate the project against its Business Case, and produce the End Project Report. This report summarises performance against the project's objectives, benefits, and tolerances, providing the Project Board with the information needed to authorise project closure.

Why this answer

Closing a Project involves confirming that all products have been handed over, evaluating the project against its Business Case, and producing the End Project Report. These activities ensure the Project Board can confirm that the project's objectives have been met and that there are no outstanding issues before authorising closure.

Exam trap

The trap here is confusing stage-level planning or initiation activities with project closure, when Closing a Project is specifically about confirming handover and evaluating the project against its Business Case.

233
MCQeasy

Refer to the exhibit. A project has just completed the Starting up a Project process and received authorization to initiate. Which process should the project manager execute next?

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

Having secured authorisation to initiate, the project manager proceeds directly to Initiating a Project, the process that establishes the Project Initiation Documentation, business case and project controls. Starting up a Project is complete, so this is the mandated next step in the PRINCE2 process sequence.

Why this answer

After the Starting up a Project process, the project has received authorization to initiate. The next logical step is to plan the project in detail, which is done in the Initiating a Project process. This process produces the Project Initiation Documentation (PID) and establishes a solid foundation for the project.

Therefore, option C is correct.

Exam trap

PeopleCert often tests the order of PRINCE2 processes, and the trap here is confusing the authorization to initiate with authorization to deliver, leading candidates to incorrectly select Controlling a Stage or Managing Product Delivery instead of Initiating a Project.

How to eliminate wrong answers

Option A is wrong because Managing Product Delivery is executed during the delivery stage to control the work of the team, not at the start of the project. Option B is wrong because Controlling a Stage is used to manage each stage after initiation, not before the project has been fully planned and authorized. Option D is wrong because Directing a Project is the process for the Project Board to make key decisions and provide overall direction, not for the project manager to execute next.

234
MCQmedium

A Team Manager is assigned a Work Package. In which process does the Team Manager execute the work and deliver the products?

A.Controlling a Stage
B.Managing a Stage Boundary
C.Managing Product Delivery
D.Directing a Project
AnswerC

Managing Product Delivery is where the Team Manager accepts the Work Package, plans and executes the work, and delivers products to the agreed quality criteria. It sits between Controlling a Stage and the team, satisfying the stem's requirement for the execution process.

Why this answer

The Team Manager executes the work and delivers the products within the Managing Product Delivery process. This process defines the interface between the Project Manager (who controls the stage) and the Team Manager (who accepts, executes, and delivers the Work Package). It contains the activities 'Accept a Work Package', 'Execute a Work Package', and 'Deliver a Work Package'.

Exam trap

PRINCE2F often tests the confusion between the Project Manager's Controlling a Stage process and the Team Manager's Managing Product Delivery process, since both involve work execution but at different management levels.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage is the Project Manager's process for monitoring and controlling the stage, not where the Team Manager executes work. Option B is wrong because Managing a Stage Boundary is used by the Project Manager to prepare for the next stage or project closure. Option D is wrong because Directing a Project is the Project Board's process for high-level decision-making, not for work execution.

235
MCQmedium

During which process does the Project Board give ad-hoc direction to the Project Manager?

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

Directing a Project is the process where the Project Board provides ad-hoc direction and decisions to the Project Manager between stage boundaries, authorising exception responses and continued viability. It satisfies the stem's requirement for board-level guidance outside formal stage-gate reviews.

Why this answer

The Directing a Project process is owned by the Project Board and covers the board's ongoing oversight of the project between decision points. It explicitly includes giving ad-hoc direction and advice to the Project Manager whenever the board's authority or guidance is needed outside the formal stage boundaries. The other processes are owned by the Project Manager, not the board.

Exam trap

PRINCE2F often tests the boundary between Project Board responsibilities and Project Manager responsibilities, so candidates confuse 'Controlling a Stage' (PM-led) with 'Directing a Project' (Board-led) when the question mentions the board.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage is the Project Manager's day-to-day process for managing a stage, not where the Project Board issues direction. Option C is wrong because Initiating a Project is a Project Manager-led process to produce the PID, with the board only approving at the end. Option D is wrong because Starting Up a Project is a pre-project process run by the Project Manager to prepare the project brief for board authorisation.

236
MCQhard

A Team Manager is assigned a Work Package. The Team Manager realizes that the work cannot be completed within the agreed tolerances. What should the Team Manager do?

A.Take corrective action to bring the work back within tolerance
B.Continue working and report the issue in the next Checkpoint Report
C.Raise an Exception Report to the Project Board
D.Raise an Issue Report to the Project Manager
AnswerD

Tolerances sit with the Project Manager, so the Team Manager cannot unilaterally exceed them. Raising an Issue Report escalates the forecast breach, letting the Project Manager decide on corrective action, a new Work Package or stage-level replanning, satisfying the constraint that stage tolerances remain the Project Manager's authority.

Why this answer

In PRINCE2, the Team Manager works within the Work Package tolerances agreed with the Project Manager. If the Team Manager forecasts that the work will breach those tolerances, the correct escalation path is to raise an Issue Report to the Project Manager, who then decides whether to handle it at project level or escalate further. The Team Manager does not go directly to the Project Board.

Exam trap

PRINCE2F often tests the escalation hierarchy by offering 'Exception Report to the Project Board' as a tempting answer — candidates forget that only the Project Manager escalates to the Board, and the Team Manager's first stop is always the Project Manager via an Issue Report.

How to eliminate wrong answers

Option A is wrong because once the Team Manager has determined the work cannot be completed within tolerance, corrective action within their authority is no longer sufficient — the forecast breach must be escalated, not silently absorbed. Option B is wrong because waiting for the next Checkpoint Report delays escalation and violates the 'manage by exception' principle; Checkpoint Reports are for progress, not for raising exceptions. Option C is wrong because Exception Reports go to the Project Board from the Project Manager, not from the Team Manager — the Team Manager has no direct line to the Board in PRINCE2's organization structure.

237
MCQmedium

When should the Project Manager escalate an issue to the Project Board?

A.When the issue involves the Project Manager's own performance
B.Only at the end of a stage
C.When the issue cannot be resolved within the delegated tolerances
D.Only when the issue is identified
AnswerC

Escalation is triggered by breaching delegated authority: tolerances define how far the Project Manager may deviate before the issue exceeds their remit. Once resolution is impossible within those limits, only the Project Board can authorise corrective action or a revised plan.

Why this answer

In PRINCE2, the Project Manager is delegated tolerances by the Project Board and manages the stage within those tolerances. Escalation to the Board is required when an issue (or a forecast issue) cannot be resolved within the delegated tolerances, because only the Board has authority to change tolerances, the Business Case, or the project's scope. This is the 'manage by exception' principle in action.

Exam trap

PRINCE2F often tests the misconception that all issues must be escalated or that escalation happens only at stage boundaries — the correct trigger is inability to resolve within delegated tolerances.

How to eliminate wrong answers

Option A is wrong because issues involving the Project Manager's own performance are typically handled by the Board through other governance channels (e.g., Project Assurance or the Executive), not as a routine escalation trigger — the trigger is tolerance breach, not role conflict. Option B is wrong because escalation is event-driven, not calendar-driven; waiting until end of stage could allow a tolerance breach to go unmanaged. Option D is wrong because not every identified issue requires escalation — most issues are resolved by the Project Manager within tolerances; only those that cannot be resolved within tolerances are escalated.

238
MCQmedium

A project is in the Managing a Stage Boundary process. Which document should the Project Manager produce to report the current stage's performance?

A.End Stage Report
B.Highlight Report
C.Lesson Log
D.Project Brief
AnswerA

The End Stage Report reviews the stage's performance against its plan and business case, providing the Project Board with the information needed to authorise the next stage. It is the specific management product produced during Managing a Stage Boundary for reporting current stage performance.

Why this answer

In PRINCE2, the End Stage Report is the document produced by the Project Manager at the end of a stage during the Managing a Stage Boundary process. It summarizes the stage's performance against the Stage Plan, including actual versus planned costs, timescales, and products, and provides the basis for the Project Board to decide whether to approve the next stage.

Exam trap

PRINCE2F often tests the confusion between the End Stage Report (produced at stage boundary) and the Highlight Report (produced periodically during a stage) — candidates must remember the trigger event, not just the document name.

How to eliminate wrong answers

Option B is wrong because the Highlight Report is a progress report produced at regular intervals (e.g., monthly) during a stage, not at the stage boundary. Option C is wrong because the Lessons Log is a running record of lessons learned throughout the project, not a stage performance report. Option D is wrong because the Project Brief is a pre-project document that defines the project's foundation, produced before the project starts, not during Managing a Stage Boundary.

239
Multi-Selecthard

Which TWO of the following are responsibilities of the Project Manager during the Controlling a Stage process?

Select 2 answers
A.Review progress and take corrective action
B.Authorize Work Packages
C.Produce the End Project Report
D.Produce Checkpoint Reports
E.Authorize the stage plan
AnswersA, B

The PM monitors progress and takes action to keep the stage within tolerance.

Why this answer

The Project Manager is responsible for reviewing progress against the stage plan and taking corrective action when deviations occur, as defined in the Controlling a Stage process. This ensures the stage remains within tolerance and aligns with the project plan.

Exam trap

PeopleCert often tests the distinction between who produces versus who authorizes management products, and the trap here is confusing the Project Manager's role in creating a stage plan with the Project Board's authority to approve it.

240
MCQhard

In the Controlling a Stage process, a Team Manager reports that a product is complete. Which activity does the Project Manager perform next?

A.Send a Highlight Report to the Project Board
B.Approve the next Stage Plan
C.Review the product to confirm it meets quality criteria
D.Update the Project Plan
AnswerC

The PM must check that the product meets the defined quality criteria before acceptance.

Why this answer

In the Controlling a Stage process, after a Team Manager reports that a product is complete, the Project Manager must first review the product to confirm it meets the quality criteria defined in the Product Description. This is part of the 'Review Work Package' activity, ensuring that the product is fit for purpose before any further actions, such as reporting or planning, occur. Only after this quality check can the Project Manager proceed to other activities like updating logs or sending reports.

Exam trap

The trap here is that candidates often confuse the immediate operational step (quality review) with higher-level reporting or planning activities, assuming that a completion report automatically triggers a Highlight Report or stage approval without the necessary quality check first.

How to eliminate wrong answers

Option A is wrong because sending a Highlight Report is a periodic activity to inform the Project Board of progress, not the immediate next step after a product completion report; the Project Manager must first verify the product's quality. Option B is wrong because approving the next Stage Plan occurs during the Managing a Stage Boundary process, not within Controlling a Stage, and it is not triggered by a single product completion. Option D is wrong because updating the Project Plan is a broader planning activity that typically happens after stage boundaries or when significant changes occur, not as the immediate response to a completed product; the Project Manager first checks quality, then updates the Quality Register and logs.

241
MCQeasy

What is the purpose of the Closing a Project process?

A.To plan the next stage of the project
B.To manage day-to-day work within a stage
C.To create the Project Initiation Documentation
D.To ensure that the project's products are accepted and the project is closed in a controlled way
AnswerD

Closing a Project verifies that the project's products have been accepted by the customer and that the project is closed in a controlled manner. This satisfies the stem's requirement by confirming acceptance, reviewing the original justification, and handing over products, so the project ends formally rather than drifting to an uncontrolled stop.

Why this answer

Closing a Project ensures controlled closure: hand over products, confirm benefits review arrangements, produce End Project Report and Lessons Report, and release resources. Planning next stage is SB. PID is from IP.

Day-to-day management is CS.

242
MCQhard

In the Directing a Project process, the Project Board authorizes an Exception Plan. What triggers the need for an Exception Plan?

A.The project is closing
B.A stage tolerance is forecast to be exceeded
C.A new stage is about to begin
D.The Project Board requests it for strategic reasons
AnswerB

An Exception Plan is produced when a Stage Plan is forecast to exceed its agreed stage tolerance, meaning the stage can no longer be delivered within the delegated limits. The Project Board then authorises the Exception Plan in Directing a Project.

Why this answer

In PRINCE2, an Exception Plan is triggered when a stage tolerance is forecast to be exceeded. The Project Board authorizes this plan to address the deviation and keep the project on track. This is a key control mechanism within the Directing a Project process.

Exam trap

The trap here is that candidates often confuse an Exception Plan with a Stage Plan or a Project Plan, but the key trigger is the forecast of exceeding stage tolerances, not routine stage boundaries or strategic requests.

How to eliminate wrong answers

Option A is wrong because the project closing is managed by the Closing a Project process, not by an Exception Plan. Option C is wrong because a new stage beginning is a normal planned event managed by the Managing a Stage Boundary process, not an exception. Option D is wrong because the Project Board does not request an Exception Plan for strategic reasons; it is only triggered by a forecast tolerance deviation.

243
MCQmedium

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

A.Project Manager
B.Project Board
C.Project Support
D.Team Manager
AnswerD

Within Managing Product Delivery, the Team Manager produces Checkpoint Reports to inform the Project Manager of work package progress, typically at agreed intervals. Work Package status and quality register updates flow from this role, not from the Project Board or Project Assurance.

Why this answer

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports during the Managing Product Delivery process. These reports provide the Project Manager with progress updates on work packages, including actual versus planned progress, quality activities, and any issues or risks. The Team Manager is the role that manages the day-to-day work of the team and reports back to the Project Manager.

Exam trap

The trap here is that candidates often confuse the roles of Project Manager and Team Manager, assuming the Project Manager produces all reports, but PRINCE2 specifically assigns Checkpoint Reports to the Team Manager to maintain clear delegation and control.

How to eliminate wrong answers

Option A is wrong because the Project Manager receives Checkpoint Reports but does not produce them; they are produced by the Team Manager. Option B is wrong because the Project Board does not produce Checkpoint Reports; they receive higher-level reports like Highlight Reports from the Project Manager. Option C is wrong because Project Support assists with administrative tasks and may help compile data, but the responsibility for producing Checkpoint Reports lies with the Team Manager.

244
MCQeasy

Which PRINCE2 process produces the Project Initiation Documentation (PID)?

A.Managing a Stage Boundary
B.Starting Up a Project
C.Initiating a Project
D.Directing a Project
AnswerC

Initiating a Project assembles the PID, basing it on the Project Brief and the four strategy documents. This process satisfies the stem's requirement by producing the PID as its principal output, alongside the business case and project controls, before the project board authorises the next stage.

Why this answer

The Project Initiation Documentation (PID) is produced during the Initiating a Project process. This process refines the project's business justification, establishes the project management team, and creates the PID as the definitive reference document for how the project will be managed, including plans, controls, and tolerances.

Exam trap

PeopleCert often tests the distinction between the Project Brief (produced in Starting Up a Project) and the PID (produced in Initiating a Project), leading candidates to confuse the two documents and their respective processes.

How to eliminate wrong answers

Option A is wrong because Managing a Stage Boundary focuses on providing information to the Project Board for stage-end decisions and updating the business case, not on creating the PID. Option B is wrong because Starting Up a Project produces the Project Brief and the initiation stage plan, but the PID is not created until the subsequent Initiating a Project process. Option D is wrong because Directing a Project is the process for the Project Board to make key decisions and provide overall control, but it does not produce the PID; it authorizes the work that leads to its creation.

245
MCQhard

A project is in the Managing a Stage Boundary process. The Project Manager has produced an End Stage Report. What else must be produced?

A.Benefits Review Plan
B.Stage Plan for the next stage
C.Project Initiation Documentation
D.Project Brief
AnswerB

Managing a Stage Boundary requires both an End Stage Report reviewing performance and a Stage Plan for the next stage, which the Project Board needs to authorise continuation. The next Stage Plan supplies the forecast, products, tolerances and resources the Board evaluates alongside the End Stage Report.

Why this answer

In the Managing a Stage Boundary process, the Project Manager produces an End Stage Report to summarize the current stage's performance. The PRINCE2 method requires that a Stage Plan for the next stage must also be produced during this process, as it provides the detailed plan for the upcoming work and is essential for the Project Board to authorize the next stage. Without the next Stage Plan, the project cannot proceed beyond the current stage boundary.

Exam trap

The trap here is that candidates often confuse the End Stage Report with the only output of the Managing a Stage Boundary process, forgetting that the next Stage Plan is a mandatory parallel output to enable stage authorization.

How to eliminate wrong answers

Option A is wrong because the Benefits Review Plan is created during the Initiating a Project process and is updated throughout the project, not specifically produced during Managing a Stage Boundary. Option C is wrong because the Project Initiation Documentation (PID) is created during the Initiating a Project process and provides the baseline for the project, not produced at a stage boundary. Option D is wrong because the Project Brief is an input to the Initiating a Project process and is used to create the PID, not produced during Managing a Stage Boundary.

246
MCQhard

A project is nearing the end of its final stage. The Project Manager has prepared the End Project Report and a Lessons Report. Which process is responsible for authorising the project closure?

A.Closing a Project
B.Managing a Stage Boundary
C.Directing a Project
D.Controlling a Stage
AnswerC

Directing a Project authorises project closure via the Project Board, which approves the End Project Report and Lessons Report at the final stage boundary. This satisfies the stem's requirement for the process that authorises closure, not the one that prepares it.

Why this answer

In PRINCE2, the 'Directing a Project' process is responsible for authorising project closure. The Project Board, which operates within the Directing a Project process, reviews the End Project Report and Lessons Report and gives final approval to close the project. This authorisation is a key decision point that confirms the project has delivered its objectives and can be formally closed.

Exam trap

PRINCE2 Foundation often tests the confusion between 'Closing a Project' (which prepares closure) and 'Directing a Project' (which authorises closure) — candidates must remember that authorisation is always a Project Board responsibility under Directing a Project.

How to eliminate wrong answers

Option A is wrong because 'Closing a Project' is the process that prepares the End Project Report and Lessons Report and performs the closure activities, but it does not authorise the closure — that authority lies with the Project Board in Directing a Project. Option B is wrong because 'Managing a Stage Boundary' is used at the end of each stage (except the final stage) to prepare for the next stage and update the project plan; it does not authorise project closure. Option D is wrong because 'Controlling a Stage' is the day-to-day management of a stage by the Project Manager, not the authorisation of project closure.

247
MCQeasy

Which process is responsible for producing the Project Brief?

A.Directing a Project
B.Initiating a Project
C.Starting Up a Project
D.Controlling a Stage
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

248
MCQmedium

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

A.Controlling a Stage
B.Managing a Stage Boundary
C.Managing Product Delivery
D.Initiating a Project
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

249
MCQhard

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

A.SU produces the Project Plan; IP produces the Stage Plan
B.SU is performed before the Project Board authorizes initiation; IP is performed after
C.SU is optional; IP is mandatory
D.SU appoints the Project Manager; IP appoints the Executive
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

250
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

251
MCQmedium

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

A.Project Manager
B.Team Manager
C.Project Support
D.Project Board
AnswerB

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

Why this answer

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

252
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

253
MCQmedium

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

A.Authorize the next stage as planned
B.Request a new Project Brief
C.Assess the situation and, if appropriate, approve an Exception Plan
D.Instruct the Project Manager to continue with the current plan
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

254
MCQmedium

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

A.Raise an Exception Report
B.Update the Project Plan
C.Close the project stage
D.Deliver the Work Package to the Project Manager
AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

255
MCQhard

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

A.To produce the Lessons Report
B.To hand over the project products to the operational environment
C.To confirm the project has met its objectives and authorize closure
D.To release the project resources
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

256
MCQmedium

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

A.Exception Report
B.End Project Report
C.End Stage Report
D.Project Brief
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

257
Multi-Selecthard

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

Select 3 answers
A.Authorize Work Packages
B.Produce the Project Initiation Documentation (PID)
C.Review progress and update stage status
D.Approve the next Stage Plan
E.Escalate issues and risks that exceed stage tolerances
AnswersA, C, E

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

Why this answer

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

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

Exam trap

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

258
MCQeasy

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

A.Producing Highlight Reports
B.Authorizing the next Stage Plan
C.Managing day-to-day work within a stage
D.Accepting Work Packages
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

259
MCQmedium

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

A.Team Manager
B.Project Manager
C.Project Board
D.Project Support
AnswerA

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

Why this answer

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

260
MCQmedium

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

A.Escalate the exception to the Project Board immediately by producing an Exception Report for the stage.
B.Assess the exception against the stage tolerances and consider corrective action before escalating.
C.Instruct the Team Manager to stop all work on the work package and await a new Work Package.
D.Authorize the Team Manager to continue and record the issue in the Issue Register without further action.
AnswerB

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

Why this answer

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

Exam trap

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

261
MCQmedium

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

A.Project Initiation Documentation
B.End Stage Report
C.Project Brief
D.Business Case
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

262
Multi-Selecteasy

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

Select 2 answers
A.Project Initiation Documentation
B.End Stage Report
C.Stage Plan for the next stage
D.Initiation Stage Plan
E.Project Brief
AnswersD, E

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

Why this answer

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

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

Exam trap

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

263
MCQeasy

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

A.To confirm the project's scope and high-level risks before the project mandate is issued.
B.To authorize work packages for the first stage of the project.
C.To develop a detailed justification for the project and confirm it remains viable.
D.To obtain final approval from the project board before project execution begins.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

264
MCQmedium

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

A.Controlling a Stage
B.Starting Up a Project
C.Directing a Project
D.Initiating a Project
AnswerC

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

Why this answer

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

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

Exam trap

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

How to eliminate wrong answers

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

265
MCQmedium

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

A.Escalate directly to the Project Board by raising an Exception Report.
B.Instruct the Team Manager to stop all work on the work package immediately and await further instruction.
C.Record the deviation in the Issue Register and take corrective action within the stage, consulting the Team Manager.
D.Amend the Business Case to reflect the increased cost before any further work continues.
AnswerC

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

Why this answer

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

Exam trap

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

266
MCQmedium

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

A.Approve the Exception Report
B.Request a new Project Plan
C.Request an Exception Plan to assess options
D.Close the project
AnswerC

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

Why this answer

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

267
MCQhard

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

A.Authorize a work package to the Team Manager for the next stage
B.Request authorization to start the next stage from the Project Board
C.Produce a Highlight Report for the Project Board
D.Produce an Exception Report if the stage is forecast to exceed its tolerances
AnswerB

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

Why this answer

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

Exam trap

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

268
MCQhard

In the Managing a Stage Boundary process, the Project Manager updates the Project Plan. What is the main purpose of this update?

A.To reflect the actual progress and re-forecast the remaining work
B.To provide a baseline for performance measurement
C.To replace the original Project Plan entirely
D.To create a detailed plan for the next stage only
AnswerA

Updating the Project Plan at a stage boundary incorporates actual progress and re-forecasts remaining work for the next stage. This satisfies the process's purpose of providing the Project Board with a realistic, revised baseline before authorising continuation.

Why this answer

In PRINCE2, the Managing a Stage Boundary process is triggered at the end of each stage to allow the Project Board to review progress and authorize the next stage. As part of this process, the Project Manager updates the Project Plan to reflect actual progress achieved during the ending stage and to re-forecast the remaining work, costs, and timelines. This keeps the Project Plan as a living document that accurately represents the current view of the entire project.

Exam trap

PRINCE2F often tests the confusion between the Project Plan (whole project, updated at stage boundaries) and the Stage Plan (next stage only, created at stage boundaries) — candidates frequently pick the Stage Plan answer when the question asks about the Project Plan.

How to eliminate wrong answers

Option B is wrong because providing a baseline for performance measurement is the purpose of the Project Initiation Documentation (PID) and the original baselined Project Plan, not the update performed during Managing a Stage Boundary. Option C is wrong because the Project Plan is updated, not replaced — PRINCE2 emphasizes maintaining continuity of the plan with tolerances and baselines intact. Option D is wrong because creating a detailed plan for the next stage is the purpose of the Stage Plan, which is a separate product produced during Managing a Stage Boundary, not the Project Plan update.

269
MCQhard

The Project Board gives ad-hoc direction during which process?

A.Controlling a Stage
B.Starting Up a Project
C.Managing a Stage Boundary
D.Directing a Project
AnswerD

Directing a Project is the Project Board's own process, covering ad-hoc direction and decisions throughout the project's life rather than at defined stage boundaries. It satisfies the stem's requirement for ad-hoc direction, since Managing a Stage Boundary handles only end-of-stage authorisation requests.

Why this answer

In PRINCE2, the Project Board provides ad-hoc direction during the 'Directing a Project' process, which runs from project start to closure and enables the Board to make decisions and give guidance outside of formal stage boundaries. This process is specifically designed for the Board to manage by exception and respond to issues or exceptions raised by the Project Manager.

Exam trap

PRINCE2F often tests the specific process where the Project Board gives ad-hoc direction, and candidates may confuse it with 'Managing a Stage Boundary' or 'Controlling a Stage' because those involve Board interactions at stage ends.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage is the Project Manager's process for day-to-day management, not where the Board gives ad-hoc direction. Option B is wrong because Starting Up a Project is a pre-project process where the Project Board appoints the Project Manager and approves the project brief, but it is not the ongoing ad-hoc direction process. Option C is wrong because Managing a Stage Boundary is a process for preparing for the next stage, not for ad-hoc direction.

270
Multi-Selectmedium

Which THREE of the following are activities of the Managing a Stage Boundary process?

Select 3 answers
A.Hand over products to the customer
B.Update the Project Plan
C.Plan the next stage
D.Authorize Work Packages
E.Produce an End Stage Report
AnswersB, C, E

Updating the Project Plan is a Managing a Stage Boundary activity: the next stage plan's products, activities and resources are incorporated into the overall Project Plan before the stage boundary is reported to the project board for approval.

Why this answer

Option B (Update the Project Plan) is correct because Managing a Stage Boundary includes updating the Project Plan with actual progress, revised forecasts, and any approved changes before the next stage begins. Option C (Plan the next stage) is correct because a core activity of this process is preparing the Next Stage Plan (or Exception Plan) for the following stage. Option E (Produce an End Stage Report) is correct because the End Stage Report is a key output of Managing a Stage Boundary, summarizing stage performance and providing the basis for the End Stage Assessment.

Option A (Hand over products to the customer) does not belong because product handover occurs in Closing a Project, and Option D (Authorize Work Packages) does not belong because that activity is performed in Controlling a Stage.

Exam trap

PRINCE2F often tests whether candidates confuse Managing a Stage Boundary activities with Controlling a Stage activities (like Authorize Work Packages) or Closing a Project activities (like handover).

271
MCQhard

Which report from the Team Manager is used by the Project Manager to review progress within a stage?

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

The Checkpoint Report is the Team Manager's regular progress report to the Project Manager, covering work completed, work in progress and issues within the current stage. It directly satisfies the stem's requirement to review progress within a stage, feeding the Highlight Report cycle rather than end-stage reporting.

Why this answer

The Checkpoint Report is the Team Manager's regular progress report to the Project Manager, produced at a frequency defined in the Work Package (often weekly or at agreed checkpoints). It summarizes progress, issues, and forecast against the Work Package, giving the Project Manager visibility within a stage. This is distinct from stage-level or project-board-level reports.

Exam trap

PRINCE2F often tests the role-to-report mapping, so the trap is confusing the Team Manager's Checkpoint Report with the Project Manager's Highlight Report because both describe progress within a stage.

How to eliminate wrong answers

Option A is wrong because the Highlight Report is produced by the Project Manager for the Project Board to summarize stage progress at agreed intervals, not by the Team Manager for the Project Manager. Option B is wrong because the End Stage Report is created by the Project Manager at the end of a stage to summarize performance and request authorization for the next stage. Option C is wrong because an Exception Report is produced by the Project Manager when a stage or project is forecast to exceed tolerances, and is escalated to the Project Board.

272
MCQmedium

Who is responsible for reviewing the End Stage Report and deciding whether to authorize the next stage?

A.Project Manager
B.Executive
C.Senior User
D.Project Board
AnswerD

The Project Board reviews the End Stage Report at each stage boundary and decides whether to authorise the next stage. This is a Directing a Project decision, taken on the Managing a Stage Boundary output.

Why this answer

The Project Board is responsible for reviewing the End Stage Report and deciding whether to authorize the next stage. This is a key governance point in PRINCE2, where the Project Board assesses the current stage's performance against the plan and approves moving forward.

Exam trap

PeopleCert often tests the misconception that the Project Manager has the authority to authorize the next stage, but in PRINCE2, the Project Manager only recommends, while the Project Board decides.

How to eliminate wrong answers

Option A is wrong because the Project Manager creates the End Stage Report and presents it to the Project Board, but does not have the authority to authorize the next stage. Option B is wrong because the Executive is a member of the Project Board, but the decision to authorize the next stage is a collective Project Board responsibility, not an individual one. Option C is wrong because the Senior User is also a member of the Project Board, but the authorization decision requires the full board, not just the user representative.

273
MCQmedium

During which process are the Benefits Management Approach and the Risk Management Approach first created?

A.Directing a Project
B.Managing a Stage Boundary
C.Initiating a Project
D.Starting Up a Project
AnswerC

Initiating a Project produces the Benefits Management Approach and the Risk Management Approach as part of the Project Initiation Documentation, satisfying the requirement that these strategies are established before the project proceeds. Starting Up a Project only drafts the outline Business Case, so the approaches are first created here.

Why this answer

The Benefits Management Approach and Risk Management Approach are both created during the Initiating a Project process, as part of the Project Initiation Documentation (PID). This process establishes the overall project strategies and baselines before the first stage begins, so the approaches that govern benefits realization and risk handling are defined here.

Exam trap

PRINCE2F often tests the boundary between Starting Up a Project and Initiating a Project, so the trap is assuming the Risk Management Approach is created in Starting Up a Project because risk is discussed there in outline form.

How to eliminate wrong answers

Option A is wrong because Directing a Project is the Project Board's decision-making process (authorizing stages, tolerances, closure) and does not create management approaches. Option B is wrong because Managing a Stage Boundary reviews and updates existing approaches at stage end, but does not first create them. Option D is wrong because Starting Up a Project produces the Project Brief and Business Case outline, but the formal Benefits Management Approach and Risk Management Approach are created later in Initiating a Project.

274
MCQeasy

A PRINCE2 project is in the Closing a Project process. The Project Manager is preparing for the final closure. Which activity is performed during this process?

A.Authorise the project closure.
B.Confirm that all products have been delivered and accepted.
C.Prepare the next Stage Plan.
D.Hand over the project's products to the operational environment.
AnswerB

Confirming that all products have been delivered and accepted is a key activity in Closing a Project. The Project Manager ensures that all outputs meet the agreed quality criteria and have been formally accepted by the customer or operational environment. This confirmation is essential before the project can be closed, as it verifies that the project has achieved its objectives.

Why this answer

In Closing a Project, the Project Manager confirms that all products have been delivered and accepted according to the quality criteria. This activity ensures that the project has met its objectives and that there are no outstanding issues. The Project Board then authorises project closure based on the End Project Report.

Handing over products occurs in Managing Product Delivery, and preparing the next Stage Plan is part of Managing a Stage Boundary.

Exam trap

The trap here is thinking that the Project Manager authorises project closure, when in fact that is a Project Board decision made in Directing a Project.

275
MCQmedium

A project is in the Initiating a Project process. Which document is the key output that defines how the project will be managed?

A.Stage Plan
B.Project Brief
C.Business Case
D.Project Initiation Documentation
AnswerD

The Project Initiation Documentation consolidates the business case, project plan, controls and governance approach, defining how the project will be managed. It is assembled during Initiating a Project and approved by the project board before delivery begins.

Why this answer

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and other management strategies into a single, controlled document that defines how the project will be managed, controlled, and executed. The PID serves as the foundation for decision-making and is used throughout the project lifecycle.

Exam trap

The trap here is that candidates often confuse the Project Brief (a pre-initiation document) with the Project Initiation Documentation (the formal management document produced during initiation), or they mistakenly think the Business Case alone defines how the project is managed.

How to eliminate wrong answers

Option A is wrong because a Stage Plan is a detailed plan for a specific management stage, not the overarching document that defines how the entire project will be managed. Option B is wrong because the Project Brief is created during the Starting Up a Project process and provides initial context and justification, but it is refined and expanded into the PID during Initiating a Project. Option C is wrong because the Business Case is a key component within the PID that justifies the project's viability, but it is not the comprehensive management document itself.

276
MCQhard

During the Managing Product Delivery process, a Team Manager identifies a quality issue that will delay the delivery of a Work Package. What should the Team Manager do?

A.Update the project plan to reflect the delay
B.Issue a Checkpoint Report to the Project Board
C.Raise an issue to the Project Manager
D.Authorize corrective action to resolve the quality issue
AnswerC

The Team Manager works within tolerances agreed in the Work Package. A quality issue threatening delivery time breaches those tolerances, so it must be escalated as an issue to the Project Manager, who owns the project-level response and any change to the plan.

Why this answer

In PRINCE2, the Team Manager reports to the Project Manager, not directly to the Project Board. When a quality issue threatens Work Package delivery, the Team Manager must escalate by raising an issue (via the Issue Report) to the Project Manager, who then decides on corrective action. This aligns with the Managing Product Delivery process, where the Team Manager's responsibility is to inform the Project Manager of any deviations.

Exam trap

A common misconception in PRINCE2 is that the Team Manager can directly communicate with the Project Board or authorize corrective actions, but PRINCE2 strictly enforces the reporting line: Team Manager → Project Manager → Project Board.

How to eliminate wrong answers

Option A is wrong because the Team Manager does not have authority to update the project plan; that is the Project Manager's responsibility. Option B is wrong because Checkpoint Reports are sent to the Project Manager, not the Project Board, and they are used for regular progress updates, not for escalating issues. Option D is wrong because the Team Manager cannot authorize corrective action; that authority rests with the Project Manager or, for exception situations, the Project Board.

277
MCQmedium

A project is in the Controlling a Stage process. The Project Manager has just reviewed a completed Work Package, confirmed that all products met their quality criteria, and updated the Stage Plan. According to PRINCE2, which action should the Project Manager take NEXT?

A.Update the Benefits Review Plan to reflect the completion of the stage's products.
B.Escalate the completion to the Project Board by raising an Exception Report.
C.Authorise the next Work Package or, if the stage is complete, prepare for the Managing a Stage Boundary process.
D.Close the project immediately because the final products have been delivered.
AnswerC

After accepting a completed Work Package in Controlling a Stage, the Project Manager must review work package status and decide whether to authorise the next Work Package or, if all stage work is done, trigger the Managing a Stage Boundary process. This keeps the stage progressing and ensures the stage is properly closed or continued according to the Stage Plan.

Why this answer

In Controlling a Stage, once a Work Package is accepted and the Stage Plan is updated, the Project Manager reviews work package status and decides the next action. That could be authorising the next Work Package or, if all stage products are complete, preparing for Managing a Stage Boundary. Escalation or project closure would only apply in different circumstances.

Exam trap

The trap here is assuming that accepting a completed Work Package automatically triggers stage closure or project closure, rather than the routine decision to authorise further work or move to the stage boundary.

278
MCQhard

What is the difference between Starting Up a Project and Initiating a Project?

A.SU is a pre-project process; IP formally initiates the project
B.SU is performed after IP
C.SU produces the PID; IP produces the Project Brief
D.SU is performed by the Project Board; IP is performed by the Project Manager
AnswerA

Starting Up a Project is a pre-project process, occurring before the project board authorises the project, and its output is the project brief. Initiating a Project then formally begins once that authorisation exists, producing the project initiation documentation and the PID-based baseline. This sequencing satisfies the stem's distinction between pre-project preparation and formal project initiation.

Why this answer

Starting Up a Project (SU) is the pre-project process that ensures the prerequisites for initiating the project are in place — it appoints the executive and project manager and produces the Project Brief. Initiating a Project (IP) then formally begins the project by building the Project Initiation Documentation (PID) and obtaining Project Board authorization.

Exam trap

PRINCE2 Foundation often tests the sequence and outputs of SU versus IP, so candidates who confuse the Project Brief (SU output) with the PID (IP output) or reverse the process order pick the wrong answer.

How to eliminate wrong answers

Option B is wrong because it reverses the sequence — SU precedes IP, not the other way around. Option C is wrong because it swaps the outputs: SU produces the Project Brief (and Daily Log, Lessons Log), while IP produces the PID. Option D is wrong because both processes are primarily the responsibility of the Project Manager, not the Project Board; the Project Board authorizes via Directing a Project (DP) but does not perform SU or IP.

279
MCQmedium

A project is nearing the end of its final stage and all products have been delivered and accepted. The Project Manager needs to prepare the information required for the Project Board to confirm that the project can be closed. Which activity belongs to the Closing a Project process?

A.Confirming that all products have been handed over to the operational and maintenance environment and that acceptance has been recorded.
B.Updating the Business Case to reflect the benefits realised so far and forecasting the remainder.
C.Producing the End Stage Report to summarise the final stage's performance for the Project Board.
D.Authorising the final Work Package so the last products can be delivered before closure begins.
AnswerA

Closing a Project verifies that the project has delivered what was defined in the Project Product Description, including handover and acceptance. Confirming handover and recording acceptance is a core closing activity because it demonstrates that the products are now in operational use and the project's obligations to the user are complete.

Why this answer

Closing a Project confirms that the project's products have been delivered, accepted and handed over, and that the project can be closed. Handover and acceptance are central to that confirmation. End Stage Reports, Business Case updates and Work Package authorisation belong to other processes and do not by themselves establish that closure criteria are met.

Exam trap

The trap here is equating any end-of-project documentation with closure, when Closing a Project specifically confirms handover and acceptance of the products.

280
MCQmedium

During the Controlling a Stage process, which report does the Project Manager send to the Project Board?

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

The Highlight Report provides the Project Board with a periodic summary of stage progress, status and forecasts during the Controlling a Stage process, satisfying the stem's requirement for a report sent to that board. Work Package status goes to the Team Manager, while Checkpoint Reports flow upward from teams, not to the board.

Why this answer

In the Controlling a Stage process, the Project Manager sends the Highlight Report to the Project Board at regular intervals to provide a summary of progress against the stage plan, including achievements, next steps, and any issues or risks. This report is the standard communication tool for keeping the board informed during a stage, as defined in PRINCE2.

Exam trap

In PRINCE2, candidates often confuse the Checkpoint Report (sent to the Project Manager by team managers) with the Highlight Report (sent to the Project Board by the Project Manager) due to their similar names and periodic nature. This distinction is critical in the Controlling a Stage process.

How to eliminate wrong answers

Option A is wrong because the Exception Report is sent only when a stage plan is forecast to exceed tolerance levels, not as a routine report during Controlling a Stage. Option B is wrong because the Checkpoint Report is a team-level report from Team Managers to the Project Manager, not to the Project Board. Option C is wrong because the End Stage Report is produced at the end of a stage during the Managing a Stage Boundary process, not during Controlling a Stage.

281
MCQmedium

According to PRINCE2, which process is responsible for ensuring that the project has a clear and agreed start before any substantial work is undertaken?

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

Starting Up a Project creates the project mandate's response, appoints the Project Board and Project Manager, and produces the Project Brief, giving the Project Board the information needed to authorise initiation before substantial work begins.

Why this answer

In PRINCE2, 'Starting Up a Project' (SU) is the pre-project process that ensures the project has a clear and agreed start before any substantial work is undertaken. It produces the Project Brief, appoints the Project Board and Project Manager, and captures the lessons log and project approach, culminating in the 'Authorize Initiation' decision by the Project Board. Only after this authorization does the project move into Initiating a Project.

Exam trap

PRINCE2F often tests the confusion between 'Starting Up a Project' (pre-project, produces Project Brief) and 'Initiating a Project' (produces PID) — candidates frequently pick the latter because it sounds like the project's formal start.

How to eliminate wrong answers

Option A is wrong because 'Initiating a Project' happens after Starting Up a Project and focuses on building the PID (business case, plans, controls) — it assumes the project has already been authorized to initiate. Option C is wrong because 'Directing a Project' is the ongoing Project Board process that provides overall direction and decision-making throughout the project, not the pre-project startup. Option D is wrong because 'Controlling a Stage' is the Project Manager's day-to-day delivery process within a stage, which occurs well after the project has started.

282
MCQhard

What is the primary difference between Managing Product Delivery and Controlling a Stage?

A.Managing Product Delivery focuses on the Team Manager delivering Work Packages; Controlling a Stage focuses on the Project Manager's day-to-day management
B.Managing Product Delivery produces the Highlight Report
C.Managing Product Delivery is only used in the Initiating a Project process
D.Managing Product Delivery is the Project Manager's process; Controlling a Stage is the Team Manager's process
AnswerA

Managing Product Delivery assigns the Team Manager responsibility for accepting and executing Work Packages, while Controlling a Stage covers the Project Manager's day-to-day monitoring, issue handling and progress review within a stage. This split satisfies the stem's focus on role-based responsibility boundaries between delivery and stage control.

Why this answer

Managing Product Delivery is the process where the Team Manager accepts, executes, and delivers Work Packages, while Controlling a Stage is the Project Manager's process for day-to-day monitoring and control of the stage. The two processes operate at different levels and with different role ownership, which is the core distinction the question tests.

Exam trap

PRINCE2F often tests role-to-process mapping — candidates reverse the Project Manager and Team Manager ownership of Controlling a Stage versus Managing Product Delivery.

How to eliminate wrong answers

Option B is wrong because the Highlight Report is produced by the Project Manager in the Controlling a Stage process, not by Managing Product Delivery. Option C is wrong because Managing Product Delivery is used throughout the delivery stages whenever Work Packages are executed, not only during Initiating a Project. Option D is wrong because it reverses the roles — Managing Product Delivery is the Team Manager's process, and Controlling a Stage is the Project Manager's process.

283
MCQmedium

A Project Manager is about to begin work on a new stage. Which document provides the authority to proceed with the stage?

A.Project Brief
B.Stage Plan
C.Project Initiation Documentation
D.Business Case
AnswerB

The Stage Plan, approved by the Project Board, contains the authorisation to proceed; the 'authorise a stage or exception plan' activity grants that authority. Without an approved Stage Plan the Project Manager cannot start stage work, so it is the document providing the go-ahead.

Why this answer

In PRINCE2, the Stage Plan is the document that, once approved by the Project Board, provides the authority to proceed with that specific stage. The 'authorize a stage' activity within the Directing a Project process uses the Stage Plan as the basis for the Project Board's decision. Without an approved Stage Plan, the Project Manager cannot legitimately start work on the stage.

Exam trap

PRINCE2F often tests the distinction between the PID (which authorizes the project) and the Stage Plan (which authorizes each stage), causing candidates to select the PID for stage-level authority questions.

How to eliminate wrong answers

Option A is wrong because the Project Brief is a pre-project document used during Starting Up a Project to define the initial scope and justification; it does not authorize stage work. Option C is wrong because the Project Initiation Documentation authorizes the project as a whole (via the 'authorize the project' activity), not an individual stage. Option D is wrong because the Business Case is a justification document that is reviewed and updated, but it is not the authority mechanism for proceeding with a stage.

284
MCQeasy

Which process ensures that the project's products are handed over and the project is formally closed?

A.Controlling a Stage
B.Managing a Stage Boundary
C.Directing a Project
D.Closing a Project
AnswerD

Closing a Project confirms acceptance of the project's products, reviews benefits against the Business Case, and formally disbands the project. It satisfies the stem's requirement for handover and formal closure, unlike Managing a Stage Boundary, which only prepares for the next stage.

Why this answer

Closing a Project is the PRINCE2 process that ensures the project's products are handed over to the customer or operations and that the project is formally closed. It covers acceptance of the products, confirmation of closure, and lessons learned. The other processes deal with stage-level control, stage boundaries, or project direction, not final closure.

Exam trap

PRINCE2F often tests whether candidates confuse stage-level processes with the project-level closure process — the trap is selecting Managing a Stage Boundary because it sounds like the end of a stage, when the question is about formally closing the entire project.

How to eliminate wrong answers

Option A is wrong because Controlling a Stage is about day-to-day management of a stage, including work package authorization and progress monitoring, not project closure. Option B is wrong because Managing a Stage Boundary prepares for the next stage or an exception, and does not close the project. Option C is wrong because Directing a Project is the board-level process that provides overall direction and authorizes the project, not the process that hands over products and closes it.

285
Multi-Selecthard

Which THREE of the following are responsibilities of the Project Manager during the Controlling a Stage process?

Select 3 answers
A.Authorizing Work Packages
B.Producing Checkpoint Reports
C.Reviewing the Business Case
D.Escalating issues and risks that exceed stage tolerances
E.Reviewing the progress of the stage against the Stage Plan
AnswersA, D, E

Correct. PM authorizes Work Packages in CS.

Why this answer

During the Controlling a Stage process, the Project Manager authorizes Work Packages to assign work to Team Managers or team members, ensuring that the work is formally allocated and controlled. This authorization is a key responsibility to maintain alignment with the Stage Plan and manage the delivery of products.

Exam trap

PRINCE2 often tests the distinction between the Project Manager's operational responsibilities (like authorizing Work Packages and escalating exceptions) versus the Team Manager's reporting duties (like producing Checkpoint Reports), leading candidates to confuse who produces versus who reviews reports.

286
MCQmedium

A Project Manager is midway through a stage when a Work Package is completed and the Team Manager returns it for acceptance. The products have met their quality criteria, but the Project Manager notices that a required specialist resource was used for longer than the Work Package had authorised. Which action should the Project Manager take FIRST?

A.Raise an Exception Report immediately to the Project Board requesting a change to the stage budget.
B.Accept the Work Package and log the resource overrun as a lesson in the Lessons Log.
C.Reject the Work Package and instruct the Team Manager to redo the work within the authorised resource limit.
D.Assess the resource overrun against the current Stage Plan and stage tolerances before deciding whether to accept the Work Package.
AnswerD

The Project Manager is accountable for controlling the stage, so any deviation revealed on Work Package completion must be evaluated against the Stage Plan and the delegated stage tolerances. This assessment determines whether the overrun is tolerable, requiring corrective action within the stage, or whether it constitutes an exception that must be escalated to the Project Board.

Why this answer

When a Work Package is completed, the Project Manager must confirm that the products conform and check whether the work stayed within its authorised limits. Any resource variance must be measured against the Stage Plan and the delegated stage tolerances, because that comparison determines whether the Project Manager can correct the situation within the stage or must escalate it as an exception to the Project Board.

Exam trap

The trap here is assuming that a completed Work Package must be accepted or rejected purely on product quality, ignoring that the Project Manager must also assess schedule, cost and resource deviations against stage tolerances before deciding.

287
MCQmedium

The Project Board has authorized a Stage Plan. During the stage, the Project Manager identifies a risk that could cause the stage to exceed its time tolerance. What should the Project Manager do first?

A.Inform the Team Manager to accelerate work to stay within tolerance
B.Raise an Exception Report to the Project Board and await their direction
C.Record the risk in the Risk Register and continue monitoring
D.Implement a contingency plan to mitigate the risk and continue as planned
AnswerB

A forecast breach of stage time tolerance is an exception, so the Project Manager must escalate via an Exception Report and await Project Board direction. The Board owns tolerance decisions; the Project Manager cannot unilaterally replan beyond delegated authority.

Why this answer

In PRINCE2, if a risk materializes or is forecast to cause the stage to exceed its time tolerance, the Project Manager must escalate by raising an Exception Report to the Project Board, because tolerances are delegated by the Board and only they can authorize a change to the stage plan or tolerance. The Project Manager should not unilaterally take corrective action beyond tolerance.

Exam trap

The trap is thinking the Project Manager should 'fix it first and report later' — PRINCE2's management-by-exception principle requires escalation as soon as a tolerance breach is forecast, not after attempting corrective action.

How to eliminate wrong answers

Option A is wrong because instructing the Team Manager to accelerate work is a corrective action that may still not keep the stage within tolerance, and it bypasses the required escalation to the Project Board. Option C is wrong because simply recording the risk and monitoring is insufficient when the stage is forecast to breach tolerance — PRINCE2 requires proactive escalation. Option D is wrong because implementing a contingency plan is only appropriate if the plan is within the Project Manager's delegated tolerance; if the stage will exceed time tolerance, the exception must be escalated first.

288
MCQmedium

A Project Manager is managing a stage in a PRINCE2 project. A Team Manager reports that a work package is forecast to exceed its agreed tolerances. According to PRINCE2, what should the Project Manager do first?

A.Assess the issue and decide on the appropriate action.
B.Take corrective action to bring the work package back within tolerance.
C.Escalate the issue to the Project Board by producing an Exception Report.
D.Update the Risk Register with the potential deviation.
AnswerA

When a Team Manager reports a forecast deviation, the Project Manager must first assess the issue to understand its impact on the stage and project. This assessment involves reviewing the work package status, the tolerances, and the overall stage plan. Only after assessing can the Project Manager decide whether to take corrective action, escalate, or accept the deviation.

Why this answer

The Project Manager's first step when a work package deviation is reported is to assess the issue and its potential impact. This assessment informs the decision on whether to take corrective action, escalate, or accept the deviation. Escalation to the Project Board is only required if stage or project tolerances are threatened.

Updating the Risk Register is a secondary action.

Exam trap

The trap here is assuming that any work package deviation must be immediately escalated to the Project Board, when in fact the Project Manager should first assess and manage within stage tolerances.

289
MCQhard

A PRINCE2 project is nearing the end of a stage. The Project Manager has confirmed that all products are complete and approved, and the next Stage Plan is ready for approval. Which action should the Project Manager take to close the current stage and move to the next?

A.Produce an End Stage Report and request a decision from the Project Board at an End Stage Assessment
B.Update the Project Initiation Documentation and begin the next stage immediately
C.Raise an Exception Report to explain that the stage is complete
D.Issue a Highlight Report to the Project Board summarising stage progress
AnswerA

The Managing a Stage Boundary process requires the Project Manager to produce an End Stage Report and a next Stage Plan, then request an End Stage Assessment from the Project Board. This is the formal checkpoint where the Board reviews performance and authorises the next stage. Without this authorisation, the project cannot legitimately proceed to the next stage.

Why this answer

Closing a stage and moving to the next is governed by the Managing a Stage Boundary process. The Project Manager prepares an End Stage Report and the next Stage Plan, then requests an End Stage Assessment from the Project Board. The Board reviews performance, confirms continued business justification, and authorises the next stage.

This maintains the formal control point required at every stage boundary.

Exam trap

The trap here is confusing routine progress reporting (Highlight Reports) with the formal stage-boundary decision process that requires an End Stage Report and End Stage Assessment.

290
Multi-Selectmedium

Which THREE of the following are responsibilities of the Project Board during the Directing a Project process?

Select 3 answers
A.Approving stage plans and updates
B.Producing Checkpoint Reports
C.Managing the day-to-day activities of the project team
D.Authorising closure of the project
E.Authorising initiation of the project
AnswersA, D, E

Approving stage plans and updates falls to the Project Board, satisfying the Directing a Project requirement for authorising each management stage. Under PRINCE2, the Board grants stage boundaries through the "Authorise a Stage or Exception Plan" activity, retaining accountability for continued business justification before work proceeds.

Why this answer

Option A is correct because in PRINCE2 the Project Board approves Stage Plans and Exception Plans (stage plan updates) as part of the 'Authorise a Stage or Exception Plan' activity within Directing a Project. Option D is correct because authorising project closure is the 'Authorise Project Closure' activity, where the Project Board confirms the project can be closed after the Closing a Project process. Option E is correct because 'Authorise Initiation' is the first activity of Directing a Project, where the Board approves the Project Brief and the initiation stage.

Option B is incorrect because Checkpoint Reports are produced by the Project Manager (or Team Manager) and reviewed by the Board, not created by it. Option C is incorrect because day-to-day management of the project team is the Project Manager's responsibility, not the Project Board's.

Exam trap

PeopleCert often tests the distinction between strategic and operational responsibilities, so the trap here is confusing the Project Board's high-level decision-making role with the Project Manager's or Team Manager's execution-level duties.

291
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.

292
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.

293
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.

294
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.

295
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.

296
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.

297
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.

298
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.

299
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.

300
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.

← PreviousPage 4 of 5 · 325 questions totalNext →

Ready to test yourself?

Try a timed practice session using only PRINCE2 Processes questions.