CCNA Prince2 Practices Questions

In PRINCE2, the risk owner is accountable for the overall management of a risk, including monitoring and ensuring that appropriate responses are implemented. The risk actionee, on the other hand, is responsible for performing specific actions or tasks assigned as part of the risk response plan. Option C correctly captures this distinction between accountability and execution.

In PRINCE2, threat responses (for negative risks) are: Avoid (eliminate the threat by altering the plan), Reduce (lower the probability or impact), Fallback, Transfer, and Accept. From the options, 'Avoid' (A) and 'Reduce' (C) are threat responses. 'Exploit' (B) is an opportunity response. 'Reject' (E) is not a PRINCE2 term. 'Share' (D) is an opportunity response where the opportunity is shared with a third party to increase its chances; for threats, the equivalent is 'Transfer'. Therefore, Share is not a threat response.

The Product Breakdown Structure (PBS) is a key characteristic of PRINCE2's product-based planning approach. It provides a hierarchical decomposition of all products to be created, ensuring that the project's outputs are clearly defined before activities are planned. This aligns with PRINCE2's principle of focusing on products rather than activities.

The PRINCE2 project management team includes the Executive, Senior User, Senior Supplier, Project Manager, Team Manager, Project Assurance, and Project Support. The Project Board consists of the Executive, Senior User, and Senior Supplier. 'Project Sponsor' is not a PRINCE2 role; 'Steering Committee' is not a PRINCE2 term.

The Business Case practice is the correct answer because it is the PRINCE2 practice that specifically defines the reasons for initiating a project and ensures that the project remains desirable, viable, and achievable throughout its lifecycle. It provides the justification for continued investment by requiring regular review and update of the business justification, which is documented in the Business Case. Without a valid Business Case, the project should be stopped.

Quality Assurance (A) is correct because it is a key element of the PRINCE2 quality practice, focusing on ensuring that the project's quality management system is in place and operating effectively. It provides independent checks that the project is being managed according to defined quality processes.

A Request for Change (RFC) is a proposal to modify a baseline, while an Off-specification (Off-spec) describes something that should be provided by the product but is not. Therefore, option A is correct.

PRINCE2 requires that each risk has a named risk owner who is accountable for managing that risk and implementing the planned responses. This ensures clear accountability and proactive risk management throughout the project lifecycle.

The Executive is a defined role in the PRINCE2 project management team, responsible for overall project direction, key decision-making, and ensuring the project delivers business value. The Executive chairs the Project Board and is ultimately accountable for the project's success.

PRINCE2 defines quality as 'fit for purpose' — meeting agreed requirements and fulfilling its purpose.

The Risk Register is a PRINCE2 management product that captures and tracks all identified risks throughout the project lifecycle. It records risk descriptions, probability, impact, proximity, and responses, ensuring risks are actively managed and monitored. This aligns with the PRINCE2 principle of continued business justification by maintaining visibility of threats and opportunities.

A Work Package is the document that authorizes the Team Manager to create one or more products. It contains details of the work to be done and constraints.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve its completion, and authorize the next stage. This process ensures that the project remains viable and aligned with the business case before proceeding, making D the correct answer.

The Organising practice defines the project management team structure, including roles, responsibilities, and reporting lines. It establishes who is accountable for key decisions and how the team is organized to deliver the project. This is distinct from other practices that focus on justification, planning, or monitoring.

Options B and E are correct. A Product Description includes acceptance methods and quality criteria. Lessons Report, stage boundaries, and risk budget are not components of a Product Description.

The Business Case in PRINCE2 captures the justification for the project, including the expected benefits (tangible and intangible) that the project aims to deliver. Benefits are a core component because they define the value that the project must provide to justify the investment. Without expected benefits, the Business Case cannot demonstrate whether the project is worthwhile.

The purpose is to provide the Project Board with sufficient information to review the current stage, approve the next stage plan, and confirm continued business justification.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two recognized types of issue are 'Off-specification' (something that should be provided by the project but is not, or is provided incorrectly) and 'Request for Change' (a proposal for a change to a product's baseline). Options D and E are correct because they directly match these defined types.

Exploit and Enhance are opportunity responses. Avoid and Transfer are threat responses. Accept can be used for both.

The five threat responses are: avoid, reduce, transfer, accept, share. Fallback is not a separate response; it is part of a plan.

The Business Case is a core component of the Project Initiation Documentation (PID) because it provides the justification for the project, including costs, benefits, and risks. The Project Plan is also a component of the PID as it defines how and when the project objectives will be achieved, including timescales and resource requirements. Both are mandatory elements that form the foundation of the PID in PRINCE2.

Project Assurance is independent of the Project Manager and provides assurance to the Project Board.

The Highlight Report is produced by the Project Manager at intervals defined in the Communication Management Approach to update the Project Board on progress.

The Project Manager is responsible for maintaining the Business Case throughout the project because they manage day-to-day activities, track progress against the Business Case, and escalate any deviations to the Executive. PRINCE2 assigns this operational responsibility to the Project Manager to ensure continuous alignment with the project's justification.

In PRINCE2, when a project is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board by raising an Exception Report. This is because tolerances are delegated authority limits, and exceeding them requires the Project Board to decide on corrective action, such as approving a revised plan or adjusting tolerances. Option C is correct as it directly follows the PRINCE2 principle of management by exception.

Management by exception dictates that when a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. Continuing without escalation is not allowed.

The Organising practice defines the project management team structure, roles, and responsibilities, including the four levels of management (corporate/programme management, project board, project manager, and team manager) and the three project interests (business, user, supplier). It establishes clear accountability and authority within the PRINCE2 project management team.

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 closure, including authorizing stages, reviewing progress, and providing strategic direction.

The Initiating a Project process is responsible for establishing a solid foundation for the project, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—including the Project Plan, Business Case, and Project Brief—into a single, approved document that defines the project's scope, objectives, and controls. This document is the baseline against which project progress is measured and is formally approved by the Project Board before the project proceeds.

In PRINCE2, opportunity responses are specific actions to address opportunities (positive risks). 'Share' (Option A) is correct because it involves partnering with another party to exploit an opportunity, sharing the potential benefits. 'Enhance' (Option D) is correct because it means proactively increasing the probability and/or impact of an opportunity to maximize its potential benefits.

In PRINCE2, the Project Board sets stage tolerances for the Project Manager as part of the 'Manage by Stages' principle. This allows the Project Manager to manage the stage within defined tolerances without needing to escalate every minor deviation, ensuring delegated authority is clear and controlled.

The Project Manager is responsible for maintaining the Business Case throughout the project because PRINCE2 assigns the day-to-day management of the Business Case to the Project Manager, who must ensure it remains viable and aligned with project progress. The Project Manager updates the Business Case with actual costs, benefits, and risks, and presents it to the Project Board for approval at key decision points. This is defined in PRINCE2's Business Case management process, where the Project Manager owns the document's maintenance, not its approval.

Management by exception is a core PRINCE2 principle where the Project Board only gets involved when forecasts indicate that tolerances (e.g., time, cost, quality) will be exceeded. This allows the Project Manager to manage day-to-day within agreed tolerances, escalating only exceptions. Option B correctly captures this delegation of authority.

The Executive is the single individual accountable for the project's success and chairs the Project Board in PRINCE2. This role provides the business justification, secures funding, and makes key strategic decisions, ensuring the project remains viable and aligned with organizational objectives.

The purpose is to provide the Project Board with information to approve the next stage and review the current stage's performance.

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 to continue the project. It produces an End Stage Report summarizing the current stage's results and a Stage Plan for the next stage, enabling informed governance decisions.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify a baselined product, while an Off-specification (Off-spec) is a notification that a product does not meet its agreed specification. The key distinction is that an RFC seeks to change the specification itself, whereas an Off-spec reports a failure to conform to the existing specification. Option B correctly captures this fundamental difference.

The Plans practice defines the means of delivering the products by establishing a structured approach to planning, including the creation of project and stage plans. This facilitates communication and control by providing a clear roadmap for stakeholders and enabling progress tracking against baselines. It is not about defining quality criteria, managing changes, or assigning roles, which are covered by other PRINCE2 practices.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two defined types of issue are a Request for Change (RFC), which is a proposal for a change to a product's specification or baseline, and an Off-specification, which is something that should be provided by the project but is not (e.g., a missing feature or a product that does not meet its specification). Both are formally captured and managed through the Issue and Change Control practice.

C is correct because when a project forecasts exceeding its cost tolerance, the Project Manager must escalate the issue to the Project Board via an Exception Report. This is a PRINCE2 management by exception principle: tolerances are delegated limits, and exceeding them requires board-level decision-making, not unilateral action by the Project Manager.

Planning steps: design the plan, define products, identify activities, estimate, and schedule/document.

In PRINCE2, the 'Controlling a Stage' process is responsible for authorizing work packages to be executed by the team. This process ensures that each work package is formally assigned, with clear acceptance criteria, reporting arrangements, and any constraints, before the team proceeds with delivery.

The Quality Review technique is used to assess whether a product meets its quality criteria and to identify errors.

A Request for Change is a proposal for a change to the project's baselines, while an Off-specification is something that should be provided but is not (or is forecast not to be).

When a tolerance is forecast to be exceeded, the PM must escalate via an Exception Report to the Project Board. This is management by exception.

A Request for Change is a proposal for a modification to a product that has been approved, while an Off-specification is a product that does not meet its specification.

The Highlight Report is a progress report that provides the Project Board with a summary of the project's status at a frequency defined in the Communication Management Approach. It is specifically designed to keep the Project Board informed of progress, achievements, and any issues or risks that require their attention. The Project Board is the sole recipient of the Highlight Report, as they are responsible for overall project governance and decision-making.

Exploit is the correct risk response for an opportunity the project wants to make more likely to happen. In PRINCE2, the Exploit response is specifically used when the project actively seeks to ensure that an opportunity is realized, often by allocating resources or taking direct actions to increase the probability of the positive event occurring. This contrasts with Enhance, which only increases the probability or impact without guaranteeing the outcome.

An off-specification (Off-spec) is the correct type of issue when a product has been delivered but does not meet its agreed specification. In PRINCE2, an off-specification is defined as a situation where a product should be produced according to its specification but is not, or where a product is delivered that does not meet its specification. This directly matches the scenario described.

The 'management by exception' principle in PRINCE2 means that the Project Board sets tolerances for time, cost, quality, scope, risk, and benefits, and only requires the Project Manager to escalate if those tolerances are forecast to be exceeded. This allows the Project Manager to manage within tolerances without constant board involvement, empowering them to make day-to-day decisions while the Board focuses on strategic issues.

The Quality Management Approach defines how quality will be managed, including quality criteria and acceptance methods.

Management by exception is a key principle where tolerances are set and escalation occurs only when tolerances are forecast to be exceeded.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. The two types of issue are 'Off-specification' (something that should be provided but is not) and 'Request for Change' (a proposal for a change to a baseline). Options B and E are correct because they directly match these defined types.

According to the management by exception principle, when a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

A Product Flow Diagram shows the order in which products will be developed and the dependencies between them. It is a key input to the activity network.

PRINCE2 defines five threat responses (Avoid, Transfer, Mitigate, Accept, Contingent) and five opportunity responses (Exploit, Share, Enhance, Accept, Contingent). 'Exploit' is a specific opportunity response that seeks to make the opportunity happen. 'Accept' is also an opportunity response, meaning the opportunity is accepted without proactive action, but with a contingency plan. Therefore, both A and B are correct opportunity responses.

Managing a Stage Boundary (SB) is designed to provide the Project Board with information to review the current stage's performance, approve the next stage plan, and update the Business Case and project plan.

The risk owner is responsible for managing the risk, while the risk actionee performs specific actions.

An RFC proposes a modification to a product that has been approved or baselined; an Off-spec is something that should be provided but is not (or will not be) as specified.

In PRINCE2, the Executive (Senior Responsible Owner) is the single point of accountability for the project's business justification. This role owns the business case, ensures the project remains viable, and has ultimate authority over its initiation, continuation, and closure. The Project Manager is accountable for day-to-day management, not the business justification.

An Off-specification is something that should be provided but is not (or is wrong). A Request for Change is a proposed modification to a baselined product.