CCNA Prince2 Practices Questions

The Business Case includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The risk register is a separate document.

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.

The Project Board provides overall direction, approves plans, and makes key decisions. Day-to-day management is the Project Manager's role, and configuration management is typically done by Project Support.

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 focuses on defining the required products first, then the activities needed to produce them, ensuring clarity and reducing omissions.

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.

A Product Status Account is a report on the status of one or more products, typically used to show configuration item records and their current state (e.g., approved, in development). It is not a plan or a quality document.

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.

Option A is correct because 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.

A Request for Change proposes a modification to agreed baselines, while an Off-specification is a product that deviates from its specification.

PRINCE2 defines quality as 'fit for purpose', meaning the product meets its agreed requirements.

The Team Manager handles risks within the work package; the Project Manager manages stage-level risks.

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

The Project Board, particularly the Executive and other board members, are responsible for providing independent assurance. Project Assurance is a role on the Project Board.

The Change practice in PRINCE2 provides the framework for managing changes to baselined products, including issue and change control procedures, configuration management, and the use of change authority levels. It defines how proposed changes are captured, assessed, and either approved or rejected, ensuring that baselined products are modified in a controlled manner.

Request for Change and Off-specification are types of issue. Options A and B are correct.

Project Assurance is the PRINCE2 role responsible for providing independent assurance that the project is being conducted properly. This role is separate from the Project Manager and Project Support, ensuring objective oversight of the project's adherence to PRINCE2 principles, themes, and processes. The Project Board delegates this responsibility to one or more individuals who are independent of the day-to-day management.

A Business Case in PRINCE2 is the document that justifies the project's initiation and continued viability. Major risks are a component because they must be identified and assessed to determine if the project's potential rewards outweigh the threats. Expected benefits are also a core component, as they define the measurable improvements that the project is expected to deliver, forming the basis for the justification.

The Project Initiation Documentation (PID) is the key output, as it formalises the project's scope, plan, and controls.

The Project Manager is responsible for maintaining the Business Case as part of day-to-day management, while the Executive owns it and approves changes.

The Project Board approves the Project Plan as part of the PID during Initiating a Project.

When a stage tolerance is forecast to be exceeded, the Project Manager must raise an Exception Report to the Project Board. This is management by exception.

The Project Manager is responsible for maintaining the Business Case throughout the project, including updating it at each stage boundary. The Executive owns the Business Case but does not maintain it.

The Project Manager must assess the impact on stage tolerances. If the delay is within tolerance, they can take corrective action. If it exceeds tolerance, they must escalate via an Exception Report.

Opportunity responses include exploit, enhance, share, and reject. Avoid and transfer are threat responses.

An RFC proposes a modification to an agreed product, while an Off-spec reports that an agreed product does not meet its specification. An RFC is proactive; an Off-spec is a deviation that has already occurred.

Project Assurance is independent of the Project Manager and reports to the Project Board. Project Support provides administrative support.

Managing a Stage Boundary provides information to the Project Board to review the current stage, approve the next stage plan, and assess continuing viability.

The Quality Review technique is a structured review of a product to assess its quality against criteria, involving a chair, presenter, and reviewers. It is not a test or acceptance method.

In PRINCE2, threat response types are designed to address negative risks (threats). 'Reduce' (also called 'Mitigate') involves taking action to lower the probability and/or impact of a threat to an acceptable level. 'Transfer' shifts the financial or contractual impact of a threat to a third party (e.g., insurance). 'Avoid' involves changing the plan to eliminate the threat entirely or protect the project from its impact. These three are explicitly listed in the PRINCE2 risk management practice.

For an opportunity with high probability and high impact, the 'exploit' response is appropriate to maximize the benefit.

The Executive (SRO) is ultimately accountable for the business case and justification.

A Request for Change proposes a modification to an agreed baseline, whereas an Off-specification identifies something that was specified but not delivered.

The Product Breakdown Structure (PBS) is a hierarchical diagram showing all products in the project. The Product Flow Diagram shows sequence, and Product Descriptions define quality criteria.

The Project Plan, Stage Plans, and Product Descriptions are baselined. Highlight Reports are reports, not baselines. The Issue Register records issues but is not a baseline.

Expected benefits and major risks are standard components of a Business Case. Dis-benefits and timescales are also components, but the question asks for specific ones.

The Project Initiation Documentation (PID) is the key output that defines the project and provides a baseline for decision-making.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It provides a comprehensive baseline for the project.

The Project Board consists of the Executive, Senior User, and Senior Supplier. The Project Manager and Team Manager are not board members.

The Managing a Stage Boundary process provides the Project Board with information needed to review the current stage, approve the next stage plan, and assess ongoing business justification.

The risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate. Identify is first.

In PRINCE2, the Executive is the single individual on the Project Board who has overall accountability for the project's business justification and success. The Executive is responsible for appointing the Project Manager, as defined in the PRINCE2 manual's management roles section. This ensures the Project Manager is selected by the person who owns the business case and can delegate day-to-day management authority.

A Request for Change is a proposal for a modification (new requirement), while an Off-specification is a product that has failed to meet its specification. Both are issue types. Option C correctly captures this.

The Product Flow Diagram shows the sequence and dependencies of product development.

The Managing a Stage Boundary process produces an End Stage Report and a Stage Plan for the next stage. The Project Plan is updated, not created. The Benefits Review Plan is created during the Initiating a Project process.

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

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

Quality Assurance is an independent check that processes are followed; Quality Control checks that products meet specifications.

A Request for Change proposes a change that is not currently required by the baseline, while an Off-specification is a failure to deliver something that was specified.

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

The Quality practice in PRINCE2 provides the framework for quality planning and control. It defines how the project will ensure that its products meet customer expectations and are fit for purpose, including the methods for quality assurance and quality control activities. During the Initiating a Project process, the project manager uses this practice to establish the project's approach to quality, which is documented in the Quality Management Strategy.

The Issue Register is the PRINCE2 management product used to capture and manage issues that may affect the project's baselines, such as scope, schedule, or cost. Baselines are formally approved versions of management products, and any proposed change, off-specification, or problem/concern that could impact them must be logged in the Issue Register for assessment and decision-making.

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

PRINCE2 defines quality as 'fit for purpose', meaning the product meets the stated requirements. Option A is correct.

In PRINCE2, when a stage tolerance is forecast to be exceeded, the project manager must escalate the issue to the project board. This is done through the 'Controlling a Stage' process, which includes the 'Escalate' activity. The process ensures that the project manager reports the forecast deviation and requests guidance or a decision from the project board, rather than taking corrective action independently.

The Quality Review technique is a structured review to assess whether a product meets its quality criteria and to identify defects. It is not for updating the Business Case, finalizing the project, or training users.

The Business Case components include reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. The Project Plan is a separate management product.

The Highlight Report is a regular report from the Project Manager to the Project Board summarizing progress, achievements, and issues within the current stage.

PRINCE2 defines four opportunity responses: exploit, enhance, share, and reject. 'Enhance' is one of these.

The Project Board authorizes the change budget, but they may delegate authority to the Change Authority to approve changes within that budget.