1599 questions total · 22pages · All types, answers revealed
Which PRINCE2 principle emphasizes that a project must remain viable throughout its lifecycle?
Ensuring the Business Case remains valid is key to viability.
Why this answer
The 'Continued business justification' principle requires that the Business Case is reviewed and updated regularly to ensure the project remains desirable, viable, and achievable.
Who is responsible for maintaining the Business Case throughout the project?
The Project Manager is responsible for maintaining the Business Case and updating it as needed.
Why this answer
The Project Manager is responsible for maintaining the Business Case throughout the project because they manage day-to-day activities, monitor progress against the Business Case, and update it when changes occur. PRINCE2 assigns this responsibility to the Project Manager to ensure the Business Case remains viable and reflects current project realities. The Project Manager prepares and updates the Business Case for approval by the Project Board, but the ongoing maintenance is their duty.
Exam trap
The trap here is that candidates confuse the Executive's ownership and approval authority with the Project Manager's responsibility for maintaining the document, leading them to select the Executive (SRO) instead of the Project Manager.
How to eliminate wrong answers
Option B is wrong because the Senior User represents the users' interests and specifies benefits, but they do not maintain the Business Case; they provide input on benefits realization. Option C is wrong because the Executive (SRO) is the ultimate owner of the Business Case and approves it, but the day-to-day maintenance is delegated to the Project Manager. Option D is wrong because the Project Board makes key decisions and approves the Business Case, but they are not responsible for its ongoing maintenance; that is a Project Manager role.
The Project Board consists of three roles. Which of the following is NOT a mandatory role on the Project Board?
The Project Manager attends Project Board meetings but is not a member.
Why this answer
The mandatory roles are Senior User, Senior Supplier, and Senior Responsible Owner. The Project Manager is not a member of the Project Board.
Which TWO of the following are outputs of the Initiating a Project process?
Correct: This is produced as part of the PID during IP.
Why this answer
The PID and the Benefits Management Approach are key outputs of IP. The Daily Log is created in SU. The End Project Report is from CP.
A project is forecast to exceed its cost tolerance. What should the Project Manager do?
This is the correct response per management by exception.
Why this answer
When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.
In PRINCE2, what is the main reason for separating the Project Manager role from the Project Assurance role?
Project Assurance provides an independent view to the Project Board, not influenced by the Project Manager.
Why this answer
Separation ensures independent and objective assurance that the project is running correctly, free from the biases or conflicts of day-to-day management.
In product-based planning, what does the Product Flow Diagram show?
This is the purpose of the Product Flow Diagram.
Why this answer
The Product Flow Diagram in PRINCE2 product-based planning shows the sequence in which products are developed and the dependencies between them. It is a key technique for identifying the order of creation and the relationships among products, which is essential for planning the project's activities and stages.
Exam trap
The trap here is that candidates often confuse the Product Flow Diagram with the Product Breakdown Structure (PBS), mistakenly thinking the flow diagram shows a hierarchy rather than sequence and dependencies.
How to eliminate wrong answers
Option A is wrong because the hierarchical breakdown of all products is shown in the Product Breakdown Structure (PBS), not the Product Flow Diagram. Option C is wrong because the activities required to create each product are detailed in the activity network or project plan, not in the Product Flow Diagram. Option D is wrong because the quality criteria for each product are defined in the Product Description, not in the Product Flow Diagram.
Which document is the key output of the Initiating a Project process?
Correct. The PID is created during Initiating a Project.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process.
A project is in the delivery stage. The team manager has accepted a work package. Which process governs the team manager's work in delivering the products?
Correct. MP covers the team manager's activities to deliver products as per the work package.
Why this answer
Managing Product Delivery (D) is the correct process because it governs the acceptance, execution, and delivery of work packages by the team manager. In the delivery stage, the team manager receives a work package from the project manager (via Controlling a Stage) and is responsible for producing the products, reporting progress, and delivering completed work back to the project manager. This process directly controls the team manager's activities in building the products.
Exam trap
In PRINCE2, the trap is confusing the project manager's process (Controlling a Stage) with the team manager's process (Managing Product Delivery). Candidates often pick Controlling a Stage because it involves work packages, but it governs the project manager's oversight, not the team manager's execution.
How to eliminate wrong answers
Option A is wrong because Initiating a Project is the process that establishes the project's foundation, creates the Project Initiation Documentation, and occurs before any delivery stages begin; it does not govern team manager work during delivery. Option B is wrong because Directing a Project is the process for the Project Board to make key decisions, authorize stages, and provide overall direction, not for managing day-to-day product delivery by the team manager. Option C is wrong because Controlling a Stage is the process used by the project manager to assign work packages, monitor stage progress, and handle issues, but it is the project manager's process, not the team manager's process for delivering products.
According to PRINCE2, who is responsible for authorizing the work packages to be executed by the team?
The Project Manager authorizes work packages.
Why this answer
In PRINCE2, the Project Manager is responsible for authorizing work packages to be executed by the team. This is because the Project Manager manages the day-to-day activities and has the authority to assign work to team members or Team Managers, ensuring that the work packages align with the project plan and stage tolerances. The Project Board provides overall direction and approves stage plans, but the authorization of individual work packages is delegated to the Project Manager.
Exam trap
The trap here is that candidates often confuse the Project Board's high-level authority with the Project Manager's delegated authority for operational work package authorization, leading them to incorrectly select the Project Board.
How to eliminate wrong answers
Option A is wrong because the Project Board is responsible for overall project direction, approving stage plans, and making key decisions, but they do not authorize individual work packages—that is delegated to the Project Manager. Option B is wrong because the Senior Responsible Owner (SRO) is a role in PRINCE2 for the business case and project assurance, not for authorizing work packages; the SRO is part of the Project Board but does not handle operational work package authorization. Option D is wrong because the Team Manager is responsible for coordinating and managing the team's work on assigned work packages, but they do not authorize them—they receive authorized work packages from the Project Manager.
Who is responsible for producing a Checkpoint Report?
Team Managers produce Checkpoint Reports.
Why this answer
Team Managers produce Checkpoint Reports to inform the Project Manager of progress against work packages.
Which TWO of the following statements about the Project Board are correct?
Correct: Project Board meetings are held at stage boundaries or when exceptions occur.
Why this answer
The Project Board in PRINCE2 is designed to be an exception-driven body; it convenes only when decisions are required, such as approving stage plans or exception plans, rather than on a fixed schedule. This aligns with the PRINCE2 principle of management by exception, where the board delegates day-to-day management to the Project Manager and escalates only when tolerances are forecast to be exceeded.
Exam trap
The trap here is that candidates often confuse the Project Board's meeting frequency with a typical steering committee that meets regularly, but PRINCE2 specifically mandates an exception-driven approach, not a fixed schedule.
What is the difference between a Request for Change (RFC) and an Off-specification (Off-spec)?
An RFC requests a change to a baselined product; an Off-spec indicates a product does not meet its specification.
Why this answer
An RFC is a request to change a product that has been agreed upon and baselined, whereas an Off-spec is something that should have been provided but is not, or is not meeting specifications. An RFC proposes a change; an Off-spec identifies a deviation.
What is the purpose of the Managing a Stage Boundary process?
This is the correct purpose of SB.
Why this answer
The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and decide whether the project should continue. It ensures that the project remains viable and aligned with business justification before committing resources to the next stage.
Exam trap
The trap here is confusing the purpose of Managing a Stage Boundary with Controlling a Stage (Option D), as both involve stage-level activities, but the boundary process is specifically about the handover and approval between stages, not daily management.
How to eliminate wrong answers
Option A is wrong because closing the project after final delivery is the purpose of the Closing a Project process, not Managing a Stage Boundary. Option C is wrong because initiating the project and obtaining authorization is the purpose of the Initiating a Project process, which occurs before any stage boundaries. Option D is wrong because controlling day-to-day activities of a stage is the purpose of the Controlling a Stage process, which operates within a stage, not at its boundary.
Which THREE of the following are activities performed during the Controlling a Stage process?
The PM reviews progress against the Stage Plan.
Why this answer
CS includes authorizing Work Packages, reviewing progress, and escalating issues. Planning the next stage is done in Managing a Stage Boundary. Authorizing the project is done in Directing a Project.
Which role is responsible for providing assurance that the project is being managed correctly from a business perspective?
Project Assurance performs independent oversight on behalf of the Project Board.
Why this answer
Project Assurance is independent of the Project Manager and reports to the Project Board. Business assurance is one aspect of Project Assurance.
A project is in an early stage and the Project Manager discovers a new risk that could cause a delay. The risk is within the stage tolerance. What should the Project Manager do?
The PM can handle risks within tolerance without escalation.
Why this answer
Since the risk is within stage tolerance, the Project Manager should manage it within the stage (e.g., by updating the risk register and taking corrective action) without escalating to the Project Board.
Who is responsible for maintaining the Business Case throughout the project?
The Project Manager maintains the Business Case on behalf of the Executive.
Why this answer
The Project Manager is responsible for maintaining the Business Case throughout the project because PRINCE2 requires the Business Case to be a living document that is reviewed and updated at each stage boundary. The Project Manager ensures that the Business Case remains viable by monitoring costs, benefits, and risks against the approved baseline, and escalates any deviations to the Project Board. This ongoing maintenance is a key project management responsibility, distinct from the Executive's ownership of the Business Case's justification.
Exam trap
The trap here is that candidates confuse the Executive's accountability for the Business Case with the Project Manager's responsibility for its maintenance, leading them to incorrectly select the Executive as the answer.
How to eliminate wrong answers
Option A is wrong because the Executive owns the Business Case and is accountable for its justification, but the day-to-day maintenance and update of the document is delegated to the Project Manager. Option B is wrong because Project Support provides administrative and clerical assistance, such as filing and version control, but does not have the authority or responsibility to maintain the Business Case's content or viability. Option D is wrong because the Senior Supplier is responsible for providing the project's products and ensuring supplier interests are met, not for maintaining the Business Case, which is a management product.
Which TWO statements about tolerances in PRINCE2 are correct?
Stage tolerances are defined by the Project Board.
Why this answer
Tolerances are defined for each stage by the Project Board, and the Project Manager may only deviate within that tolerance without escalation. They are set for time, cost, scope, quality, risk, and benefits.
During the Closing a Project process, which report is used to evaluate the project's performance against the approved Business Case?
The End Project Report reviews overall project performance against the Business Case.
Why this answer
The End Project Report is used to evaluate the project's performance against the Business Case and provide lessons for future projects.
What is the purpose of the Managing a Stage Boundary process?
Correct. The process provides an End Stage Report and next Stage Plan for decision.
Why this answer
The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information—via the End Stage Report and the next Stage Plan—to review the current stage's performance, assess the continued viability of the project, and make an informed decision on whether to authorize the next stage. This process ensures that the project remains aligned with the business case and tolerances before proceeding.
Exam trap
The trap here is confusing the 'gate review' purpose of Managing a Stage Boundary with the authorization or exception-handling activities that belong to other processes, leading candidates to select options that describe work package authorization or exception management.
How to eliminate wrong answers
Option B is wrong because authorizing a Work Package is the purpose of the Controlling a Stage process, not Managing a Stage Boundary. Option C is wrong because managing exceptions when tolerances are exceeded is handled by the Managing Product Delivery process (for work package exceptions) and the Controlling a Stage process (for stage-level exceptions), not by Managing a Stage Boundary. Option D is wrong because producing the Project Initiation Documentation is the purpose of the Initiating a Project process, which occurs before any stage boundary reviews.
What is the purpose of the Closing a Project process?
CP ensures controlled closure and handover.
Why this answer
Closing a Project ensures a controlled closure, including handing over products, evaluating the project, and recommending closure.
What is the definition of a project according to PRINCE2?
This is the PRINCE2 definition of a project.
Why this answer
PRINCE2 explicitly defines a project as 'a temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case.' This definition emphasizes the temporary nature, the focus on outputs (business products), and the governance through a Business Case, which justifies the project's initiation and continuation.
Exam trap
The trap here is that candidates often confuse a project with a program or operational work, and they may select Option B because it includes 'temporary organization' and 'defined output' but forget that PRINCE2 mandates the Business Case as a core component of the project definition.
How to eliminate wrong answers
Option A is wrong because it describes a permanent structure for ongoing operations, which is the definition of a functional or operational unit, not a project. Option B is wrong because it omits the critical element of the Business Case; PRINCE2 requires that a project delivers outputs according to an agreed Business Case, not just any defined output. Option D is wrong because it describes a permanent organization producing repetitive outputs, which is characteristic of business-as-usual or operations, not a project.
What is the difference between tailoring and embedding PRINCE2?
Tailoring is project-specific; embedding is organization-wide.
Why this answer
Tailoring adapts PRINCE2 to suit the specific project, while embedding integrates PRINCE2 into the organization's standard processes. Option A reverses these definitions, making it incorrect. Option B correctly states the definitions.
Options C and D are incorrect: tailoring and embedding are both applicable regardless of project size, and they are not synonyms.
During the Managing a Stage Boundary process, the Project Manager updates the Project Plan based on the actual results of the completed stage. What is the primary reason for updating the Project Plan?
Correct. The Project Plan is updated with actual data to maintain an accurate baseline for the whole project.
Why this answer
The Project Plan is updated to reflect actual performance and to provide an updated baseline for the remaining stages. This ensures the plan remains realistic and that the Business Case remains viable.
Which TWO of the following are differences between the Highlight Report and the Checkpoint Report?
Correct: Highlight Report goes to Project Board; Checkpoint Report goes to PM.
Why this answer
The Highlight Report is a formal report from the Project Manager to the Project Board, providing an overview of the stage's progress, while the Checkpoint Report is a detailed report from the Team Manager to the Project Manager, focusing on the Work Package status. This distinction is a key difference in PRINCE2's management reporting lines.
Exam trap
Candidates often mistake the frequency and scope of the Highlight Report, thinking it covers the entire project or is produced at the end of each stage. In PRINCE2, it reports on the current stage and its frequency is defined in the Communication Management Strategy.
Which document is used to capture the quality criteria for a product?
The Product Description includes quality criteria for each product.
Why this answer
The Product Description defines the product's purpose, composition, quality criteria, and quality methods.
Which TWO of the following are responsibilities of the Project Board?
The Project Board authorizes stage plans and any deviations from tolerances.
Why this answer
Options C and D are correct. The Project Board is responsible for authorizing stage plans and providing overall direction and control of the project. Option A is incorrect because producing the Project Initiation Documentation is a Project Manager responsibility.
Option B is incorrect because maintaining the Business Case is the Executive's role on behalf of the Board. Option E is incorrect because managing risks on a day-to-day basis is the Project Manager's role.
Which THREE of the following are true about the Directing a Project process?
The Board can give ad-hoc direction.
Why this answer
The Directing a Project process is designed for the Project Board to provide ad-hoc direction to the Project Manager, such as when a stage boundary is reached or an exception arises. This process does not involve day-to-day management but rather high-level decision-making and control.
Exam trap
The trap here is confusing the roles: candidates often think the Project Manager directs the project, but PRINCE2 explicitly assigns that authority to the Project Board, with the Project Manager managing day-to-day activities.
What is the minimum frequency of Project Board meetings?
The Project Board meets at key decision points and when exceptions arise.
Why this answer
The Project Board meets at predetermined points (stage boundaries) and when an exception is raised. They are exception-driven, so there is no fixed minimum frequency.
Which process is used by the Project Board to authorise the start of a new stage?
The Project Board authorises stage plans in DP.
Why this answer
Directing a Project includes authorising stage plans (including exception plans) and project closure.
What is the definition of quality in PRINCE2?
Correct. This is the PRINCE2 definition.
Why this answer
In PRINCE2, quality is defined as 'fit for purpose,' meaning the product must meet the stated user needs and expectations within the project's scope. This definition aligns with the PRINCE2 principle of continued business justification, ensuring that deliverables provide value by satisfying their intended use. Unlike conformance to specification, which focuses solely on meeting documented requirements, 'fit for purpose' emphasizes that the product must actually work in its operational environment.
Exam trap
The trap here is that candidates often confuse 'conformance to specification' (a common ISO 9000 definition) with PRINCE2's 'fit for purpose,' leading them to select Option A, but PRINCE2 prioritizes user needs over strict specification adherence.
How to eliminate wrong answers
Option A is wrong because 'conformance to specification' is a narrower, manufacturing-focused definition that does not account for whether the product meets user needs or is usable in context, which PRINCE2 requires. Option B is wrong because 'customer satisfaction' is an outcome of quality but not its formal definition in PRINCE2; the framework defines quality in terms of the product's fitness for its stated purpose, not subjective satisfaction. Option C is wrong because 'zero defects' is a quality control target from total quality management (TQM) and is not the PRINCE2 definition; PRINCE2 acknowledges that acceptable quality may include tolerances for defects based on cost and time constraints.
A project is in the Initiating a Project process. The Project Manager is creating the Project Initiation Documentation. Which plan should be produced during this process?
The Project Plan is produced during the Initiating a Project process and is part of the PID.
Why this answer
The Project Plan is created during the Initiating a Project process. Stage Plans are created during Managing a Stage Boundary. Team Plans are created by team managers as required.
Exception Plans are created in response to an exception.
Which PRINCE2 document provides the Project Board with a summary of the stage's progress, including achievements, issues, and forecasts, at regular intervals during a stage?
Correct. The Highlight Report is the regular progress report from PM to Project Board.
Why this answer
The Highlight Report is prepared by the Project Manager and sent to the Project Board at regular intervals (e.g., weekly) to provide a summary of stage progress, including achievements, issues, and forecasts.
Which TWO of the following are true about the relationship between Controlling a Stage (CS) and Managing Product Delivery (MP)?
In CS, the PM authorizes Work Packages; in MP, the Team Manager executes them.
Why this answer
CS is the PM's process for managing the stage; MP is the Team Manager's process for delivering Work Packages. The PM authorizes Work Packages in CS, and the Team Manager delivers them in MP.
Which document is the key output of the Initiating a Project process?
The PID is the main output of the Initiating a Project process, providing a foundation for project management.
Why this answer
The Initiating a Project process in PRINCE2 is where the project's foundations are established, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—including the Business Case, project plan, risk register, and controls—into a single, approved document that defines what the project will deliver and how it will be managed. This makes option C correct because the PID is the definitive output that triggers the next process, Managing a Stage Boundary.
Exam trap
PeopleCert often tests the distinction between the Project Brief (output of Starting Up a Project) and the Project Initiation Documentation (output of Initiating a Project), so the trap here is confusing the initial outline with the fully developed, approved baseline document.
How to eliminate wrong answers
Option A is wrong because the Project Brief is created during the Starting Up a Project process, not Initiating a Project; it provides initial context but is refined into the PID. Option B is wrong because the Stage Plan is an output of the Managing a Stage Boundary process, created for each management stage, not the overall project initiation. Option D is wrong because the Business Case is a component within the PID, not the key output itself; it is developed and updated throughout the project but the PID is the comprehensive document that includes it.
During the Managing Product Delivery process, the Team Manager identifies a problem that could affect the quality of a product. What should the Team Manager do?
The Team Manager reports progress and issues to the Project Manager through Checkpoint Reports.
Why this answer
The Team Manager should inform the Project Manager via the Checkpoint Report or, if urgent, via an issue. The team manager does not directly escalate to the Board.
What is the difference between the Starting Up a Project (SU) and Initiating a Project (IP) processes?
Correct. SU outputs the Project Brief; IP outputs the PID.
Why this answer
Starting Up a Project (SU) is the pre-project process that produces the Project Brief, which provides the outline business case and project approach needed to decide whether to proceed. Initiating a Project (IP) is the next process that produces the detailed Project Initiation Documentation (PID), including the full business case, project plan, and risk register, to establish a solid foundation for the project. The key difference is that SU creates the high-level justification and approach, while IP creates the comprehensive management documentation required for execution.
Exam trap
The trap here is that candidates confuse the outputs of SU and IP, often thinking the Project Brief is produced in IP or that the PID is produced in SU, but PRINCE2 explicitly assigns the Project Brief to SU and the PID to IP.
How to eliminate wrong answers
Option B is wrong because both SU and IP are mandatory processes in PRINCE2; IP is not optional. Option C is wrong because the Project Manager performs both SU and IP, while the Project Board provides direction and approval but does not perform the processes. Option D is wrong because SU appoints the Project Manager and Executive, while IP does not appoint the Project Board; the Project Board is already in place by the end of SU.
In the Managing Product Delivery process, what is the Team Manager responsible for?
The Team Manager in Managing Product Delivery accepts, executes, and delivers Work Packages.
Why this answer
In PRINCE2, the Managing Product Delivery process focuses on the work required to create project products. The Team Manager's primary responsibility is to accept Work Packages from the Project Manager and then deliver them by coordinating the team's work, ensuring the products meet the required quality criteria. This directly aligns with option A, as accepting and delivering Work Packages is the core function of the Team Manager within this process.
Exam trap
PeopleCert often tests the distinction between the Team Manager's operational role and the Project Manager's or Project Board's strategic responsibilities, causing candidates to confuse Checkpoint Reports with Highlight Reports or to attribute Business Case updates to the wrong role.
How to eliminate wrong answers
Option B is wrong because producing Highlight Reports is the responsibility of the Project Manager, not the Team Manager; the Team Manager provides Checkpoint Reports to the Project Manager. Option C is wrong because authorizing the initiation of the project is a key decision made by the Project Board, not the Team Manager. Option D is wrong because updating the Business Case is the responsibility of the Senior User or the Project Manager, as the Business Case is a strategic document that the Team Manager does not have authority to modify.
Which THREE of the following are components of the PRINCE2 quality management approach?
Methods are defined in the approach.
Why this answer
The Quality Management Approach includes standards, quality control methods, and quality assurance. The Quality Register is a separate document, not part of the approach. The Project Plan is also separate.
You are the project manager for a construction project with a project board consisting of an executive (who is also the senior user), a senior supplier, and a separate senior user. The executive is heavily involved in day-to-day operations and often gives direct instructions to team members, bypassing you. This has caused confusion and delays. The business case is still viable, but the project is behind schedule. What should you do?
Correct: address the issue professionally.
Why this answer
The project manager must manage the project according to the PRINCE2 management structure, which defines clear roles and responsibilities. The executive is overstepping their role by giving direct instructions to team members, bypassing the project manager, which violates the 'management by exception' principle. Speaking privately to the executive is the appropriate first step to resolve the issue informally and reinforce the need to follow the established project management structure, as per the 'Organizing' theme.
Exam trap
PeopleCert often tests the misconception that the project manager should immediately escalate or formalize executive interference, rather than first addressing the issue informally through direct communication to reinforce the management structure.
How to eliminate wrong answers
Option A is wrong because escalating to the senior supplier immediately is premature; the issue is with the executive's behavior, not a supplier-related problem, and the senior supplier has no authority over the executive. Option B is wrong because ignoring the executive's instructions without addressing the underlying issue could escalate the conflict and further damage the project's progress; the project manager must manage the relationship, not simply disregard instructions. Option C is wrong because issuing a change request to update the project plan to include the executive's instructions would formalize the bypassing behavior, undermining the project manager's authority and the PRINCE2 management structure, and does not address the root cause of the confusion.
The Project Board has delegated authority for change control decisions to a separate body. What is this body called?
The Change Authority is an optional role to which the Project Board delegates change control decisions.
Why this answer
In PRINCE2, the Change Authority is a body to which the Project Board delegates responsibility for making decisions on change requests and off-specifications, within defined limits. This allows the board to focus on strategic oversight while empowering a separate group to handle change control efficiently. The Change Authority is formally defined in the 'Organize' process and its authority is documented in the Project Initiation Documentation.
Exam trap
The trap here is that candidates confuse the Change Authority with Project Assurance, mistakenly thinking that assurance includes decision-making power, when in fact Project Assurance is an independent oversight function, not a decision-making body for change control.
How to eliminate wrong answers
Option B (Project Support) is wrong because Project Support provides administrative and clerical services to the project management team, not decision-making authority for change control. Option C (Project Assurance) is wrong because Project Assurance is responsible for monitoring and checking compliance with standards and plans, not for making change control decisions. Option D (Senior Supplier) is wrong because the Senior Supplier is a specific role on the Project Board representing the interests of those providing the project's products, not a separate delegated body for change control.
In PRINCE2, what is the primary purpose of the Product Breakdown Structure (PBS)?
The PBS is a hierarchical chart of all products.
Why this answer
The PBS is used to identify all the products that need to be created, providing a hierarchical decomposition of the project's outputs. Option A is wrong because the Product Flow Diagram shows the sequence. Option C is wrong because the PBS does not show dependencies; that is the Product Flow Diagram.
Option D is wrong because quality criteria are documented in Product Descriptions.
Which TWO of the following are typical roles in the Project Board?
Correct. The Senior Supplier is a Project Board role.
Why this answer
The Project Board is the PRINCE2 management layer responsible for overall project direction and decision-making. The Executive represents the business interests and is the ultimate decision-maker, while the Senior Supplier represents the interests of those providing the project's products or services. These are two of the three primary Project Board roles, the third being the Senior User.
Exam trap
The trap here is that candidates often confuse the Project Manager as a member of the Project Board, but PRINCE2 explicitly separates the 'directing' level (Project Board) from the 'managing' level (Project Manager), and the Project Manager reports to the Board, not sits on it.
Which role is responsible for the day-to-day management of the project within the tolerances set by the Project Board?
This is a core responsibility of the Project Manager.
Why this answer
The Project Manager manages the project on a day-to-day basis within the tolerances delegated by the Project Board.
Who is responsible for maintaining the Business Case throughout the project?
The Project Manager maintains the Business Case on behalf of the Executive.
Why this answer
In PRINCE2, the Project Manager is responsible for maintaining the Business Case throughout the project. This includes monitoring the project's viability against the Business Case, updating it with actual costs and benefits, and escalating any deviations to the Project Board. The Project Manager ensures the Business Case remains valid and aligned with the project's objectives.
Exam trap
Candidates often confuse accountability with responsibility, mistakenly assigning the maintenance of the Business Case to the Executive instead of the Project Manager. In PRINCE2, the Executive is accountable for the Business Case, but the Project Manager is responsible for its day-to-day maintenance and monitoring.
How to eliminate wrong answers
Option A is wrong because the Executive (Senior Responsible Owner) is accountable for the Business Case and its approval, but not for its day-to-day maintenance. Option C is wrong because Project Support provides administrative and configuration management services, not ownership or maintenance of the Business Case. Option D is wrong because the Senior User represents the users' interests and specifies benefits, but does not maintain the Business Case itself.
Which TWO of the following are outputs of the Starting Up a Project process?
Correct. The Project Brief is a key output of SU.
Why this answer
SU produces the Project Brief, initiation Stage Plan, and Daily Log. The PID is produced in IP, and the Benefits Management Approach is also part of IP.
What is the purpose of the Quality Review Technique?
The review ensures the product meets its defined quality criteria.
Why this answer
The Quality Review Technique is a team-based review to assess whether a product meets its quality criteria.
What is the purpose of the Closing a Project process?
Why this answer
The Closing a Project process is designed to provide a controlled closure of the project, ensuring that all objectives have been met, products are formally accepted, lessons are documented, and the project is officially handed over to operations or the customer. This process confirms that the project has delivered its agreed scope and that any remaining issues or risks are properly managed before closure.
Exam trap
PRINCE2 often tests the distinction between processes that occur during the project (like Controlling a Stage and Managing a Stage Boundary) versus the final closure process, leading candidates to confuse the purpose of Closing a Project with ongoing stage management activities.
How to eliminate wrong answers
Option A is wrong because authorising work packages is the purpose of the Controlling a Stage process, not Closing a Project. Option B is wrong because planning the next stage is part of the Managing a Stage Boundary process, which occurs at stage boundaries, not at project closure. Option C is wrong because initiating the project is the purpose of the Initiating a Project process, which sets up the project management foundation and the Project Initiation Documentation.
Which process is responsible for authorizing the initiation of a project?
DP is the Project Board process that authorizes initiation, project, stages, and closure.
Why this answer
The Directing a Project process is responsible for authorizing the initiation of a project because it sits at the management level, where the Project Board reviews the Project Brief and decides whether to proceed. The process includes the key activity 'Authorize Initiation,' which formally gives the Project Manager permission to start the Initiating a Project process and allocate resources.
Exam trap
A common confusion is between 'Starting Up a Project' and 'Directing a Project'—candidates mistakenly think the former authorizes initiation, but it only prepares the groundwork for the Board's decision.
How to eliminate wrong answers
Option A is wrong because Initiating a Project is the process that plans the project in detail, not the one that authorizes its own start; authorization must come from a higher level. Option C is wrong because Starting Up a Project is the pre-initiation process that prepares the Project Brief and appoints the team, but it does not authorize initiation—that decision is made by the Project Board during Directing a Project. Option D is wrong because Controlling a Stage is focused on managing day-to-day work within an authorized stage, not on granting permission to begin the project.
Who is responsible for maintaining the Business Case throughout the project?
The Project Manager maintains the Business Case under the direction of the Executive.
Why this answer
In PRINCE2, the Project Manager is responsible for maintaining the Business Case throughout the project. This includes monitoring the Business Case against the project's progress and updating it as necessary to ensure it remains viable and aligned with the project's objectives. The Project Manager does this by regularly reviewing the Business Case and reporting any changes or deviations to the Project Board.
Exam trap
A common pitfall in PRINCE2 is confusing accountability (Executive) with responsibility (Project Manager) for the Business Case. Candidates often incorrectly choose the Executive as the maintainer.
How to eliminate wrong answers
Option B is wrong because the Project Board is responsible for approving the Business Case and making key decisions, but not for its day-to-day maintenance. Option C is wrong because the Executive is the owner of the Business Case and is accountable for its content, but the actual maintenance task is delegated to the Project Manager. Option D is wrong because the Senior User represents the users' interests and provides requirements, but does not maintain the Business Case.
In PRINCE2, what is the role of the Senior Supplier on the Project Board?
The Senior Supplier ensures the project has the required supplier resources and that the supplier's view is represented.
Why this answer
The Senior Supplier represents those who provide the necessary goods, services, and expertise to the project.
Which THREE of the following are responsibilities of the Project Board in the Directing a Project process?
The Board provides direction.
Why this answer
The Project Board is responsible for providing overall direction and control of the project. Giving ad-hoc direction to the Project Manager (Option B) is a key responsibility within the Directing a Project process, as the Board must intervene when necessary to keep the project aligned with business objectives.
Exam trap
The trap here is confusing the Project Board's strategic oversight role with the Project Manager's operational duties, leading candidates to mistakenly select day-to-day management or reporting tasks as Board responsibilities.
The Project Manager notes that a Work Package is at risk of being delivered late. What should the Project Manager do?
The PM manages within stage tolerances and works with the Team Manager.
Why this answer
In PRINCE2, when a Work Package is at risk of being delivered late but remains within its agreed tolerances, the Project Manager should agree corrective actions with the Team Manager. This is because the Team Manager is responsible for day-to-day management of the Work Package, and the Project Manager's role is to support and guide without escalating unless tolerances are forecast to be exceeded. Corrective actions within tolerance keep the project on track without unnecessary escalation.
Exam trap
The trap here is confusing 'at risk of being delivered late' with 'forecast to exceed tolerances,' leading candidates to incorrectly escalate to the Project Board (Option C) instead of managing within tolerance.
How to eliminate wrong answers
Option B is wrong because updating the Project Plan immediately is a reactive administrative action that does not address the root cause of the delay; the plan should only be updated after corrective actions are agreed and implemented. Option C is wrong because escalation to the Project Board is only required when the Work Package is forecast to exceed its tolerances, not when it is merely at risk within tolerance. Option D is wrong because canceling the Work Package and reassigning it to another team is a drastic, disruptive action that bypasses the proper management-by-exception process and ignores the Team Manager's responsibility to resolve issues within tolerance.
What is the purpose of the Managing a Stage Boundary process?
The process produces a Stage Plan and updates the Business Case.
Why this answer
To provide the Project Board with information to review and approve the next stage.
What is the purpose of the Managing Product Delivery process?
MP is the Team Manager's process for delivering products.
Why this answer
The Managing Product Delivery process is responsible for accepting Work Packages from the Project Manager, executing the work to create the products defined in the Work Package, and delivering the completed products back to the Project Manager. This ensures that work is controlled, progress is reported, and the products meet the agreed quality criteria before delivery.
Exam trap
PRINCE2 often tests the distinction between 'Controlling a Stage' (which produces Highlight Reports and manages day-to-day work within a stage) and 'Managing Product Delivery' (which focuses on the acceptance, execution, and delivery of specific Work Packages).
How to eliminate wrong answers
Option B is wrong because directing the project and making key decisions is the purpose of the Directing a Project process, not Managing Product Delivery. Option C is wrong because planning the next stage and updating the project plan is the purpose of the Managing a Stage Boundary process. Option D is wrong because controlling the work within a stage and producing Highlight Reports is the purpose of the Controlling a Stage process, not Managing Product Delivery.
Which THREE of the following are outputs of the Initiating a Project process?
The Business Case is updated and approved in IP.
Why this answer
The Initiating a Project process updates the Business Case to reflect the detailed understanding of the project's justification, costs, benefits, and risks gained during initiation. This updated Business Case is a key output that confirms whether the project remains viable before proceeding.
Exam trap
The trap here is confusing outputs from the Initiating a Project process with those from later processes like Controlling a Stage or Closing a Project, leading candidates to select Highlight Report or Lessons Report.
Which THREE of the following are responsibilities of the Project Board?
The Board oversees the Business Case.
Why this answer
The Project Board is accountable for the Business Case, approves plans, and authorizes stage transitions.
Who is responsible for maintaining the Business Case throughout the project?
The Project Manager maintains the Business Case on behalf of the Executive.
Why this answer
The Project Manager maintains the Business Case, but the Executive (SRO) is the owner and accountable for it. The question asks who maintains it, so option C is correct. The Senior User defines benefits, and the Senior Supplier provides resources.
Which process is responsible for authorizing the start of each stage?
DP authorizes stage start.
Why this answer
The Directing a Project process is responsible for authorizing the start of each stage because it provides the high-level governance and decision-making authority from the Project Board. This process ensures that the Project Manager receives explicit permission to proceed with the next stage, based on the Stage Plan and updated Business Case. Without this authorization, the project cannot move forward to the next stage.
Exam trap
The trap here is that candidates confuse the process that prepares the request (Managing a Stage Boundary) with the process that grants the authorization (Directing a Project), leading them to select Option A instead of C.
How to eliminate wrong answers
Option A is wrong because Managing a Stage Boundary is the process that prepares the End Stage Report and the next Stage Plan for the Project Board, but it does not itself authorize the start of the next stage—it only requests authorization. Option B is wrong because Controlling a Stage is the process that manages the day-to-day work within a stage and handles issues and changes, but it does not have the authority to authorize the start of a new stage. Option D is wrong because Starting Up a Project is the pre-project process that creates the Project Brief and appoints the Project Board, but it occurs before any stages are authorized and does not authorize stage starts.
In PRINCE2, what is the purpose of the Managing a Stage Boundary process?
This is the core purpose of Managing a Stage Boundary.
Why this answer
The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and confirm continued business justification. Option D correctly identifies that this process involves planning the next stage and seeking Project Board approval before proceeding.
Exam trap
The trap here is confusing the Managing a Stage Boundary process with the Controlling a Stage process, as both involve stage-level activities, but only Managing a Stage Boundary focuses on planning the next stage and obtaining approval to proceed.
How to eliminate wrong answers
Option A is wrong because closing the project and handing over products is the purpose of the Closing a Project process, not Managing a Stage Boundary. Option B is wrong because authorizing the initiation of the project is the purpose of the Starting up a Project process and the Directing a Project process for project initiation authorization. Option C is wrong because managing the work of the current stage and reporting progress is the purpose of the Controlling a Stage process, which handles day-to-day management and progress reporting within a stage.
Which TWO of the following are produced in the Starting Up a Project process?
Correct. The plan for the initiation stage is created in SU.
Why this answer
The Starting Up a Project process is the first process in PRINCE2, executed before the project is formally initiated. Its purpose is to ensure that the project has a viable and worthwhile business case, and that the necessary authorities and resources are in place. The Initiation Stage Plan is produced to plan the work required for the Initiation Stage, and the Project Brief is produced to provide a firm foundation for the initiation of the project, containing the outline Business Case, project scope, and key risks.
Exam trap
PRINCE2 Foundation often tests the distinction between the Starting Up a Project and Initiating a Project processes, and the trap here is confusing the Project Brief (produced in SU) with the Project Initiation Documentation (produced in IP), or assuming that the Benefits Management Approach is created earlier than it actually is.
When is the Business Case formally reviewed and confirmed?
Correct: at stage boundaries the Business Case is reviewed for continued viability.
Why this answer
The Business Case is developed in pre-project, approved at initiation, and reviewed at each stage boundary.
Which document is the key output of the Initiating a Project process?
PID is the key output of IP.
Why this answer
The Project Initiation Documentation (PID) is the key output of the Initiating a Project process because it consolidates all the planning information needed to justify the project, define its scope, and establish the baseline for decision-making. It includes the Business Case, Project Plan, Risk Register, and other components that together form the foundation for project governance. Without the PID, there is no formal authorization to proceed with the project's delivery stages.
Exam trap
The trap here is that candidates often confuse the Project Brief (created in Starting Up a Project) with the Project Initiation Documentation (created in Initiating a Project), because both contain similar-sounding information, but the PID is far more detailed and includes the full project plan and business case.
How to eliminate wrong answers
Option A is wrong because the Daily Log is an informal record of issues, actions, and events, and it is created during the Starting Up a Project process, not as the key output of Initiating a Project. Option C is wrong because the End Stage Report is produced at the end of each management stage to summarize progress against the PID, not as an output of Initiating a Project. Option D is wrong because the Project Brief is created during the Starting Up a Project process to provide a high-level overview, and it is refined into the PID during Initiating a Project, not the key output itself.
In the Directing a Project process, who has the authority to authorize an exception plan that exceeds the project's stage tolerance but remains within project tolerance?
The Board authorizes exception plans as part of DP.
Why this answer
The Project Board authorizes exception plans. The Project Manager manages within tolerances; exceeding stage tolerance requires Board approval. The SRO alone cannot, and the team manager has no such authority.
What is the purpose of the Directing a Project process?
The Project Board authorizes stages, plans, and closure, and gives ad-hoc direction.
Why this answer
Directing a Project enables the Project Board to make key decisions and provide overall direction without managing day-to-day activities.
Who is responsible for maintaining the Business Case throughout the project?
Correct. The Project Manager maintains the Business Case, ensuring it reflects current information.
Why this answer
The Project Manager is responsible for maintaining the Business Case, ensuring it remains viable and up to date. The Executive (SRO) owns the Business Case and is accountable for it, but the PM does the day-to-day maintenance.
Which PRINCE2 role is optional and provides administrative support to the project?
Project Support is optional and provides admin support.
Why this answer
In PRINCE2, Project Support is an optional role that provides administrative services to the project, such as maintaining files, collecting progress data, and managing project documentation. The role is not mandatory because the project manager can perform these tasks or they can be delegated to a separate support function. This distinguishes it from the other roles, which have specific governance or delivery responsibilities.
Exam trap
The trap here is that candidates often confuse Project Support with Project Assurance, thinking both are mandatory oversight roles, but PRINCE2 explicitly separates administrative support (optional) from independent assurance (optional but distinct).
How to eliminate wrong answers
Option A is wrong because the Change Authority is a role that authorizes changes to baselines, not administrative support; it is optional but focuses on change control decisions. Option B is wrong because Project Assurance is an optional role that provides independent oversight and checks compliance with PRINCE2, not administrative support. Option C is wrong because the Team Manager is an optional role that manages the technical delivery of products within a team, not administrative support for the project.
Which document describes the quality expectations and standards for the project?
Correct. It sets out quality standards and procedures.
Why this answer
The Quality Management Approach (A) is the PRINCE2 document that defines the specific quality methods, standards, and responsibilities to be used during the project. It describes how quality will be managed, including the quality expectations, quality criteria, and the quality control and assurance activities that will be applied. This is distinct from the higher-level strategy or the product-focused descriptions.
Exam trap
The trap here is confusing the project-level 'Quality Management Approach' with the corporate-level 'Quality Management Strategy', as candidates often think the strategy document contains the project's specific quality expectations, but PRINCE2 separates strategic policy from tactical implementation.
How to eliminate wrong answers
Option B (Quality Management Strategy) is wrong because the Quality Management Strategy is a corporate or programme-level document that sets the overall quality policy and standards for the organization, not the project-specific quality expectations and standards. Option C (Project Plan) is wrong because the Project Plan describes the time, cost, and resource baselines for the project, not the detailed quality expectations and standards. Option D (Project Product Description) is wrong because it describes the final product's purpose, composition, and acceptance criteria, but it does not define the project's overall quality expectations and standards for all deliverables.
Which THREE of the following are responsibilities of the Project Manager during the Managing a Stage Boundary process?
The PM updates the Business Case with actuals and re-evaluates viability at stage boundaries.
Why this answer
The Project Manager is responsible for updating the Business Case during the Managing a Stage Boundary process to reflect any changes in costs, benefits, or risks that have occurred during the current stage, ensuring the project remains viable before proceeding to the next stage.
Exam trap
PRINCE2 Foundation exam often tests the distinction between 'create' and 'approve' in PRINCE2 processes, so the trap here is confusing the Project Manager's role in creating the next Stage Plan with the Project Board's role in approving it.
Which of the following is an optional role in the PRINCE2 project management team?
Project Support is optional and can be provided by a separate team member.
Why this answer
In PRINCE2, the Project Support role is optional and is only required when the project is large or complex enough to need administrative or specialist support. The PRINCE2 manual explicitly lists Project Support as a role that may be filled, whereas the Executive, Senior User, and Project Manager are mandatory roles on every project.
Exam trap
The trap here is that candidates often assume all roles listed in the PRINCE2 team structure are mandatory, but PRINCE2 explicitly designates Project Support as optional, while the Executive, Senior User, and Project Manager are always required.
How to eliminate wrong answers
Option A is wrong because the Executive is a mandatory role who owns the business case and provides overall accountability for the project. Option B is wrong because the Senior User is a mandatory role who represents the interests of those who will use the project's outputs. Option D is wrong because the Project Manager is a mandatory role who manages the day-to-day work and is required on every PRINCE2 project.
What is the difference between the Starting Up a Project process and the Initiating a Project process?
Correct distinction.
Why this answer
The Starting Up a Project (SU) process is a pre-project activity that ensures the project has a viable business justification and the necessary basic conditions (e.g., a clear project mandate, appointed executive, and project manager) before any detailed planning begins. The Initiating a Project (IP) process then takes this foundation and develops the detailed Project Initiation Documentation (PID), including the business case, risk register, and project plan, to establish solid management controls for the project. Option A correctly captures this sequential relationship: SU verifies readiness, while IP builds the detailed governance framework.
Exam trap
The trap here is confusing the outputs of SU and IP, specifically thinking the PID is produced in SU or that the Project Brief is produced in IP, which is a common PRINCE2 Foundation exam trick to test precise process knowledge.
How to eliminate wrong answers
Option B is wrong because it reverses the outputs: SU produces the Project Brief (not the PID), and IP produces the PID (not the Project Brief). Option C is wrong because SU is performed by the Project Manager (with the Executive’s approval), not the Project Board; the Project Board is involved in IP for approval but does not perform the process. Option D is wrong because SU and IP are distinct processes with different objectives and outputs; SU is a pre-project process, while IP is the first process after project authorization.
Which TWO statements correctly describe the difference between a Request for Change (RFC) and an Off-specification?
Correct. This accurately describes the nature of each type of issue.
Why this answer
An RFC is a proposal for a modification that is not currently required, while an Off-specification is something that is missing or deviating from the agreed specification. Option A is correct because an RFC suggests something new; option B is correct because an Off-specification indicates a required product is missing or incorrect. Option C is incorrect because changes may or may not affect the budget, and Off-specifications do not inherently decrease it.
Option D is incorrect because both RFCs and Off-specifications are subject to formal change control and can be rejected.
A project is forecast to exceed its cost tolerance at the project level. What should the Project Manager do?
The Project Manager should raise an Exception Report to the Project Board for decision.
Why this answer
When project-level tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.
During which process is the Project Initiation Documentation (PID) created?
The PID is the key output of the Initiating a Project process.
Why this answer
The Project Initiation Documentation (PID) is created during the Initiating a Project process. This process takes the initial project mandate and outline business case from Starting Up a Project and develops them into a comprehensive, baselined set of documents that define the project's scope, objectives, risks, and controls. The PID is formally approved by the Project Board during this process, providing the authority to proceed with the project.
Exam trap
The trap here is confusing the creation of the PID with its approval or subsequent updates; candidates often select Starting Up a Project because they think the PID is created early, but PRINCE2 clearly separates the initial Project Brief from the detailed PID developed in Initiating a Project.
How to eliminate wrong answers
Option A is wrong because Starting Up a Project produces the Project Brief, not the PID; the PID is developed later in Initiating a Project. Option C is wrong because Managing a Stage Boundary updates the PID (e.g., revising the Business Case or Risk Register) but does not create it from scratch. Option D is wrong because Directing a Project is the decision-making process where the Project Board approves the PID, but the actual creation of the PID occurs in Initiating a Project.
Practice PRINCE2F by domain
Target a specific domain to shore up weak areas.