CCNA Prince2 Practices Questions

An RFC is a proposal for a change that would deliver something not originally specified. An Off-specification is something that should have been provided but was not, i.e., a failure to meet a requirement.

PRINCE2 defines tolerances for time, cost, scope, quality, risk, and benefits. Quality and risk are valid tolerances.

The Quality Review technique is used to assess the quality of a product and identify defects. It is a form of quality control.

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

A Product Description includes purpose, composition, derivation, format, quality criteria, quality method, and quality tolerance. Cost and benefits are not part of a Product Description; they are in the Business Case.

Option C is correct. Product Descriptions define the quality criteria, acceptance methods, and other details for each product. The Quality Management Approach defines the overall quality strategy.

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

PRINCE2 defines three types of issues: Request for Change, Off-specification, and Problem/Concern. Risk and change are not types of issues.

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

The risk owner is responsible for managing the risk and ensuring appropriate responses are implemented; the risk actionee is the person who carries out specific risk response actions.

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

Expected benefits and major risks are key components of a Business Case in PRINCE2.

An RFC is a proposal for a modification to a product that has been baselined, while an Off-specification is a product that should be produced but is not meeting specifications.

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 D are correct. The recommended risk management procedure steps are: Identify, Assess, Plan, Implement, Communicate. 'Assess' includes both probability and impact evaluation. 'Implement' involves executing the planned responses. 'Monitor' and 'Control' are not separate steps; they are part of Implement and Communicate.

Product-based planning follows: write Project Product Description, create Product Breakdown Structure, create Product Flow Diagram, then produce Product Descriptions for each product.

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.

Threat response strategies include Avoid, Reduce (Mitigate), Fallback, Transfer, Accept, and Share. Exploit is an opportunity response, not a threat response.

Option C is correct. 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 (A), continue without escalation (B), or close the project without Board decision (D).

The Project Board is responsible for providing overall direction, approving plans, and ensuring assurance. Producing Highlight Reports is the PM's responsibility; managing risks on a daily basis is the PM's role.

A Request for Change is a proposal for a modification to a product that has been baselined, while an Off-specification is something that should be provided but is not (or is forecast not to be). The key difference is that RFC is about changing what was agreed, whereas Off-spec is about failing to deliver what was agreed.

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.

A Request for Change is a proposal for a change, while an Off-specification is something that should be there but isn't.

PRINCE2 defines three issue types: Request for Change, Off-specification, and Problem/Concern. Options A, B, and D are correct. Options C and E are not issue types.

The PID includes the Business Case, Project Plan, and Risk Register. The Lessons Log is separate; the Work Package is created later.

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 and costs (investment appraisal). Options A and B are correct. Options C, D, and E are not standard components.

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.

Management by Exception is the principle of delegating authority within tolerances and escalating deviations.

Project Assurance is performed by individuals independent of the Project Manager, typically from the Project Board roles.

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

A Request for Change proposes a modification to an agreed baseline; an Off-specification is something that should be there but is not, or is wrong.

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.

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

A Product Description includes purpose, composition, and quality criteria, among others.

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 includes reasons, options, expected benefits, dis-benefits, timescale, costs, investment appraisal, and major risks. Expected benefits and major risks are correct.

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

The risk owner is responsible for managing the risk and implementing responses. The risk actionee carries out specific actions. The owner may delegate tasks but retains overall accountability.

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 Project Initiation Documentation (PID) is the key output of the Initiating a Project process. It forms the basis for management decision-making.

If a stage is within its tolerances, the Project Board authorizes the next stage. If tolerance is exceeded, an Exception Plan should be requested or the project may be closed.

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.

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

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

Expected benefits and major risks are key components of the Business Case. Options B and D are correct.

The Senior User specifies user needs, ensures the solution meets them, and is responsible for realizing benefits. The Senior User does not own the Business Case (Executive does) and does not manage risks day-to-day (Project Manager does).

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

Highlight Reports and End Stage Reports are produced by the Project Manager for the Project Board. Checkpoint Reports are for Team Managers; the End Project Report is produced at the end.

The Benefits Review Plan is created during the Initiating a Project process.

PRINCE2 separates the management and assurance functions to maintain objectivity.

PRINCE2 lists avoid, reduce, fallback, transfer, accept, and share as threat responses. Exploit is an opportunity response.

The Team Manager provides Checkpoint Reports at regular intervals. The Project Manager uses these to compile Highlight Reports for the Project Board.