CCNA Prince2 People Questions — Page 3 of 4

151

Multi-Selecthard

Which THREE of the following are responsibilities of the Senior Supplier role on the Project Board?

Select 3 answers

A.Manage the team on a day-to-day basis

B.Ensure that the supplier's products meet quality requirements

C.Provide resources and expertise to deliver the project's products

D.Contribute to the Business Case from a supplier perspective

E.Approve the Stage Plans

AnswersB, C, D

Quality conformance of supplier-produced products sits with the Senior Supplier, who is accountable for the supplier's delivery meeting agreed requirements. This satisfies the stem by tying the role to assurance that delivered products satisfy their quality criteria.

Why this answer

The Senior Supplier role on the Project Board is responsible for ensuring that the supplier's products meet the agreed quality requirements. This includes providing the necessary resources and expertise to deliver the project's products, and contributing to the Business Case from a supplier perspective, particularly regarding the feasibility and cost of the supplier's work.

Exam trap

The trap here is that candidates often confuse the day-to-day management responsibilities of the Project Manager with the strategic oversight responsibilities of the Senior Supplier on the Project Board, leading them to incorrectly select Option A.

Practice this question →

152

MCQhard

Which role can delegate change control decisions to a Change Authority?

A.Project Manager

B.Project Board

C.Executive

D.Senior User

AnswerB

The Project Board owns change control, and PRINCE2 permits it to delegate decisions within agreed tolerances to a Change Authority. The Project Manager and Team Manager cannot assume that authority unless explicitly delegated, so the Board is the correct source.

Why this answer

In PRINCE2, the Project Board is responsible for overall project governance and can delegate its change control authority to a Change Authority. This delegation is formalized in the Project Initiation Documentation (PID) and allows the Change Authority to approve or reject change requests within predefined limits, such as cost or time thresholds, without needing to escalate every decision back to the Board.

Exam trap

The trap here is that candidates often confuse the Project Board with its individual members (Executive or Senior User) and mistakenly think one person can delegate change authority, but PRINCE2 requires collective Board approval for such delegation.

How to eliminate wrong answers

Option A is wrong because the Project Manager manages day-to-day activities and can recommend changes but does not have the authority to delegate change control decisions; that authority rests with the Project Board. Option C is wrong because the Executive is a single role on the Project Board, not the collective decision-making body; delegation of change control is a Board-level decision, not an individual one. Option D is wrong because the Senior User represents user interests on the Project Board but, like the Executive, cannot unilaterally delegate change authority; only the full Project Board can do so.

Practice this question →

153

MCQeasy

Which role manages the day-to-day execution of a Work Package?

A.Project Support

B.Team Manager

C.Senior User

D.Project Manager

AnswerB

The Team Manager owns day-to-day execution of a Work Package, directing the team and reporting progress to the Project Manager via Checkpoint Reports. This satisfies the stem's constraint by assigning operational delivery to the role PRINCE2 designates for it, distinct from the Project Manager's strategic, exception-based control.

Why this answer

The Team Manager is the role responsible for the day-to-day management of a Work Package within a PRINCE2 project. They report to the Project Manager and ensure that the work is completed according to the agreed tolerances, quality criteria, and schedule. This is defined in the PRINCE2 manual under the 'Organizing' theme, where the Team Manager is specifically tasked with coordinating the team's work and reporting progress.

Exam trap

The trap here is that candidates often confuse the Project Manager's overall responsibility with the Team Manager's specific duty to manage the day-to-day execution of a Work Package, leading them to incorrectly select the Project Manager.

How to eliminate wrong answers

Option A is wrong because Project Support provides administrative and advisory services to the project, such as maintaining files and providing tools, but does not manage the execution of a Work Package. Option C is wrong because the Senior User represents the interests of those who will use the project's products and specifies requirements, but does not manage day-to-day Work Package execution. Option D is wrong because the Project Manager delegates the management of Work Packages to the Team Manager and focuses on overall project planning and control, not the daily execution of individual Work Packages.

Practice this question →

154

MCQhard

A PRINCE2 project is in the 'Initiating a Project' process. The 'Project Manager' is defining the 'Project Management Team' structure. The 'Executive' wants to ensure that the 'Senior Supplier' has the authority to commit supplier resources. Which statement BEST describes the 'Senior Supplier' role?

A.The 'Senior Supplier' is accountable for the business case and ensures the project delivers value for money.

B.The 'Senior Supplier' manages the 'Project Manager' and authorizes all project expenditure.

C.The 'Senior Supplier' is responsible for specifying the user requirements and ensuring the products meet those requirements.

D.The 'Senior Supplier' represents the interests of those designing, developing, facilitating, procuring, and implementing the project's products.

AnswerD

The 'Senior Supplier' is responsible for representing the supplier community and ensuring that the supplier's resources are committed as needed. This includes those designing, developing, and implementing the products. The role provides the Project Board with confidence that the supplier's contribution is feasible and that the technical integrity of the products will be maintained. This aligns with the 'Defined roles and responsibilities' principle.

Why this answer

The 'Senior Supplier' represents the supplier interests on the Project Board, ensuring that the supplier's resources are committed and that the products are technically feasible. This role is distinct from the Executive, who owns the business case, and the Senior User, who represents user requirements. The Senior Supplier does not manage the Project Manager or control the budget; those are responsibilities of the Executive and the Project Board collectively.

Exam trap

The trap here is confusing the 'Senior Supplier' with the 'Executive' or 'Senior User', particularly regarding accountability for the business case or user requirements.

Practice this question →

155

MCQmedium

A Team Manager receives a Work Package from the Project Manager. To whom should the Team Manager report progress?

A.Project Board

B.Senior User

C.Project Assurance

D.Project Manager

AnswerD

Under PRINCE2, the Team Manager works within the Managing Product Delivery process and reports progress, issues and completed Work Packages directly to the Project Manager, who authorised the Work Package. Reporting to any other role would breach that defined line of authority.

Why this answer

In PRINCE2, the Team Manager is responsible for delivering the Work Package and reports progress directly to the Project Manager, who is the single point of accountability for the project. The Project Manager uses this information to update the Project Plan and report to the Project Board. This ensures a clear line of control and avoids bypassing the management layer.

Exam trap

The trap here is that candidates confuse the reporting line with oversight roles, assuming that Project Assurance or the Board needs direct progress updates, when PRINCE2 explicitly mandates that the Team Manager reports only to the Project Manager to preserve the single point of control.

How to eliminate wrong answers

Option A is wrong because the Project Board is the ultimate decision-making body and does not receive direct progress reports from the Team Manager; the Project Manager reports to the Board. Option B is wrong because the Senior User represents user interests and is not involved in day-to-day progress reporting from the Team Manager. Option C is wrong because Project Assurance is an independent oversight function that reviews compliance and quality, not a recipient of routine progress reports from the Team Manager.

Practice this question →

156

MCQhard

In PRINCE2, what is the difference between a Request for Change (RFC) and an Off-Specification (Off-spec)?

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

B.There is no difference; they are interchangeable terms

C.An RFC is a request to modify a product, while an Off-spec is a product that does not meet its specification

D.An RFC is always approved by the Change Authority; an Off-spec is always rejected

AnswerC

An RFC initiates a change to a baselined product, whereas an Off-spec records a product that has been produced but fails to meet its agreed specification. The stem asks for the difference, and this option correctly separates a change request from a non-conforming deliverable.

Why this answer

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a product, its specification, or the project's baseline, while an Off-Specification (Off-spec) is a product that has been completed but does not meet its agreed specification. The key distinction is that an RFC seeks to change what is required, whereas an Off-spec identifies a deviation from what was required.

Exam trap

The trap here is that candidates confuse the raising authority or approval outcome with the core definition, leading them to choose options that describe procedural roles rather than the fundamental difference in what each term represents.

How to eliminate wrong answers

Option A is wrong because both RFCs and Off-specs can be raised by any project stakeholder, not exclusively by the Project Board or Project Manager; the Project Board may approve them, but raising is not restricted. Option B is wrong because RFC and Off-spec are distinct concepts with different definitions and purposes in PRINCE2; they are not interchangeable. Option D is wrong because an Off-spec is not always rejected; it may be accepted as a concession if the deviation is deemed acceptable, and an RFC is not always approved by the Change Authority—it can be rejected or deferred.

Practice this question →

157

MCQeasy

Who is responsible for managing the delivery of a Work Package?

A.Project Manager

B.Senior User

C.Team Manager

D.Project Support

AnswerC

The Team Manager accepts the Work Package from the Project Manager and is accountable for its day-to-day delivery, allocating work and reporting progress via Checkpoint Reports. This satisfies the stem's constraint: PRINCE2 assigns delivery management to the Team Manager role, distinct from the Project Manager's overall project accountability.

Why this answer

The Team Manager is responsible for the delivery of one or more Work Packages and reports progress to the Project Manager.

Practice this question →

158

MCQmedium

Which of the following is NOT a role in the PRINCE2 project management team?

A.Project Sponsor

B.Change Authority

C.Team Manager

D.Project Manager

AnswerA

PRINCE2 defines the Project Board with Executive, Senior User and Senior Supplier roles, plus Project Manager, Team Manager and Project Assurance. 'Project Sponsor' is not a PRINCE2 term; that responsibility maps to the Executive, making this the non-role.

Why this answer

The PRINCE2 project management team structure includes the Project Board (Executive, Senior User, Senior Supplier), Project Manager, Team Manager, and optionally the Change Authority. The Project Sponsor is not a defined role in PRINCE2; instead, the Executive role fulfills the sponsorship responsibilities. Therefore, option A is correct as the role that does NOT exist in the PRINCE2 framework.

Exam trap

The trap here is that candidates often confuse the generic term 'Project Sponsor' with the PRINCE2-specific 'Executive' role, leading them to incorrectly select a wrong option like Change Authority or Team Manager.

How to eliminate wrong answers

Option A is correct because 'Project Sponsor' is not a PRINCE2 role; the Executive is the equivalent. Option B is wrong because Change Authority is a valid PRINCE2 role, responsible for authorizing change requests within delegated limits. Option C is wrong because Team Manager is a valid PRINCE2 role, responsible for delivering the work packages assigned by the Project Manager.

Option D is wrong because Project Manager is a core PRINCE2 role, managing the day-to-day project activities and reporting to the Project Board.

Practice this question →

159

MCQmedium

Which role is responsible for providing independent assurance to the Project Board that the project is on track?

A.Senior User

B.Project Support

C.Project Assurance

D.Project Manager

AnswerC

Project Assurance provides the Project Board with independent, objective scrutiny of the project's performance and viability, separate from the Project Manager's own reporting. That independence is the defining attribute the stem requires, distinguishing it from Project Support and Change Authority duties.

Why this answer

Project Assurance is independent of the Project Manager and provides assurance to the Project Board that the project is being managed correctly and remains viable.

Practice this question →

160

MCQeasy

Which role is accountable for the project's Business Case throughout the project?

A.Project Manager

B.Senior User

C.Project Assurance

D.Executive (SRO)

AnswerD

The Executive owns the Business Case and remains accountable for it from start to finish, ensuring the project stays justified and aligned with business objectives. This satisfies the stem's requirement for continuous accountability throughout the project, distinct from the Project Manager's day-to-day delivery duties or the Senior User's benefits focus.

Why this answer

The Executive (Senior Responsible Owner, SRO) is the role accountable for the Business Case throughout the project in PRINCE2. This accountability includes ensuring that the Business Case remains viable and aligned with corporate objectives, and that the project continues to justify its investment. The Executive owns the Business Case from initiation through to project closure, making the final decision on whether to proceed based on its continued viability.

Exam trap

The trap here is that candidates often confuse the Project Manager's responsibility for developing and maintaining the Business Case with the Executive's accountability for it, leading them to incorrectly select the Project Manager as the accountable role.

How to eliminate wrong answers

Option A is wrong because the Project Manager is responsible for developing, maintaining, and monitoring the Business Case on a day-to-day basis, but is not accountable for it; accountability rests with the Executive. Option B is wrong because the Senior User represents the users' interests and provides requirements, but does not hold accountability for the Business Case; that role is limited to specifying benefits and ensuring they are realized. Option C is wrong because Project Assurance provides independent oversight and checks that the Business Case is being managed correctly, but it does not own or hold accountability for the Business Case itself.

Practice this question →

161

Multi-Selectmedium

A PRINCE2 project is in the Starting Up a Project process. The Project Manager is assembling the project management team. Which TWO of the following statements about the Project Board are correct? (Choose two.)

Select 2 answers

A.The Project Board is accountable for the success or failure of the project.

B.The Project Board is optional in small projects.

C.The Project Board delegates all day-to-day management to the Project Manager.

D.The Project Board is responsible for approving the Project Initiation Documentation.

E.The Project Board must include the Project Manager as a member.

AnswersA, D

The Project Board is the ultimate decision-making authority and is accountable to the business for the project's success. It provides direction and resources, and ensures the project remains justified. This is a core PRINCE2 principle: the Project Board owns the project.

Why this answer

The Project Board is accountable for project success and approves the Project Initiation Documentation. It does not include the Project Manager, does not delegate all management, and is never optional. These responsibilities ensure proper governance and alignment with the Business Case.

Exam trap

The trap here is confusing the Project Manager's role with that of the Project Board, or assuming the board is optional in smaller projects.

Practice this question →

162

MCQmedium

A PRINCE2 project is being initiated to deliver a new data warehouse. The Executive has limited availability and wants to ensure that the project remains aligned with the business case. She asks the Project Manager to recommend who should be appointed to represent her interests on a day-to-day basis and provide independent assurance that the project is on track to deliver the benefits. Which role should the Project Manager recommend?

A.Project Assurance

B.Team Manager

C.Project Support

D.Senior User

AnswerA

Project Assurance is responsible for independently monitoring all aspects of the project's performance and products on behalf of the Project Board. The Executive can delegate her assurance responsibilities to a Project Assurance role. This person ensures the project remains aligned with the business case and provides the day-to-day oversight the Executive cannot give due to limited availability.

Why this answer

The Executive is accountable for the business case but may delegate day-to-day monitoring to Project Assurance. This role independently checks that the project remains aligned with the business case and that the project is on track to deliver the intended benefits. Project Assurance provides the continuous oversight the Executive cannot provide due to limited availability, ensuring the project stays on course.

Exam trap

The trap here is assuming that the Senior User provides assurance to the Executive, when in fact Project Assurance is the dedicated role for independent monitoring on behalf of the Project Board.

Practice this question →

163

MCQeasy

Who is responsible for ensuring that the project remains viable in terms of Business Case?

A.Project Board

B.Executive

C.Project Manager

D.Senior User

AnswerB

The Executive owns the Business Case and is accountable for confirming the project remains viable and deliverable throughout, judging continued justification against cost, risk, benefit and any changes, and deciding whether the project should proceed, change or stop.

Why this answer

The Executive is the single individual on the Project Board who has ultimate accountability for the project's business justification. They own the Business Case and must ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Project Manager manages the day-to-day work but does not own the Business Case; the Executive alone is responsible for its ongoing viability.

Exam trap

The trap here is that candidates often assume the Project Board as a whole is responsible for the Business Case, but PRINCE2 specifically assigns this accountability to the Executive alone, making the Board's role collective approval rather than individual ownership.

How to eliminate wrong answers

Option A is wrong because the Project Board as a whole is responsible for overall project direction and approval, but the Executive is the specific member who owns the Business Case and is accountable for its viability. Option C is wrong because the Project Manager manages the project on a day-to-day basis and provides information for the Business Case, but does not own it or have authority to decide on its viability. Option D is wrong because the Senior User represents the users' interests and specifies benefits, but does not own the Business Case or have accountability for its viability.

Practice this question →

164

MCQhard

Why does PRINCE2 separate the Project Manager role from the Project Assurance role?

A.To ensure that assurance activities are independent and objective

B.To allow the Project Manager to focus on user requirements

C.To reduce the workload of the Project Manager

D.Because PRINCE2 requires a separate person for every role

AnswerA

PRINCE2 assigns assurance to a role separate from the Project Manager so that reviews of the project's viability, progress and risks are performed independently. This separation prevents self-review bias, giving the Project Board objective evidence on which to base continued-investment decisions.

Why this answer

Separation ensures independence of assurance, preventing the Project Manager from making biased assessments of their own work.

Practice this question →

165

MCQmedium

During a project's initiation, the Project Board is concerned about the technical feasibility of a new product. They want to ensure that the supplier's proposed solution is achievable and that technical risks are managed. Which role is responsible for providing assurance that the supplier's solution is technically viable?

A.Project Manager

B.Project Assurance

C.Senior Supplier

D.Team Manager

AnswerC

The Senior Supplier is accountable for the technical integrity of the project and ensures that the supplier's solution is feasible and achievable. They provide assurance that the proposed products can be delivered to the required quality standards and within constraints, leveraging their technical expertise.

Why this answer

The Senior Supplier is the Project Board role accountable for the technical integrity of the project. They ensure that the supplier's proposed solution is feasible and that technical risks are understood and managed, providing confidence to the Project Board that the project can deliver the required products.

Exam trap

The trap here is assuming that Project Assurance or the Project Manager is responsible for technical feasibility, when it is actually the Senior Supplier who provides that assurance.

Practice this question →

166

Multi-Selectmedium

A Project Board is considering how to engage stakeholders in a project that affects multiple departments. According to PRINCE2, which TWO of the following are valid responsibilities of the Project Board in relation to stakeholder engagement? (Choose two.)

Select 2 answers

A.Writing the detailed stakeholder analysis and maintaining the stakeholder register.

B.Ensuring that the project's communication strategy is aligned with the organisation's communication policy.

C.Deciding the frequency of all project team meetings.

D.Personally conducting all stakeholder interviews and feedback sessions.

E.Approving the communication management approach as part of the project initiation documentation.

AnswersB, E

The Project Board is accountable for ensuring the project aligns with corporate policies, including communication. They should approve the communication management approach and verify that stakeholder engagement activities comply with organisational standards. This oversight helps maintain consistency and avoids conflicting messages.

Why this answer

The Project Board is accountable for ensuring the project aligns with organisational policies and for approving key management products, including the communication management approach. These responsibilities ensure stakeholder engagement is planned and governed effectively. Operational tasks such as conducting interviews, maintaining the stakeholder register, and scheduling team meetings are delegated to the Project Manager or other team members.

Exam trap

The trap here is confusing Project Board governance responsibilities with operational stakeholder engagement tasks that belong to the Project Manager.

Practice this question →

167

MCQmedium

A project is in the Managing a Stage Boundary process. Which action should the Project Manager take?

A.Authorize the next stage

B.Release a Work Package to the Team Manager

C.Prepare the Project Brief

D.Update the Project Plan with actuals and forecasts

AnswerD

Managing a Stage Boundary requires the Project Manager to update the Project Plan with actuals from the closing stage and forecasts for the next, then prepare the End Stage Report and Next Stage Plan for the board's authorisation decision.

Why this answer

During the Managing a Stage Boundary process, the Project Manager must update the Project Plan with actuals and forecasts to reflect the current stage's performance and provide a basis for planning the next stage. This ensures the Project Board has accurate information to authorize the next stage or take corrective action.

Exam trap

PeopleCert often tests the distinction between the Project Manager's role (preparing information and updating plans) and the Project Board's role (authorizing stages), leading candidates to mistakenly think the Project Manager authorizes the next stage.

How to eliminate wrong answers

Option A is wrong because authorizing the next stage is a decision made by the Project Board, not the Project Manager; the Project Manager prepares the information for that decision. Option B is wrong because releasing a Work Package to the Team Manager occurs during the Managing Product Delivery process, not during the Managing a Stage Boundary process. Option C is wrong because the Project Brief is created during the Starting Up a Project process and is not prepared or updated during the Managing a Stage Boundary process.

Practice this question →

168

MCQmedium

What is the purpose of the Directing a Project process?

A.To produce the Project Plan

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

C.To plan the next stage

D.To manage the day-to-day activities of a stage

AnswerB

Directing a Project sits above the managing stage boundary, giving the Project Board authority to approve initiation, stage plans, tolerances and closure. It satisfies the stem's need for overall control by reserving key go/no-go decisions to the board rather than the Project Manager.

Why this answer

The Directing a Project process is designed to enable the Project Board to make key decisions and exercise overall control over the project. It covers the board's responsibilities from project initiation through to closure, including authorizing the initiation, stage plans, and project closure, as well as providing ad hoc direction. This process does not involve detailed planning or day-to-day management, which are handled by other processes.

Exam trap

The trap here is that candidates often confuse the high-level control and decision-making role of the Project Board in Directing a Project with the detailed planning or execution tasks of other processes, such as Initiating a Project or Controlling a Stage.

How to eliminate wrong answers

Option A is wrong because producing the Project Plan is the purpose of the Initiating a Project process, not Directing a Project. Option C is wrong because planning the next stage is performed by the Managing a Stage Boundary process, which provides the Stage Plan for the board's approval. Option D is wrong because managing the day-to-day activities of a stage is the responsibility of the Controlling a Stage process, not Directing a Project.

Practice this question →

169

Multi-Selectmedium

Which TWO of the following are responsibilities of the Senior Responsible Owner (SRO/Executive) on the Project Board?

Select 2 answers

A.Day-to-day management of the project

B.Accountable for the Business Case

C.Chairing the Project Board

D.Preparing the Highlight Report

E.Defining the technical specifications of products

AnswersB, C

In PRINCE2, the Executive owns the Business Case, ensuring the project remains justified, viable and aligned with corporate objectives throughout. This accountability cannot be delegated to Project Manager or Senior User, making it a defining responsibility of the Senior Responsible Owner role.

Why this answer

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case, ensuring the project remains viable and aligned with organizational objectives. This includes approving the Business Case at initiation and any subsequent changes, as well as securing the necessary funding. The SRO also chairs the Project Board, providing overall leadership and direction, and is ultimately responsible for the project's success.

Exam trap

PeopleCert often tests the distinction between accountability (SRO/Executive) and responsibility (Project Manager or Senior User), leading candidates to confuse the SRO's strategic duties with the Project Manager's tactical tasks like reporting or management.

Practice this question →

170

MCQhard

A Project Board is concerned that the Project Manager is making decisions that should be reserved for the board. Which principle of PRINCE2 is being violated?

A.Manage by exception

B.Learn from experience

C.Tailor to suit the project environment

D.Defined roles and responsibilities

AnswerA

Manage by exception means that the Project Board sets tolerances for the Project Manager and delegates authority within those limits. If the Project Manager is making decisions that should be reserved for the board, then the agreed tolerances are not being respected, and the principle of manage by exception is being violated. The Project Board should only be involved when exceptions occur, but the Project Manager must stay within the defined boundaries.

Why this answer

The principle of manage by exception requires that the Project Board sets tolerances and delegates authority to the Project Manager to manage within those limits. When the Project Manager makes decisions that should be reserved for the board, they are acting outside the agreed tolerances, thus violating this principle. The other principles are not directly related to the delegation and control of authority in this scenario.

Exam trap

The trap here is thinking that any governance problem is about defined roles and responsibilities, but the specific breach is exceeding delegated tolerances, which is manage by exception.

Practice this question →

171

Multi-Selectmedium

Which TWO of the following describe the role of Project Assurance?

Select 2 answers

A.Assures the Project Board that the project is on track

B.Provides administrative support to the project team

C.Reports to the Project Board via Highlight Reports

D.Independent of the Project Manager

E.Manages the delivery of Work Packages

AnswersA, D

Project Assurance independently monitors all aspects of project performance on behalf of the Project Board, verifying that the project remains viable and on track against its business case. This satisfies the stem's requirement that the role provides the Board with confidence, distinct from Project Manager or Project Support duties.

Why this answer

Option A is correct because Project Assurance exists to give the Project Board confidence that the project remains viable and on track against its business case, plans, and tolerances, providing an independent view of performance and compliance. Option D is correct because Project Assurance must be independent of the Project Manager — it cannot be performed by the Project Manager or those reporting to them — so that its assessments are objective and free from delivery bias. Option B is wrong because administrative support is the responsibility of Project Support, not Project Assurance.

Option C is wrong because Highlight Reports are produced by the Project Manager and sent to the Project Board; Project Assurance reports through the Assurance role's own channels, not via Highlight Reports. Option E is wrong because managing the delivery of Work Packages is the Team Manager's responsibility, not Project Assurance.

Exam trap

PRINCE2F often tests whether candidates confuse Project Assurance with Project Support or with the Project Manager's reporting duties — the trap is picking 'administrative support' or 'Highlight Reports' because they sound like oversight activities.

Practice this question →

172

MCQmedium

What is the primary difference between Project Assurance and a quality review?

A.Project Assurance is a continuous activity; a quality review is a scheduled event

B.Project Assurance is performed by the Project Manager; quality reviews are performed by the team

C.There is no difference; they are the same

D.Project Assurance focuses on risks; quality reviews focus on issues

AnswerA

Project Assurance runs continuously throughout the project, monitoring management and performance against the business case, while a quality review is a scheduled, event-driven examination of a specific product. This continuous-versus-scheduled axis satisfies the stem's request for the primary difference between the two activities.

Why this answer

Project Assurance is a continuous, independent oversight activity that runs throughout the project lifecycle to ensure compliance with PRINCE2 principles and management by stages. A quality review, in contrast, is a scheduled, time-boxed event focused on assessing the quality of a specific product against its defined quality criteria. The key distinction is that Project Assurance is ongoing and embedded in governance, while a quality review is a discrete inspection meeting.

Exam trap

In PRINCE2, the trap is that candidates confuse the continuous nature of Project Assurance with the discrete, event-based nature of a quality review, often assuming both are periodic checks or that the Project Manager performs both roles.

How to eliminate wrong answers

Option B is wrong because Project Assurance is performed by someone independent of the Project Manager (e.g., a senior user, senior supplier, or corporate/programme representative), not by the Project Manager themselves; quality reviews are performed by a review team that includes the producer, reviewers, and a chair, not solely by the team. Option C is wrong because Project Assurance and quality reviews serve fundamentally different purposes: one is a governance function ensuring ongoing compliance, the other is a specific product quality check; they are not the same. Option D is wrong because Project Assurance covers all aspects of the project including risks, issues, business justification, and adherence to plans, not just risks; quality reviews focus on product quality, not issues (issues are managed via the issue register and change control).

Practice this question →

173

MCQhard

A Project Manager is working on a project where the Executive and Senior User disagree on the priority of a scope change. The Executive wants to approve the change to realise early benefits, while the Senior User is concerned about the impact on quality. What should the Project Manager do first?

A.Approve the change because the Executive has ultimate authority.

B.Arrange a Project Board meeting to discuss the change and its implications.

C.Escalate the disagreement to the Programme Board for resolution.

D.Reject the change to maintain the baseline and avoid conflict.

AnswerB

The Project Board is responsible for making decisions on changes that affect project scope, especially when there is disagreement. The Project Manager should provide an impact analysis and facilitate a meeting so the Executive and Senior User can make an informed decision together. This follows PRINCE2's principle of defined roles and responsibilities.

Why this answer

When Project Board members disagree on a change, the Project Manager should facilitate a Board meeting to discuss the change's impact and reach a collective decision. The Board is the correct forum for resolving such conflicts, ensuring that both benefits and quality concerns are weighed. Escalating prematurely, acting unilaterally, or rejecting the change without discussion would bypass proper governance.

Exam trap

The trap here is assuming that the Executive's authority allows them to override the Board, or that the Project Manager should decide unilaterally.

Practice this question →

174

MCQhard

The project board decides to use majority voting for all decisions. What is a potential issue with this decision-making process?

A.Using majority vote may undermine the principle of unified direction

B.Progress reports are too frequent, causing information overload

C.The Senior Supplier is represented by an individual rather than the organization

D.The roles are filled by three individuals, but there should be only two

AnswerA

PRINCE2 recommends consensus, not majority vote.

Why this answer

PRINCE2's principle of 'continued business justification' and the requirement for unified direction mandate that the project board make decisions by consensus, not by majority vote. The project board represents business, user, and supplier interests as a single cohesive unit; majority voting would risk dividing the board and undermining the principle of unified direction, as it could allow one interest to override others without full agreement.

Exam trap

PeopleCert often tests the misconception that majority voting is a valid decision-making method in PRINCE2, when in fact it violates the principle of unified direction and collective responsibility.

How to eliminate wrong answers

Option B is wrong because the question focuses on the decision-making process, not the frequency of progress reports; while too-frequent reports could cause overload, this is not directly related to the board's decision-making mechanism. Option C is wrong because the Senior Supplier role is correctly filled by an individual who represents the supplier organization's interests; PRINCE2 does not require the organization itself to be on the board. Option D is wrong because PRINCE2 specifies three distinct roles for the project board (Executive, Senior User, Senior Supplier), not two; having three individuals is correct and required.

Practice this question →

175

MCQmedium

Who is responsible for managing the project's day-to-day activities within the tolerances set by the Project Board?

A.Project Manager

B.Senior User

C.Project Board

D.Team Manager

AnswerA

The Project Manager runs the project on a day-to-day basis, authorised by the Project Board to work within agreed stage tolerances. This role owns delivery of the products and manages the team, distinguishing it from the Board, which sets direction and tolerance thresholds.

Why this answer

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, monitoring, and controlling project activities, escalating issues or deviations that exceed tolerances. The Project Board sets the overall direction and tolerances but does not manage daily tasks.

Exam trap

The trap here is that candidates often confuse the Project Manager's operational authority with the Team Manager's delivery focus, or mistakenly think the Project Board handles daily tasks because it 'manages' the project at a high level.

How to eliminate wrong answers

Option B (Senior User) is wrong because the Senior User represents the interests of those who will use the project's products and is responsible for specifying requirements and benefits, not for day-to-day management. Option C (Project Board) is wrong because the Project Board provides overall direction, approves plans, and sets tolerances, but does not manage daily activities. Option D (Team Manager) is wrong because the Team Manager is responsible for delivering specific products within a work package, but the Project Manager retains overall day-to-day management responsibility for the project.

Practice this question →

176

MCQeasy

Which role is ultimately accountable for the project's Business Case throughout the project?

A.Senior User

B.Senior Responsible Owner (Executive)

C.Senior Supplier

D.Project Manager

AnswerB

The Executive (Senior Responsible Owner) owns the Business Case and remains accountable for it throughout, ensuring the project stays aligned to benefits and justifies continued investment. This accountability cannot be delegated to the Project Manager, who only maintains and updates the Business Case on the Executive's behalf.

Why this answer

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case throughout its lifecycle. This role owns the Business Case and ensures the project remains viable, justified, and aligned with organizational objectives from initiation through closure.

Exam trap

The trap here is confusing the Project Manager's responsibility for maintaining the Business Case document with the Executive's ultimate accountability for its content and the project's continued viability.

How to eliminate wrong answers

Option A is wrong because the Senior User represents the interests of those who will use the project's outputs and is responsible for specifying requirements and benefits, but does not own or carry ultimate accountability for the Business Case. Option C is wrong because the Senior Supplier represents the interests of those providing the project's resources and expertise, and is accountable for the quality of deliverables, not for the Business Case. Option D is wrong because the Project Manager is responsible for managing the project on a day-to-day basis and for developing and maintaining the Business Case document, but accountability for the Business Case rests with the Executive.

Practice this question →

177

MCQeasy

Which document is used by the Project Manager to capture lessons learned during a stage?

A.Lessons Log

B.Checkpoint Report

C.End Stage Report

D.Lessons Report

AnswerA

The Lessons Log is the PRINCE2 document the Project Manager uses to record lessons as they arise during a stage, feeding the Lessons Report at stage end. The Business Case, Risk Register and Issue Register serve different purposes and do not capture lessons.

Why this answer

The Lessons Log is used to capture lessons throughout the project, including during a stage.

Practice this question →

178

Multi-Selecthard

Which THREE of the following are typical responsibilities of the Project Support role?

Select 3 answers

A.Planning the next stage

B.Administering quality reviews

C.Recording lessons learned

D.Maintaining the project filing system

E.Independent review of project status

AnswersB, C, D

Project Support often organizes quality reviews.

Why this answer

Administering quality reviews is a core administrative task of Project Support, ensuring that review meetings are scheduled, documented, and follow-up actions are tracked. This role provides the logistical and clerical backbone for quality management activities within a PRINCE2 project.

Exam trap

The trap here is that candidates confuse the administrative duties of Project Support with the managerial or assurance responsibilities of the Project Manager or Project Assurance, leading them to select options like planning or independent review.

Practice this question →

179

Multi-Selecthard

Which TWO statements correctly describe the Change Authority role?

Select 2 answers

A.It operates within limits set by the Project Board

B.It is responsible for all change decisions without limits

C.It is the same as Project Support

D.It is an optional role delegated by the Project Board

E.It is always performed by the Project Manager

AnswersA, D

The board sets the authority limits.

Why this answer

The Change Authority role in PRINCE2 operates within limits set by the Project Board. These limits define the scope of authority for approving change requests, ensuring that the Change Authority can make decisions without escalating every change to the Project Board, as long as the change falls within the agreed tolerances.

Exam trap

Candidates often mistakenly think the Change Authority has unlimited authority or is the same as the Project Manager, but PRINCE2 restricts it to the limits set by the Project Board.

Practice this question →

180

MCQmedium

According to PRINCE2, when should the Project Board meet?

A.Only at the start and end of the project

B.At each stage boundary and when an Exception Report is raised

C.Monthly

D.Weekly

AnswerB

PRINCE2 defines stage boundaries as the points where the Project Board authorises the next stage, and Exception Reports trigger escalation when tolerances are forecast to be breached. Both events demand board decisions, so meetings occur at each boundary and on exception.

Why this answer

In PRINCE2, the Project Board is the decision-making body that provides overall direction and control. The board meets at each stage boundary to review progress, approve the next stage plan, and assess continued business justification. It also meets when an Exception Report is raised, which signals that a stage is forecast to exceed its tolerances, requiring the board to decide on corrective action.

Exam trap

PeopleCert often tests the misconception that the Project Board meets on a fixed schedule (e.g., monthly or weekly), but PRINCE2 explicitly ties board meetings to stage boundaries and exception events, not arbitrary time intervals.

How to eliminate wrong answers

Option A is wrong because the Project Board does not meet only at the start and end of the project; it must meet at each stage boundary and when exceptions occur. Option C is wrong because PRINCE2 does not prescribe a fixed monthly meeting schedule; the frequency is driven by stage boundaries and exception events, not a calendar. Option D is wrong because weekly meetings are not a PRINCE2 requirement; the board meets only when management decisions are needed, such as at stage boundaries or for exceptions.

Practice this question →

181

MCQeasy

Who is responsible for the day-to-day management of the project within the tolerances set by the Project Board?

A.Project Manager

B.Team Manager

C.Senior Responsible Owner

D.Project Assurance

AnswerA

The Project Manager manages the project within tolerances on behalf of the Board.

Why this answer

In PRINCE2, the Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, delegating, monitoring, and controlling all project activities, and reporting progress to the Project Board. The Project Manager operates within the delegated authority of the tolerances (e.g., cost, time, scope) and must escalate any forecast deviation beyond those tolerances.

Exam trap

The trap here is confusing the Project Manager's operational authority with the Team Manager's delegated authority for work packages, or misattributing the Executive (the Senior Responsible Owner within PRINCE2) as the day-to-day manager.

How to eliminate wrong answers

Option B (Team Manager) is wrong because the Team Manager is responsible for delivering one or more work packages within tolerances set by the Project Manager, not for day-to-day management of the entire project. Option C (Senior Responsible Owner) is wrong because the Senior Responsible Owner is a role in PRINCE2 Agile or other frameworks, not in standard PRINCE2; in PRINCE2, the Executive is the business sponsor, not the day-to-day manager. Option D (Project Assurance) is wrong because Project Assurance is a monitoring function that provides independent oversight to the Project Board, not a management role responsible for day-to-day project activities.

Practice this question →

182

Multi-Selectmedium

A PRINCE2 project is facing challenges with stakeholder engagement. The 'Project Manager' is reviewing the 'Communication Management Approach' to improve how information is shared. Which TWO of the following are appropriate contents of the 'Communication Management Approach'? (Choose two.)

Select 2 answers

A.The list of all identified risks and their responses.

B.The project's financial budget and cost tolerance.

C.The detailed technical specifications of the project's products.

D.The format and frequency of progress reports to the Project Board.

E.The roles and responsibilities for managing stakeholder communications.

AnswersD, E

The 'Communication Management Approach' defines how the project will communicate with stakeholders, including the format and frequency of reports. Including progress report details ensures that the Project Board receives consistent and timely information. This is a key part of managing stakeholder expectations and aligns with the 'Tailor to suit the project environment' principle, as reporting needs vary by project.

Why this answer

The 'Communication Management Approach' describes the communication methods, roles, responsibilities, and reporting requirements for the project. It includes the format and frequency of reports to the Project Board, as well as the roles and responsibilities for managing communications. Technical specifications, budget details, and risk lists are documented in other management products, so they are not part of this approach.

Exam trap

The trap here is assuming that any project information can be included in the Communication Management Approach, when it should only contain communication-related details.

Practice this question →

183

MCQmedium

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

A.Stage boundary meeting

B.Monthly progress meeting

C.Daily stand-up meeting

D.Exception-driven meeting

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

184

MCQmedium

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

A.Directing a Project

B.Managing a Stage Boundary

C.Initiating a Project

D.Controlling a Stage

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

185

MCQmedium

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

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

B.Escalate the issue to the program management for resolution

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

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

AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

186

MCQmedium

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

A.Team Manager

B.Senior User

C.Project Manager

D.Project Board

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

187

MCQmedium

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

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

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

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

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

AnswerC

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

Why this answer

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

Exam trap

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

Practice this question →

188

MCQmedium

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

A.Team Manager

B.Project Support

C.Project Manager

D.Senior User

AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

189

Multi-Selectmedium

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

Select 2 answers

A.Senior User

B.Project Manager

C.Team Manager

D.Project Support

E.Change Authority

AnswersD, E

Optional administrative support role.

Why this answer

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

Exam trap

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

Practice this question →

190

MCQmedium

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

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

B.Inform the Senior Supplier and request additional resources

C.Immediately raise an Exception Report to the Project Board

D.Update the Stage Plan with the new forecast

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

191

MCQhard

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

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

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

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

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

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

192

MCQmedium

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

A.Project Assurance

B.Senior Supplier

C.Project Support

D.Team Manager

AnswerA

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

Why this answer

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

Exam trap

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

Practice this question →

193

MCQmedium

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

A.Business Case

B.Project Brief

C.Stage Plan

D.Project Initiation Documentation (PID)

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

194

MCQmedium

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

A.At stage boundaries and when an exception is raised

B.Weekly

C.At the start and end of the project only

D.Monthly

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

195

MCQhard

In PRINCE2, what is the difference between a Senior Responsible Owner (SRO) and a Project Sponsor?

A.The SRO is accountable for the Business Case; the sponsor is not defined in PRINCE2

B.The sponsor is a member of the Project Board; the SRO is not

C.The SRO is appointed after the project; the sponsor is appointed before

D.They are different names for the same role

AnswerA

Correct. SRO is a PRINCE2 role; sponsor is not.

Why this answer

In PRINCE2, the Senior Responsible Owner (SRO) is the single person accountable for the Business Case and ensuring the project delivers the expected benefits. The term 'Project Sponsor' is not a defined role in PRINCE2; it is a common industry term that may be used interchangeably with the SRO or other roles, but PRINCE2's official role structure uses the SRO as the key business representative on the Project Board.

Exam trap

The trap here is that candidates often assume 'Project Sponsor' is a formal PRINCE2 role, but PRINCE2 strictly defines the SRO as the business owner, and the exam tests whether you know that 'sponsor' is not an official PRINCE2 term.

How to eliminate wrong answers

Option B is wrong because the Senior Responsible Owner (SRO) is indeed a member of the Project Board, not excluded from it; the SRO chairs the Project Board and is the key decision-maker, so the statement that the SRO is not a member is factually incorrect. Option C is wrong because the SRO is appointed at the very start of the project (during Starting up a Project process), not after the project; the sponsor is not a defined PRINCE2 role, so the timing comparison is meaningless. Option D is wrong because while the SRO and a 'Project Sponsor' are often used interchangeably in practice, PRINCE2 does not define a 'Project Sponsor' role, so they are not officially the same; the SRO is the precise PRINCE2 term for the business owner accountable for the Business Case.

Practice this question →

196

MCQmedium

The Project Manager has issued a Work Package to a Team Manager. The Team Manager realizes that the work cannot be completed within the agreed tolerances. What should the Team Manager do first?

A.Complete the work and explain the overrun in the Checkpoint Report

B.Inform the Project Board directly

C.Raise an Exception Report to the Project Manager

D.Stop all work on the Work Package

AnswerC

Under PRINCE2, the Team Manager cannot exceed assigned Work Package tolerances. Forecast breach must be escalated immediately via an Exception Report to the Project Manager, who then decides whether to escalate to the Project Board, since only they can authorise tolerance changes.

Why this answer

When a Team Manager foresees that a Work Package will breach its agreed tolerances, PRINCE2 requires them to raise an Exception Report to the Project Manager, who then decides whether to escalate to the Project Board. The Team Manager does not have authority to change tolerances or to bypass the Project Manager. This preserves the management-by-exception principle.

Exam trap

PRINCE2F often tests the escalation path, tempting candidates to escalate directly to the Project Board or to delay reporting until the overrun actually happens.

How to eliminate wrong answers

Option A is wrong because completing the work and explaining the overrun afterward violates the principle of managing by exception — tolerances exist precisely to trigger early escalation. Option B is wrong because the Team Manager reports to the Project Manager, not directly to the Project Board; bypassing the Project Manager breaks the management hierarchy. Option D is wrong because stopping all work is not the prescribed first action — the Team Manager should raise the exception and await direction, though work may continue within tolerance until a decision is made.

Practice this question →

197

Multi-Selecteasy

Which TWO of the following are responsibilities of the Project Manager in PRINCE2?

Select 2 answers

A.Producing the Project Plan

B.Ensuring the project meets user needs

C.Providing business assurance

D.Authorizing stage boundaries

E.Day-to-day management of the project

AnswersA, E

Correct: The Project Manager produces the Project Plan.

Why this answer

The Project Manager is responsible for producing the Project Plan, which includes the detailed schedule, resource allocation, and cost estimates. This is a core PRINCE2 responsibility, as the Project Manager owns the planning process and ensures the plan aligns with the project's business case and stage tolerances.

Exam trap

The trap here is confusing the Project Manager's operational responsibilities with the strategic or assurance roles of the Project Board or Senior User, leading candidates to incorrectly assign user needs or authorization duties to the Project Manager.

Practice this question →

198

MCQmedium

Which PRINCE2 role is responsible for preparing the Project Plan?

A.Team Manager

B.Project Manager

C.Senior Responsible Owner (Executive)

D.Project Support

AnswerB

The Project Manager prepares the Project Plan, satisfying PRINCE2's division of responsibilities between the Project Board and the Project Manager. The Board owns the Project Initiation Documentation and approves plans, but drafting the Project Plan sits squarely with the Project Manager, who also manages its delivery throughout the project lifecycle.

Why this answer

In PRINCE2, the Project Manager is responsible for preparing the Project Plan, as defined in the 'Plan' theme. This includes estimating, scheduling, and documenting the plan to achieve the project's objectives within agreed tolerances. The Project Manager owns the planning process and produces the plan for approval by the Project Board.

Exam trap

The trap here is confusing the Project Manager's role in preparing the Project Plan with the Executive's accountability for the business case or the Team Manager's responsibility for lower-level Team Plans, leading candidates to select the wrong role based on perceived authority rather than defined PRINCE2 responsibilities.

How to eliminate wrong answers

Option A is wrong because the Team Manager is responsible for producing Team Plans, not the Project Plan; they focus on detailed work packages within their team. Option C is wrong because the Senior Responsible Owner (Executive) is accountable for the project's business case and overall success, not for preparing the Project Plan. Option D is wrong because Project Support provides administrative and advisory services (e.g., planning tools, configuration management) but does not prepare the Project Plan itself.

Practice this question →

199

Multi-Selectmedium

A Project Board is reviewing the project's progress and needs to ensure that the project remains viable. Which TWO of the following are responsibilities of the Project Board? (Choose two.)

Select 2 answers

A.Approve changes to the project's tolerances

B.Produce the End Stage Report

C.Authorize the start of the next stage

D.Manage the day-to-day execution of the project

E.Approve the Project Initiation Documentation

AnswersC, E

The Project Board is responsible for authorizing the start of each stage after reviewing the End Stage Report and the next Stage Plan. This ensures that the project continues to be aligned with the business case and that the Project Board maintains control.

Why this answer

The Project Board is accountable for the overall success of the project and makes key decisions such as approving the Project Initiation Documentation and authorizing the start of each stage. These responsibilities ensure that the project remains viable and aligned with the business case.

Exam trap

The trap here is confusing the Project Board's strategic responsibilities with the Project Manager's operational tasks, such as managing day-to-day work and producing reports.

Practice this question →

200

MCQeasy

Which role is ultimately accountable for the project's Business Case and its continued viability?

A.Senior Responsible Owner (Executive)

B.Project Manager

C.Senior User

D.Team Manager

AnswerA

The Executive owns the Business Case and remains accountable for its continued viability throughout the project, matching PRINCE2's principle that justification must be maintained. This role sits on the Project Board, securing funding and confirming benefits remain achievable, satisfying the stem's accountability requirement rather than delegating it to Project Manager or Business Analyst functions.

Why this answer

The Senior Responsible Owner (Executive) is ultimately accountable for the project's Business Case and its continued viability because PRINCE2 defines this role as the single point of accountability for the project's justification. The Executive owns the Business Case throughout the project lifecycle, ensuring it remains aligned with corporate strategy and approving any changes that affect its viability. This accountability cannot be delegated to the Project Manager, who is responsible for day-to-day management but not for the business justification.

Exam trap

PeopleCert often tests the distinction between 'responsible' and 'accountable' in PRINCE2, leading candidates to incorrectly choose the Project Manager because they confuse the task of creating the Business Case with the accountability for its ongoing viability.

How to eliminate wrong answers

Option B (Project Manager) is wrong because the Project Manager is responsible for managing the project on a day-to-day basis and producing the Business Case, but they are not accountable for its continued viability; accountability rests with the Executive. Option C (Senior User) is wrong because the Senior User represents the interests of those who will use the project's outputs and specifies the requirements, but they do not own the Business Case or its financial justification. Option D (Team Manager) is wrong because the Team Manager is responsible for delivering the work packages assigned to their team and has no role in the Business Case; they report to the Project Manager on technical delivery.

Practice this question →

201

MCQmedium

During the Controlling a Stage process, the Project Manager receives a Checkpoint Report from a Team Manager indicating a delay in delivering a Work Package. What should the Project Manager do first?

A.Instruct the Team Manager to recover the delay within the Work Package tolerances

B.Close the Work Package and re-plan the stage

C.Raise an Exception Report to the Project Board immediately

D.Assess the impact on the Stage Plan and decide on corrective action within stage tolerances

AnswerD

The Project Manager must first assess how the Work Package delay affects the Stage Plan, then decide whether corrective action stays within stage tolerances. Escalating or amending the Business Case comes only if tolerances would be exceeded.

Why this answer

The Project Manager must first assess the impact of the delay on the Stage Plan and decide on corrective action within the agreed stage tolerances. This aligns with the PRINCE2 principle of management by exception, where the Project Manager handles deviations within tolerances before escalating. Only if the delay exceeds stage tolerances should an Exception Report be raised to the Project Board.

Exam trap

The trap here is that candidates often jump to escalation (Option C) without recognizing that the Project Manager must first assess the impact and attempt corrective action within tolerances, as per the management by exception principle.

How to eliminate wrong answers

Option A is wrong because instructing the Team Manager to recover the delay without first assessing the impact on the Stage Plan bypasses the Project Manager's responsibility to evaluate whether the delay can be managed within stage tolerances. Option B is wrong because closing the Work Package and re-planning the stage is a drastic action that should only be considered after assessing the impact and determining that the stage cannot continue within tolerances. Option C is wrong because raising an Exception Report immediately is premature; the Project Manager must first determine if the delay exceeds stage tolerances before escalating to the Project Board.

Practice this question →

202

MCQeasy

What is the role of Project Assurance?

A.To provide administrative support to the Project Manager

B.To chair the Project Board

C.To independently assure the Project Board that the project is on track

D.To deliver Work Packages

AnswerC

Project Assurance provides independent monitoring and verification to the Project Board, confirming that the project remains viable and on track against its business case, plans and tolerances. This independence is the defining characteristic distinguishing it from Project Manager progress reporting.

Why this answer

Project Assurance is a PRINCE2 role responsible for providing an independent, objective check to the Project Board that the project remains viable, compliant, and on track. It is not a day-to-day management function but a governance safeguard, ensuring that the project adheres to its business case, quality standards, and tolerances without being influenced by the Project Manager or delivery team.

Exam trap

PeopleCert often tests the distinction between Project Assurance (independent oversight for the Board) and Project Support (administrative help for the Project Manager), leading candidates to confuse the two roles.

How to eliminate wrong answers

Option A is wrong because administrative support to the Project Manager is the role of Project Support, not Project Assurance. Option B is wrong because the Project Board is chaired by the Executive, not by Project Assurance. Option D is wrong because delivering Work Packages is the responsibility of the Team Manager or team members, not Project Assurance.

Practice this question →

203

MCQmedium

A project has a strong matrix structure. The project manager finds that team members are more loyal to their functional managers than to the project. What is the best PRINCE2 practice to improve team commitment?

A.Conduct regular performance reviews tied to project deliverables

B.Implement daily stand-up meetings to reinforce project goals

C.Change the organizational structure to a functional organization

D.Clearly define project roles and responsibilities in the Project Initiation Documentation

AnswerD

Documenting roles and responsibilities in the Project Initiation Documentation clarifies each team member's project accountability, countering the pull of functional loyalty in a strong matrix. This applies the PRINCE2 organisation practice, giving people a defined project role to commit to.

Why this answer

In a strong matrix structure, team members report to both functional and project managers, which can create loyalty conflicts. PRINCE2's 'defined roles and responsibilities' practice, documented in the Project Initiation Documentation (PID), clarifies each team member's authority, accountability, and reporting lines. This formal definition reduces ambiguity and reinforces commitment to the project by making project responsibilities explicit.

Exam trap

The trap here is that candidates confuse operational management techniques (like stand-ups or performance reviews) with PRINCE2's structural governance practice of defining roles and responsibilities to resolve organizational conflicts.

How to eliminate wrong answers

Option A is wrong because performance reviews are typically the responsibility of functional managers in a matrix structure, not the project manager, and tying them to project deliverables does not address the underlying loyalty conflict. Option B is wrong because daily stand-up meetings are an agile practice, not a PRINCE2 practice, and they focus on task coordination rather than structural role definition. Option C is wrong because changing to a functional organization would eliminate the matrix structure entirely, which is a drastic organizational change outside the project manager's authority and not a PRINCE2 practice for improving team commitment.

Practice this question →

204

MCQhard

A Project Board has approved the project initiation. The Project Manager is now assembling the team. The Senior User insists that a particular subject matter expert (SME) from their department be included, but the SME is already fully allocated to another project. The Project Manager needs to resolve this resource conflict. Which action should the Project Manager take FIRST?

A.Discuss the requirement with the Senior User and the other project manager to find a mutually agreeable solution.

B.Accept the Senior User's demand and adjust the project plan to accommodate the SME's availability.

C.Replace the SME with another resource without consulting the Senior User.

D.Escalate the issue to the Project Board as an exception.

AnswerA

The Project Manager should first engage with the stakeholders involved to understand the need and explore options, such as part-time allocation, knowledge transfer, or an alternative SME. This collaborative approach respects the Senior User's concerns while considering the broader organizational context. It is the first step before escalation or unilateral action.

Why this answer

The Project Manager should first engage with the Senior User and the other project manager to explore options. This respects the Senior User's role and the constraints of the organization. Escalation or unilateral action is premature without attempting resolution at the project level.

Collaboration is key to managing resource conflicts in PRINCE2.

Exam trap

The trap here is assuming that any resource conflict must be escalated immediately, or that the Project Manager can simply override stakeholder requests without discussion.

Practice this question →

205

MCQeasy

When should the Project Board meet?

A.At stage boundaries and when an exception occurs

B.Only at the end of the project

C.Daily

D.Weekly

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

206

MCQhard

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

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

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

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

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

AnswerC

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

Why this answer

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

Exam trap

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

Practice this question →

207

MCQeasy

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

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

B.To authorize the project to proceed

C.To produce the Project Initiation Documentation

D.To plan the entire project in detail

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

208

MCQhard

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

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

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

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

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

AnswerC

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

Why this answer

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

Practice this question →

209

MCQhard

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

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

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

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

D.They are the same role

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

210

MCQmedium

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

A.Senior Supplier

B.Project Support

C.Team Manager

D.Project Manager

AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

211

MCQhard

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

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

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

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

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

AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

212

MCQeasy

In PRINCE2, what is the purpose of Project Support?

A.To provide administrative support to the project.

B.To approve stage plans.

C.To independently assure the Project Board.

D.To manage the project's budget.

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

213

MCQmedium

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

A.To specify the desired outcomes and benefits

B.To chair the Project Board

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

D.To provide resources and expertise

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

214

MCQmedium

Which role is responsible for producing the Highlight Report?

A.Project Support

B.Project Manager

C.Senior Responsible Owner

D.Team Manager

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

215

MCQhard

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

A.Raise an Exception Report to the Project Board.

B.Update the Project Plan to reflect the delay.

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

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

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

216

Multi-Selectmedium

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

Select 2 answers

A.Project Board

B.Project Support

C.Senior Supplier

D.Project Manager

E.Change Authority

AnswersB, E

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

Why this answer

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

Exam trap

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

Practice this question →

217

MCQmedium

Who chairs the Project Board meetings in PRINCE2?

A.Senior Supplier

B.Project Manager

C.Senior User

D.Senior Responsible Owner (Executive)

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

218

MCQeasy

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

A.Project Manager

B.Project Assurance

C.Team Manager

D.Senior Responsible Owner (SRO)

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

219

Multi-Selectmedium

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

Select 3 answers

A.Project Board

B.Team Manager

C.Project Manager

D.User Group

E.Steering Committee

AnswersA, B, C

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

Why this answer

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

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

Exam trap

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

Practice this question →

220

MCQhard

Why does PRINCE2 separate the role of Project Manager from Project Assurance?

A.To allow the Project Manager to focus on day-to-day management while assurance is independent

B.To reduce the workload of the Project Manager

C.To avoid the need for quality reviews

D.To ensure that the Project Board has direct control over the team

AnswerA

Separating these roles preserves objectivity: Project Assurance reports to the Project Board, not the Project Manager, so it can scrutinise the project's viability, costs and risks independently. This satisfies PRINCE2's accountability principle, letting the Project Manager concentrate on day-to-day delivery without self-reviewing their own performance.

Why this answer

PRINCE2 separates the role of Project Manager from Project Assurance to ensure that assurance activities are performed independently of day-to-day management. This allows the Project Manager to focus on delivering the project's products and managing the team, while Project Assurance provides an objective check that the project remains viable, compliant with standards, and aligned with business expectations. The independence prevents conflicts of interest and ensures that assurance is not compromised by the pressures of daily project work.

Exam trap

The trap here is that candidates often confuse the separation of roles with workload reduction, but PRINCE2 explicitly mandates independence of assurance to maintain objectivity, not to lighten the Project Manager's load.

How to eliminate wrong answers

Option B is wrong because reducing the Project Manager's workload is a potential side effect, not the primary reason for the separation; the core principle is independence of assurance, not workload distribution. Option C is wrong because quality reviews are a separate PRINCE2 technique that still occur regardless of the separation; the separation does not eliminate the need for quality reviews. Option D is wrong because the Project Board does not gain direct control over the team through this separation; the Project Board retains strategic control via management stages and tolerances, while the Project Manager handles day-to-day team management.

Practice this question →

221

MCQhard

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

A.Project Assurance is a role providing ongoing independent oversight; a quality review is a technique to evaluate product quality

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

C.There is no difference; quality review is another name for Project Assurance

D.Project Assurance focuses on benefits; quality review focuses on products

AnswerA

Project Assurance is an ongoing role delivering independent oversight of the project's viability and compliance to the board, whereas a quality review is a structured technique applied at a point in time to evaluate whether a specific product meets its quality criteria.

Why this answer

Project Assurance is a continuous, independent oversight role for the Project Board, while a quality review is a specific technique to assess product quality at a point in time.

Practice this question →

222

MCQhard

During a PRINCE2 project, the Project Board has delegated change authority to a Change Authority for changes within a certain cost threshold. A Request for Change is raised that exceeds the threshold. The Project Manager is unsure who should make the decision. According to PRINCE2, who should decide on this change?

A.The Change Authority, because they have been delegated change control decisions

B.The Project Board, because the change exceeds the delegated authority

C.The Project Manager, because they are responsible for day-to-day management

D.The Senior User, because they represent the user community affected by the change

AnswerB

The Project Board is ultimately accountable for the project and retains authority for decisions beyond the delegated threshold. When a change exceeds the Change Authority's limit, it must be escalated to the Project Board for a decision. This aligns with the PRINCE2 principle of management by exception, ensuring that higher-level authority handles significant deviations.

Why this answer

When a change exceeds the delegated authority of the Change Authority, it must be escalated to the Project Board. The board is accountable for the project and makes decisions on significant changes that affect the project's business case, scope, or tolerances. This ensures proper governance and alignment with the principle of management by exception.

Exam trap

The trap here is assuming that the Change Authority can handle any change once delegated, but their authority is strictly limited by the threshold set by the Project Board.

Practice this question →

223

Multi-Selecthard

A Project Manager is leading a project that involves multiple teams from different organizations. To ensure effective team working, the Project Manager is considering various leadership and management techniques. Which TWO of the following are appropriate actions for the Project Manager to take to build and maintain effective teams? (Choose two.)

Select 2 answers

A.Avoid communicating with team members to prevent distractions.

B.Establish a common vision and objectives for the team.

C.Use a directive leadership style at all times.

D.Ensure that all team members report directly to the Project Manager.

E.Delegate authority to the Team Manager for work package delivery.

AnswersB, E

Establishing a common vision and objectives helps align team members from different organizations towards a shared goal. This is crucial for building effective teams, as it provides direction and fosters collaboration, reducing the risk of misunderstandings and conflicts.

Why this answer

Establishing a common vision and delegating authority to the Team Manager are both aligned with PRINCE2 principles for effective team working. They promote alignment, empowerment, and clear responsibilities, which are essential in multi-team projects.

Exam trap

The trap here is assuming that the Project Manager must have direct control over all team members or use a single leadership style, which ignores PRINCE2's emphasis on delegation and situational leadership.

Practice this question →

224

MCQmedium

The Project Board has not met for several months. According to PRINCE2, when should the Project Board meet?

A.Weekly

B.Monthly

C.At stage boundaries and when an Exception Report is raised

D.Only at the end of the project

AnswerC

PRINCE2 mandates Project Board meetings at each stage boundary to authorise the next stage, and additionally whenever an Exception Report is escalated, since tolerances have been breached. This satisfies the stem's requirement by defining the two trigger points, rather than relying on a fixed calendar schedule.

Why this answer

PRINCE2 recommends that Project Boards meet at the end of each management stage (Stage Boundary) and when an Exception Report is raised. They should not meet on a fixed monthly basis; meetings are exception-driven.

Practice this question →

225

MCQmedium

A project is being initiated, and the Project Board is being assembled. The organization's senior leadership wants to ensure that the business interests are represented and that the project remains viable. Which role is specifically responsible for ensuring that the project delivers the business benefits defined in the Business Case?

A.Executive

B.Senior User

C.Project Manager

D.Senior Supplier

AnswerA

The Executive is the single point of accountability for the project and is responsible for ensuring that the project delivers the business benefits outlined in the Business Case. This role owns the Business Case and must ensure that the project remains aligned with business objectives throughout its lifecycle.

Why this answer

The Executive is the key decision-maker and is ultimately accountable for the project's success, including the delivery of business benefits. The Senior User and Senior Supplier provide input and ensure user and supplier perspectives, but the Executive owns the Business Case and ensures alignment with organizational strategy.

Exam trap

The trap here is confusing the Senior User's focus on user benefits with the Executive's accountability for overall business benefits and the Business Case.

Practice this question →