CCNA Prince2 Practices Questions

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.

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.

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.

The Business Case is developed in pre-project, approved at initiation, and reviewed at each stage boundary.

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.

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.

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.

When project-level tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing the foundation for the project.

B is correct because the Change practice in PRINCE2 is responsible for managing product versions and baselines. It ensures that all changes to products are controlled, recorded, and traceable, using configuration management to track versions and baselines of products throughout the project lifecycle.

The quality review technique is a structured review of a product against its quality criteria. It involves a chair, presenter, and reviewers. It is not used for all products (some may use other methods) and is not the same as quality assurance (which is broader).

A Request for Change (RFC) is a formal proposal to modify a product or process that is already baselined, typically for enhancements or corrective actions, while an Off-specification (Off-spec) is a formal notification that a product or component does not meet its agreed specification or baseline. In PRINCE2, an RFC seeks to change the baseline, whereas an Off-spec reports a deviation from the baseline that must be resolved.

The Initiating a Project process is where the project's foundations are fully defined, and its key output is the Project Initiation Documentation (PID). The PID consolidates all essential information—including the Business Case, Project Plan, and risk assessments—into a single, controlled document that forms the basis for project governance and decision-making. This is distinct from the Project Brief, which is an input created earlier in the Starting Up a Project process.

The Project Manager maintains the Business Case day-to-day, but the Executive (SRO) owns it and is ultimately accountable for the business justification.

Management by exception means delegating authority within tolerances and escalating when tolerances are forecast to be exceeded.

The risk actionee is responsible for implementing the agreed response. The risk owner owns the risk and manages the response, but the actionee actually carries out the actions.

The Executive (Senior Responsible Owner) is the single point of accountability for the Business Case and ensuring value for money. The Project Manager manages the project but is not accountable. The Senior User and Senior Supplier are part of the Project Board but not accountable for the Business Case.

PRINCE2 defines quality as 'fit for purpose' — the product should satisfy the user's needs.

The Product Flow Diagram shows the order in which products are developed and their dependencies, including external dependencies.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing the baseline for project management.

PRINCE2 defines quality as 'fit for purpose'—the product must be suitable for its intended use.

The Project Manager must first log the request formally in the Issue Register as a Request for Change to ensure it is captured and tracked. Then, an impact assessment is conducted. This is required by PRINCE2's Change Control approach before any decision to approve or reject.

Configuration management in PRINCE2 includes two key elements: change control, which manages changes to configuration items, and version control, which tracks different versions. Baseline management is part of identification, not a separate element. Quality control and risk identification are separate disciplines.

PRINCE2 mandates that the Project Manager and Project Assurance roles must be separate to ensure objective oversight of the project. Project Assurance is responsible for monitoring compliance with PRINCE2 and the project's justification, and if the same person held both roles, they would be checking their own work, creating a conflict of interest. This separation is a key governance control in the PRINCE2 management structure.

Any off-specification must be formally documented as an issue. The team should not have implemented a workaround without approval. The Project Manager should raise an Issue Report and investigate the impact.

When stage tolerances are forecast to be exceeded, the Project Manager raises an Exception Report and the Managing a Stage Boundary process is used to plan the response. The Project Board may approve an Exception Plan via this process.

The Change Authority in PRINCE2 is a role that is delegated by the Project Board to approve requests for change within a specific, agreed-upon limit (e.g., cost or time). This allows for efficient decision-making without requiring the full Project Board to convene for every minor change, while still maintaining control over the project's scope and budget.

In PRINCE2, an issue is a relevant event that has occurred and requires management attention. A Request for Change (RFC) is a formal proposal for a change to a product, and an Off-specification is a situation where a product does not meet its specification. Both are defined as types of issue in the PRINCE2 framework.

The Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. Major risks and expected benefits are two of these.

The Project Manager is responsible for maintaining the Business Case on a day-to-day basis, while the Executive (SRO) owns it and is ultimately accountable for its justification.

The Project Manager is responsible for maintaining the Business Case throughout the project because PRINCE2 assigns this role to the Project Manager as part of day-to-day management. The Project Manager monitors actual costs, benefits, and risks against the Business Case, and updates it when necessary to ensure it remains viable. This is distinct from the Executive, who owns the Business Case and approves changes, but does not perform the ongoing maintenance.

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 but is not) and 'Request for Change' (a proposal for a change to a product's specification). These are formally defined in the PRINCE2 manual as the only issue types.

The Project Manager is responsible for producing and maintaining the Project Plan, as defined in PRINCE2's management products. This includes defining the project's stages, activities, dependencies, and resource estimates, and ensuring the plan aligns with the Business Case. The Project Manager owns the planning process and is accountable for the plan's accuracy and updates throughout the project.

A Highlight Report is sent from the Project Manager to the Project Board regularly, while a Checkpoint Report is sent from the Team Manager to the Project Manager more frequently.

When an Exception Plan is approved, the project board authorizes the project manager to proceed with the plan. This triggers the Managing a Stage Boundary process because the exception plan replaces the current stage plan, requiring a formal stage boundary to update the project plan, business case, and risk register before the next stage begins.

The Risk practice in PRINCE2 is specifically designed to identify, assess, and control uncertainties that could affect the project's objectives. During the initiation stage, the project manager applies this practice to systematically identify major risks, evaluate their probability and impact, and plan appropriate responses, ensuring proactive management of threats and opportunities.

In PRINCE2, during the Controlling a Stage process, the Project Manager receives Checkpoint Reports from Team Managers. The Project Manager uses the information from these reports to compile the Highlight Report for the Project Board. Therefore, the correct action is to use it to compile the next Highlight Report.

Project Assurance is an independent monitoring function, separate from the project management team, that ensures the project remains compliant with PRINCE2 principles and controls. Project Support, in contrast, is a service-oriented function that provides administrative and clerical services to the project manager and team, such as maintaining logs, filing, and scheduling. Option B correctly captures this distinction: independence for assurance versus administrative services for support.

In PRINCE2, the risk owner is the person who is accountable for the management and monitoring of a specific risk, including ensuring that appropriate response actions are planned and executed. The risk actionee, on the other hand, is the person assigned to implement the specific response actions defined for that risk. Option B correctly captures this distinction: the risk owner is accountable, while the risk actionee implements the response actions.

The Business Case includes reasons, expected benefits, costs, timescale, etc.

Project Assurance is the Project Board's responsibility, but it can be delegated to individuals or teams independent of the Project Manager.

The risk owner is responsible for managing the risk overall. The risk actionee is responsible for carrying out specific risk response actions.

A Request for Change is a proposal for a change that would modify agreed baselines or requirements. An Off-specification is something that should be provided but is not currently present (or is incorrect).

During the Managing Product Delivery process, the Team Manager is responsible for producing the Checkpoint Report. This report provides a regular update on progress against the Work Package, including actual time and resources used, quality activities completed, and any issues or risks. It is the primary communication from the Team Manager to the Project Manager during the work delivery phase.

The Product Breakdown Structure (PBS) in PRINCE2's product-based planning technique is a hierarchical diagram that decomposes the final project output into all the component products (both management and specialist) that must be created. It ensures that the project scope is fully defined before any activity planning begins, directly supporting the 'focus on products' principle. Option A correctly identifies this purpose.

The Business Case includes: reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The Quality Register is a separate document used for tracking quality activities.

When a work package tolerance is forecast to be exceeded, the team manager should inform the Project Manager via a Checkpoint Report so the PM can assess impact.

'Expected benefits' is a core component of the Business Case in PRINCE2, quantifying the justification for the project. Option C is correct because 'Major risks' are also a required component, as the Business Case must include an assessment of the risks that could affect the project's viability.

In PRINCE2, when a project forecasts exceeding its stage-level cost tolerance, the Project Manager must first escalate the issue to the Project Board by raising an Exception Report. This is because the Project Manager does not have authority to exceed the delegated tolerance; the Project Board must decide on corrective action, such as approving a revised plan or closing the project. Option C is correct as it aligns with the PRINCE2 principle of management by exception.

The Business Case in PRINCE2 is a document that justifies the project's initiation and continued viability. It contains components such as Expected Benefits, Investment Appraisal, and Major Risks. The Risk Register is a separate management product used to record and track identified risks, not a component of the Business Case itself.

Expected benefits and major risks are key components of the Business Case. Options and timescale are also components but not listed as correct in this set; the question asks for exactly two.

PRINCE2 defines quality as 'fit for purpose,' meaning the product meets its stated requirements and user expectations.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify any approved baseline (e.g., scope, schedule, cost), while an Off-specification (Off-spec) is a documented deviation where a product or process fails to meet its agreed specification. Option D correctly captures this fundamental distinction: an RFC proposes a change to a baseline, whereas an Off-spec records a failure to meet a specification.

The Senior User defines the acceptance criteria on behalf of the users.

Product-based planning in PRINCE2 ensures that all products (both management and specialist) are identified and defined in the Product Breakdown Structure and Product Descriptions before any activities or dependencies are planned. This approach prevents scope creep and ensures that the project plan is built around what needs to be delivered, not just tasks. Option D is correct because it directly reflects this principle: defining products first, then planning activities.

A Product Status Account provides information about the status of products, such as version and location.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

The Product Status Account is a PRINCE2 management product that provides a snapshot of the status of all products within a project at a given point in time. Its purpose is to give stakeholders and the project manager a consolidated view of which products are complete, in progress, or have issues, enabling informed decision-making and control.

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 Business Case, Project Plan, and Risk Register, to define the project's scope, objectives, and controls. This document is used to confirm that the project is viable and to obtain authorization to proceed.

The Quality Register is used to record all quality management activities, including planned and completed quality checks.

The Project Board is responsible for authorizing stage boundaries, which involves reviewing the current stage's progress, approving the next stage plan, and ensuring continued business justification. This is a key decision point in PRINCE2 where the Board assesses whether the project should proceed to the next stage.

The Risk Register is the central repository for recording and tracking all identified risks (both threats and opportunities) throughout the project lifecycle. It includes details such as risk description, probability, impact, proximity, and the planned responses, ensuring that every risk is managed and monitored. Option C is correct because it captures the complete purpose of the Risk Register as defined in PRINCE2.

The quality management approach includes the quality control methods, quality assurance approach, and the roles and responsibilities for quality.

In PRINCE2, the Team Manager reports progress to the Project Manager using the Checkpoint Report. This report is a periodic (typically weekly) progress update from the Team Manager to the Project Manager, covering work completed, next steps, and any issues within the work package. It is the formal mechanism for the Team Manager to report on progress during a stage.

The Business Case includes reasons, benefits, dis-benefits, costs, timescale, risks, etc. The Risk Register is a separate document.