CCNA Prince2 Practices Questions

The Project Board is responsible for authorizing the start of each stage, including the initiation stage, by approving the Stage Plan and committing the required resources. This ensures that management stage boundaries are formally controlled and that the project remains aligned with the business case. Option D is correct because the Project Board approves the Project Plan (the overall plan for the project) to confirm that it is viable and consistent with the business case before the project proceeds.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process and serves as the baseline for the project.

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

The Project Board is responsible for approving Stage Plans (Option C) because it provides the necessary authority for the Project Manager to proceed with the next stage of work. This approval ensures that the project remains aligned with the business case and tolerances set by the board. The board also has a key responsibility to provide assurance (Option D) that the project is being managed correctly and that risks are being controlled, which is a core governance function in PRINCE2.

The project product description belongs to the Quality practice because it defines the product's quality criteria, quality tolerances, acceptance methods, and quality responsibilities. It is used to ensure that the project's outputs meet the required quality standards and is a key input to the quality management approach.

Avoid is a threat response, not an opportunity response. The opportunity responses are exploit, enhance, share, and reject.

The Lessons Log is the PRINCE2 management product specifically designed to capture lessons as they occur throughout the project lifecycle. It is a dynamic repository where the project team records both positive and negative experiences, ensuring that lessons are not lost and can be reviewed at key points, such as stage boundaries and project closure.

The Executive is the single individual responsible for the Business Case in PRINCE2. They own the project's justification and ensure it remains viable throughout the project lifecycle, approving any changes that affect its viability. The Business Case is the Executive's primary accountability, as defined in the PRINCE2 manual.

Reduce is the correct risk response because it involves implementing actions to lower the probability or impact of a threat while still accepting that the risk may occur. In PRINCE2, this is a proactive response where the project team actively manages the risk by, for example, adding redundancy or conducting more frequent testing to decrease the likelihood of failure. The key is that the risk is not eliminated entirely but its effects are mitigated.

Transfer involves shifting the financial impact of a risk to a third party, e.g., through insurance or contract.

Project Assurance is an independent role that provides objective oversight to ensure the project remains viable and compliant with PRINCE2 principles, while Project Support is an administrative role that handles tasks like planning tools, filing, and configuration management. The independence of Project Assurance from the Project Manager is critical to avoid conflicts of interest, whereas Project Support serves the Project Manager and the team. This separation ensures that assurance activities are unbiased and that support services are efficient.

The Project Manager is responsible for maintaining the Business Case (keeping it up to date), while the Executive owns it and is accountable for its justification.

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 as necessary to reflect changes in costs, benefits, and risks. PRINCE2 assigns this responsibility to the Project Manager to ensure the Business Case remains viable and aligned with project objectives at all times.

In PRINCE2, a Request for Change (RFC) is a formal proposal to modify an approved baseline (e.g., a product description, plan, or schedule), whereas an Off-specification is a formal notification that a product or component does not meet its specified requirements or quality criteria. The core distinction lies in the nature of the issue: an RFC seeks to change what was agreed, while an Off-specification reports a failure to deliver what was agreed.

In PRINCE2, tolerances are predefined limits for deviations in plan performance, and the six standard tolerances are Time, Cost, Quality, Scope, Risk, and Benefit. Option B (Risk) is correct because risk tolerance defines the acceptable level of risk exposure for a project, allowing the project manager to manage within that threshold without escalating. Option D (Quality) is correct because quality tolerance sets the acceptable deviation from specified quality criteria, ensuring deliverables meet agreed standards.

Highlight Reports are prepared by the Project Manager and sent to the Project Board (and possibly stakeholders) at regular intervals.

'Purpose' is a mandatory component of a Product Description in PRINCE2. It describes what the product is intended to do and why it is needed, providing clarity on its role within the project's output. This aligns with the PRINCE2 principle of continued business justification, ensuring every product has a defined reason for existence.

The Product Description defines the quality criteria, acceptance methods, and other details for each product. The Quality Management Approach defines the overall quality strategy, not the specific criteria for individual products.

A cautious appetite means risk-averse; even low probability opportunities may be rejected if they carry risk.

Project Assurance is an independent role that ensures the project remains aligned with business, user, and supplier interests.

In PRINCE2's risk management procedure, the risk owner is responsible for managing, monitoring, and controlling all aspects of a risk, including ensuring that appropriate responses are implemented. The risk actionee, on the other hand, is assigned to carry out specific risk response actions. Option B correctly captures this distinction: the risk owner manages the risk overall, while the risk actionee performs specific actions.

Project assurance is the responsibility of the Project Board, which provides independent assurance.

A Business Case in PRINCE2 must include the justification for the project, which requires an assessment of the major risks that could affect the viability of the project. 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 cost-benefit analysis.

A Request for Change (RFC) is a formal proposal to modify an approved baseline product or process, while an Off-specification is a product that has been identified as not meeting its agreed specification. The key distinction is that an RFC seeks to change the specification itself, whereas an Off-specification indicates a deviation from an already-approved specification that must be resolved.

Transferring the financial impact to a third party (insurance) is a 'transfer' response. 'Reduce' would involve actions to lower probability or impact. 'Accept' would be to take the risk without action.

Options B and C are correct. The PRINCE2 risk management procedure consists of five steps: Identify, Assess, Plan, Implement, and Communicate. 'Assess' involves evaluating the probability and impact of risks, while 'Implement' involves executing the planned risk responses. 'Monitor' and 'Control' are not separate steps in the procedure; they are activities that occur within the 'Communicate' and 'Implement' steps, respectively.

In PRINCE2, when a project forecasts exceeding 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 limits; exceeding them requires board-level decision-making. Option B correctly follows the PRINCE2 exception management process, ensuring the board can assess the impact on the Business Case and authorize corrective action.

When a stage tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board immediately via an Exception Report — this is PRINCE2's management by exception principle. The Project Manager cannot unilaterally exceed tolerances (C), continue without escalation (B), or close the project without Board decision (D).

The Project Board is responsible for providing overall direction and control of the project, ensuring it remains aligned with business objectives and governance requirements. This includes making key decisions, approving major deliverables, and authorizing stage transitions as defined in PRINCE2's management by stages principle.

The Benefits Management Approach defines how the project's benefits will be measured, tracked, and realized throughout the project and into operations. Since the project board is concerned about benefits realization, updating this approach with revised measurement criteria, review timing, or ownership details directly addresses their concern by providing a clear plan for ensuring benefits are achieved.

PRINCE2 defines three types of issues: Request for Change, Off-specification, and Problem/Concern. Therefore, options A, B, and D are correct. Option C is a risk, not an issue, and option E is effectively the same as option A but under a different name; PRINCE2 uses the term 'Request for Change' specifically, so 'Change request' is not a recognized issue type.

In PRINCE2, threat responses are actions taken to address negative risks. 'Reduce' (also called 'Mitigate') is a valid response that aims to lower the probability and/or impact of a threat to an acceptable level. This is one of the five standard threat response categories defined in the PRINCE2 risk management practice.

The Business Case includes expected benefits, costs, timescales, major risks, etc. Options, investment appraisal, and dis-benefits are also components.

The Checkpoint Report is a PRINCE2 management product used by the Team Manager to report progress of a Work Package to the Project Manager. Its purpose is to provide regular, detailed progress updates on the work being performed by the team, ensuring the Project Manager can monitor delivery against the Work Package plan. This is distinct from higher-level reports like the End Stage Report or Highlight Report.

The Business Case includes expected benefits, costs, and investment appraisal, among others. Options and risks are also components.

Project Assurance is a PRINCE2 responsibility that provides an independent check on the project's progress, compliance, and viability. The Project Board members (or their delegates) are accountable for this function because they represent the business, user, and supplier interests, ensuring objective oversight separate from day-to-day management.

The 'Reduce' response involves proactive actions to lower the probability and/or impact of a threat.

A Request for Change (RFC) is a formal proposal to modify an approved baseline (e.g., a product description, plan, or scope), while an Off-specification (Off-spec) is a deviation from a baseline that has been identified—meaning something that should be there is missing or something that should not be there is present. In PRINCE2, both are types of issues recorded in the Issue Register, but they serve distinct purposes: RFCs seek authorized changes, whereas Off-specs report non-compliance with agreed baselines.

A Request for Change is a proposed change to a product that has been defined and possibly baselined. An Off-specification is something that is missing from a product or does not meet specifications. Both are types of issue, but the key difference is that a RFC is a change to the specification, while an Off-spec is a failure to meet it.

The Project Plan is the high-level plan covering the entire project.

The Project Manager is responsible for maintaining the Business Case on a day-to-day basis, while the Executive owns it and approves changes.

The purpose is to enable the Project Board to review the current stage's performance and approve the next stage plan.

The Project Manager maintains the Business Case under the direction of the Executive. The Executive owns it, but the PM does the updates.

The Project Manager is responsible for maintaining the risk register as part of the 'Manage Risk' practice. This includes ensuring that risks are recorded, updated, and reviewed throughout the project, and that the register reflects the current risk status. The Project Manager does not own individual risks but manages the register as a key project document.

The 'Plan' step is where risk responses are developed and selected. The 'Assess' step evaluates probability and impact, but the decision on how to respond is part of planning.

The Project Manager is delegated by the Project Board to manage the project on a day-to-day basis within agreed tolerances.

In PRINCE2, quality is defined as 'fit for purpose,' meaning the product meets the stated requirements and is suitable for its intended use. This definition emphasizes that quality is about satisfying the agreed-upon specifications and user needs, not about achieving an abstract standard like zero defects or ISO compliance.

The Purpose of the product is a mandatory element in a PRINCE2 Product Description. It defines why the product is needed and how it contributes to the project's objectives, ensuring all stakeholders understand its role before development begins.

During Managing a Stage Boundary, the PM prepares the End Stage Report and next Stage Plan. The issue should be documented with a recommendation for the Project Board to decide.

The Business Case in PRINCE2 justifies the project's initiation and continued viability. It must include the expected benefits (tangible and intangible) that the project aims to deliver, as well as the major risks that could affect those benefits. Therefore, options C and D are correct components.

The Product Description includes quality criteria and is used to verify that the product meets requirements.

The PRINCE2 definition of a risk owner is the person who is responsible for managing all aspects of a specific risk, including monitoring the risk, implementing the planned response actions, and ensuring the risk is effectively controlled. This role is accountable for the risk throughout its lifecycle, not just for executing a single task.

When a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report. This is management by exception. The PM cannot increase the budget or continue without escalation.

When a Work Package tolerance is forecast to be exceeded, the Team Manager must escalate to the Project Manager via an Exception Report. The Project Manager can then negotiate corrective actions.

The Quality Management Approach defines how quality will be managed, including methods, responsibilities, and tools.

The Risk practice covers the systematic management of threats and opportunities.

The key output of the Initiating a Project process is the Project Initiation Documentation (PID). The PID consolidates all baseline information needed to justify proceeding with the project, including the Business Case, project scope, and management strategies. It serves as the foundation for decision-making by the Project Board and is formally approved before moving to the next stage.

According to PRINCE2, if a stage has exceeded its cost tolerance, the Project Board cannot authorize the next stage without first assessing the situation. The correct action is to request an Exception Plan, which details how to recover from the deviation and bring the project back within tolerance. This ensures the board has a revised forecast and recovery strategy before committing to further expenditure.

The Executive is accountable for the Business Case, appoints the Project Manager, and chairs the Project Board. Providing customer assurance is the Senior User's role; producing Highlight Reports is the Project Manager's role.

Avoid, reduce, and transfer are threat responses. Exploit and enhance are opportunity responses.

The Project Plan contains the project-level tolerances, including cost and time.

The Business Case in PRINCE2 is the key document that justifies the project's initiation and continued viability. It must include the expected benefits (B) to demonstrate the positive outcomes the project aims to achieve, and it must identify major risks (E) to provide a balanced view of the potential downsides and uncertainties. These two components are explicitly required by the PRINCE2 Business Case theme.