Courseiva

CCNA Principles Questions

31 questions · Principles topic · All types, answers revealed

Practice these questionsExam hubAll questions
1
Multi-Selecthard

A project is in the 'Managing a Stage Boundary' process. The Project Manager is preparing the End Stage Report and the next Stage Plan. The project board has requested assurance that the project remains aligned with the PRINCE2 principle 'Focus on products'. Which TWO actions should the Project Manager take to demonstrate this principle? (Choose two.)

Select 2 answers
A.Ensure that the stage plan includes activities for risk management and issue resolution.
B.Update the product breakdown structure to reflect any changes in the products required for the next stage.
C.Verify that the project's organization structure includes a senior supplier who can approve product designs.
D.Review the product descriptions to ensure that quality criteria and quality methods are still valid for the next stage.
E.Confirm that the project board has approved the business case for the next stage.
AnswersB, D

Updating the product breakdown structure ensures that the project's products are clearly defined and agreed upon, which is central to the principle 'Focus on products'. By reflecting changes, the Project Manager ensures that the next stage plan is based on a current and accurate understanding of the required products, thereby aligning with the principle.

Why this answer

The principle 'Focus on products' requires that projects are defined and driven by the delivery of products that meet agreed quality criteria. At a stage boundary, the Project Manager should ensure that the product breakdown structure is updated and that product descriptions are reviewed to confirm their quality criteria and methods. These actions ensure that the next stage plan is product-centric and that the project remains aligned with the principle.

Exam trap

The trap here is to confuse the principle 'Focus on products' with other principles such as 'Continued business justification' or 'Defined roles and responsibilities', leading to the selection of actions that do not directly relate to product definition and quality.

Practice this question →
2
MCQmedium

During a project audit, it is discovered that team members are unsure who has the authority to approve design changes because the Project Management Team structure was never formally documented. Which PRINCE2 principle has been violated?

A.Defined roles and responsibilities
B.Focus on products
C.Tailor to suit the project
D.Manage by exception
AnswerA

Undocumented authority stems from failing to define who is accountable for what, which is precisely what the defined roles and responsibilities principle requires. It mandates that every member of the Project Management Team has a documented role, so approval authority for design changes is unambiguous rather than assumed.

Why this answer

The scenario states that the Project Management Team structure was never formally documented, leaving team members unsure who can approve design changes. PRINCE2's 'Defined roles and responsibilities' principle requires that the project management team structure be established, documented, and communicated, with clear accountabilities and delegated authority. The absence of this documentation is a direct violation of that principle.

Exam trap

PRINCE2-Practitioner often tests the overlap between 'Defined roles and responsibilities' and 'Manage by exception' — candidates may pick the latter because approval authority is mentioned, missing that the root failure is the undocumented structure.

How to eliminate wrong answers

Option B is wrong because 'Focus on products' concerns defining and delivering products to agreed quality criteria, not the governance structure or approval authority. Option C is wrong because 'Tailor to suit the project' is about adapting PRINCE2 to the project's environment, not about documenting who approves changes. Option D is wrong because 'Manage by exception' is about delegating authority within tolerances — while related, the failure here is the absence of any defined structure, not a failure to set tolerances.

Practice this question →
3
Multi-Selecthard

Which THREE of the following factors should be considered when applying the PRINCE2 principle 'Tailor to suit the project'?

Select 3 answers
A.The requirement to alter mandatory PRINCE2 principles to suit executive convenience.
B.The risk profile and geographical dispersion of the project team.
C.The personal preferences and favorite management frameworks of individual team members.
D.The scale, complexity, and importance of the project.
E.The organizational culture, environment, and existing corporate governance standards.
AnswersB, D, E

Tailoring must reflect the project's risk profile and team dispersion, since these determine how much formality, control and communication structure the method needs. Higher risk or geographically spread teams require adapted governance, satisfying the stem's requirement to consider these factors when tailoring.

Why this answer

Option B is correct because tailoring must reflect the project's risk profile and the geographical dispersion of the team, which directly affect how processes, roles, and communication are adapted. Option D is correct because the scale, complexity, and importance of the project determine the appropriate level of formality, documentation, and control applied to PRINCE2. Option E is correct because tailoring must align with the organization's culture, environment, and existing corporate governance standards so PRINCE2 integrates with, rather than conflicts with, established practices.

Option A is wrong because PRINCE2 principles are mandatory and cannot be altered or omitted to suit executive convenience; only the processes, themes, and terminology are tailored. Option C is wrong because tailoring is driven by project and organizational factors, not by individual team members' personal preferences or favorite management frameworks.

Exam trap

PRINCE2-Practitioner often tests the misconception that tailoring allows you to change or skip principles — candidates pick options about altering principles or following personal preferences, but the exam expects you to know that principles are mandatory and tailoring is driven by project and organizational factors.

Practice this question →
4
MCQeasy

Before closing a project, the Project Manager compiles a report detailing what went well and what went poorly, storing it in the corporate repository for future project managers to access. Which PRINCE2 principle is this fulfilling?

A.Continued business justification
B.Tailor to suit the project
C.Learn from experience
D.Focus on products
AnswerC

Capturing lessons on what went well and poorly, then storing them in the corporate repository, ensures future projects benefit from this experience. That directly fulfils the Learn from experience principle, which requires lessons to be recorded and shared throughout and after the project.

Why this answer

The scenario describes compiling a report on what went well and what went poorly and storing it for future project managers. This directly fulfills the 'Learn from experience' principle, which requires PRINCE2 projects to learn from previous projects and to capture lessons for future ones. The other principles do not specifically address this activity.

Exam trap

PRINCE2-PRACTITIONER often tests the principles by presenting scenarios that sound like one principle but actually map to another; candidates may confuse 'Learn from experience' with 'Continued business justification' when the scenario involves post-project review.

How to eliminate wrong answers

Option A is wrong because 'Continued business justification' ensures the project remains viable, not capturing lessons. Option B is wrong because 'Tailor to suit the project' involves adapting PRINCE2 to the project's environment, not storing lessons. Option D is wrong because 'Focus on products' emphasizes defining and delivering products, not learning from experience.

Practice this question →
5
MCQmedium

A Project Board delegates day-to-day control of a project stage to the Project Manager, stepping in only when agreed limits for cost and time are forecast to be exceeded. Which PRINCE2 principle does this governance model represent?

A.Defined roles and responsibilities
B.Tailor to suit the project
C.Manage by exception
D.Manage by stages
AnswerC

Manage by exception defines tolerances for cost and time, within which the Project Manager runs the stage without Board intervention; escalation occurs only when a forecast breach is imminent. This matches the stem's delegated day-to-day control with agreed limits, satisfying the principle's requirement for pre-defined boundaries and defined escalation points.

Why this answer

The scenario describes the Project Board delegating day-to-day control to the Project Manager and only intervening when agreed tolerances for cost and time are forecast to be exceeded. This is the definition of the 'Manage by exception' principle, which establishes tolerances and defines escalation procedures when those tolerances are threatened. The Board's role is to manage by exception, focusing on strategic decisions and only stepping in when exceptions occur.

Exam trap

PRINCE2-PRACTITIONER often tests the difference between 'Manage by exception' and 'Manage by stages' — candidates may focus on the stage aspect, but the key is the delegation within tolerances and escalation only when exceeded.

How to eliminate wrong answers

Option A is wrong because 'Defined roles and responsibilities' is about clearly defining who does what in the project, not about the delegation and tolerance mechanism. Option B is wrong because 'Tailor to suit the project' is about adapting PRINCE2 to the project's size, complexity, and environment, not about governance by exception. Option D is wrong because 'Manage by stages' is about dividing the project into stages for control and planning, not about the delegation of authority within tolerances.

Practice this question →
6
MCQhard

A company is utilizing an agile delivery method alongside PRINCE2. The Project Manager integrates sprint reviews to ensure stakeholder engagement and product validation at the end of each short iteration. Which PRINCE2 principle is primarily reinforced by this integration?

A.Manage by exception
B.Continued business justification
C.Learn from experience
D.Tailor to suit the project
AnswerD

Tailoring is the principle of adapting PRINCE2 to the project's context. Blending agile sprint reviews into the delivery approach modifies the method to fit an agile environment, satisfying the stem's requirement to integrate short iterations while retaining PRINCE2 governance and stakeholder validation.

Why this answer

'Tailor to suit the project' requires PRINCE2 to be adapted to the project's size, complexity, environment, and delivery approach. Integrating agile sprint reviews into a PRINCE2 project is a classic tailoring decision that combines PRINCE2 governance with agile delivery cadence. The principle explicitly supports using alternative delivery methods while retaining PRINCE2's governance framework.

Exam trap

The trap here is confusing 'tailor to suit the project' with 'learn from experience' — candidates see iterative reviews and assume lessons-learned is the driving principle, missing that the integration of an agile method is fundamentally a tailoring decision.

How to eliminate wrong answers

Option A is wrong because 'manage by exception' concerns tolerance-based delegation and escalation, not the integration of agile ceremonies. Option B is wrong because 'continued business justification' concerns whether the project remains viable, which is not what sprint reviews primarily reinforce. Option C is wrong because 'learn from experience' concerns capturing and applying lessons, which is a by-product of sprint reviews but not the primary principle being applied when integrating an agile method.

Practice this question →
7
MCQeasy

A Project Manager is leading a project to develop a new mobile application. The project board has defined tolerances for time, cost, and scope. During a stage, the Project Manager discovers that the actual cost is forecast to exceed the stage cost tolerance by 10%. According to the PRINCE2 principle 'Manage by exception', what should the Project Manager do?

A.Request additional funds from the finance department without involving the project board.
B.Take corrective action to bring the cost back within tolerance and continue without informing the project board.
C.Immediately escalate the issue to the project board by producing an Exception Report.
D.Do nothing until the end of the stage, then report the overspend in the End Stage Report.
AnswerC

This is correct because the principle 'Manage by exception' requires that the Project Manager only escalates to the project board when a tolerance is forecast to be exceeded. Since the cost forecast exceeds the stage tolerance, the Project Manager must raise an Exception Report to inform the project board and seek a decision on how to proceed.

Why this answer

The principle 'Manage by exception' establishes that the Project Manager has delegated authority to manage within agreed tolerances and must escalate to the project board only when a tolerance is forecast to be exceeded. In this scenario, the cost forecast exceeds the stage tolerance, so the Project Manager must produce an Exception Report and escalate to the board for a decision.

Exam trap

The trap here is to assume that the Project Manager should try to resolve the overspend independently, when the principle 'Manage by exception' requires escalation as soon as a tolerance breach is forecast.

Practice this question →
8
MCQhard

A PRINCE2 project is being tailored for a small internal IT upgrade. The Project Manager proposes that the project board will consist of only the Project Manager and the Team Manager, and that the project will be managed as a single stage. Which principle is being compromised?

A.Tailor to suit the project environment
B.Manage by exception
C.Manage by stages
D.Defined roles and responsibilities
AnswerD

This is correct because the principle 'Defined roles and responsibilities' requires that the project has a clear organizational structure with defined roles, including a project board with business, user, and supplier representation. The proposed structure lacks these three primary stakeholder interests, compromising the principle.

Why this answer

The PRINCE2 principle 'Defined roles and responsibilities' requires that projects have a clear organizational structure with defined roles, including a project board that represents the business, user, and supplier interests. The proposed structure of only the Project Manager and Team Manager lacks these three stakeholder perspectives, which compromises the principle. While tailoring is allowed, it must not violate the principles.

Exam trap

The trap here is to focus on the single stage aspect and select 'Manage by stages', but the more fundamental violation is the lack of a properly constituted project board, which relates to defined roles and responsibilities.

Practice this question →
9
MCQmedium

A multi-national corporation is rolling out PRINCE2 across various departments. They adjust the standard management reports and terminology to align with existing corporate governance frameworks without losing core controls. Which PRINCE2 principle is being applied?

A.Defined roles and responsibilities
B.Manage by exception
C.Tailor to suit the project
D.Learn from experience
AnswerC

Tailor to suit the project means adapting PRINCE2's processes, themes, terminology and reports to the organisation's scale, governance and environment while retaining the principles. Aligning reports with corporate governance frameworks without losing core controls is exactly this tailoring.

Why this answer

The principle being applied is 'Tailor to suit the project' because the corporation is adjusting PRINCE2 reports and terminology to align with existing corporate governance frameworks while maintaining core controls. Tailoring ensures that PRINCE2 is adapted to the project's environment, size, complexity, and organizational standards without compromising its principles.

Exam trap

PRINCE2-Practitioner often tests the misconception that tailoring means ignoring PRINCE2 principles or that any adaptation is acceptable; the trap is confusing tailoring with abandoning core controls.

How to eliminate wrong answers

Option A is wrong because 'Defined roles and responsibilities' focuses on establishing clear roles, not on adapting reports and terminology. Option B is wrong because 'Manage by exception' is about setting tolerances and delegating authority, not about customizing documentation. Option D is wrong because 'Learn from experience' involves capturing and using lessons, not modifying governance frameworks.

Practice this question →
10
MCQmedium

A project is running behind schedule due to unexpected regulatory sign-offs. The Project Manager identifies that the delay will consume the time tolerance agreed with the Project Board, but it will not exceed it. What should the Project Manager do, based on PRINCE2 principles?

A.Continue executing the stage plan since the forecast remains within agreed time tolerances.
B.Escalate immediately with an Exception Report because any delay is unacceptable.
C.Suspend the project immediately to re-verify the business justification.
D.Rewrite the Project Brief to adjust the quality expectations of the outputs.
AnswerA

Tolerance is delegated authority, so a forecast delay that stays within the agreed time tolerance requires no exception report or Board escalation. The Project Manager continues executing the stage plan, taking corrective action internally, satisfying the principle that management by exception operates within tolerances.

Why this answer

In PRINCE2, tolerances define the permissible deviation from planned targets before escalation is required. Since the forecast delay will consume but not exceed the agreed time tolerance, the Project Manager retains the authority to manage the stage within those limits. The correct action is to continue executing the stage plan, monitoring the situation closely, and only escalate if the tolerance is forecast to be exceeded.

This aligns with the 'Manage by Exception' principle, which empowers the Project Manager to take corrective action within delegated tolerances without unnecessary escalation.

Exam trap

PRINCE2-Practitioner often tests the misconception that any deviation from plan requires immediate escalation, confusing tolerance with zero tolerance, and overlooking the 'Manage by Exception' principle that empowers the Project Manager to act within agreed tolerances.

How to eliminate wrong answers

Option B is wrong because escalation via an Exception Report is only required when a tolerance is forecast to be exceeded, not merely when a delay occurs; PRINCE2 does not treat any delay as automatically unacceptable. Option C is wrong because suspending the project is a drastic action reserved for situations where the business justification is no longer valid or when instructed by the Project Board; a delay within tolerance does not warrant suspension. Option D is wrong because the Project Brief is a pre-project document that should not be rewritten during execution, and adjusting quality expectations is not a valid response to a time delay within tolerance; quality expectations are defined in the Project Product Description and should only be changed through formal change control.

Practice this question →
11
MCQeasy

In a large infrastructure project, the Project Board includes a representative from the user community, a representative of senior supplier interests, and an Executive representing business interests. Which PRINCE2 principle is being implemented?

A.Defined roles and responsibilities
B.Tailor to suit the project
C.Manage by exception
D.Continued business justification
AnswerA

The Project Board's three stakeholder perspectives — business, user and supplier — map directly onto PRINCE2's defined roles and responsibilities principle, which requires each stakeholder interest to be represented in the project management team structure.

Why this answer

The scenario describes the three primary Project Board interests — Business (Executive), User, and Supplier — each formally represented with defined accountabilities. This is the direct embodiment of the 'Defined roles and responsibilities' principle, which requires that the project management team structure be established with clear roles, and that the three primary stakeholder interests be represented on the Board. The presence of all three interests is the textbook signal for this principle.

Exam trap

The trap here is confusing 'Defined roles and responsibilities' (who is on the team and what they are accountable for) with 'Tailor to suit the project' (adapting the method) — candidates see 'large infrastructure project' and wrongly reach for tailoring.

How to eliminate wrong answers

Option B is wrong because 'Tailor to suit the project' concerns adapting PRINCE2's processes, themes, and products to the project's size, risk, and environment — it is not about who sits on the Board. Option C is wrong because 'Manage by exception' is about delegating authority with defined tolerances so the Board only intervenes when thresholds are breached, not about the composition of the Board. Option D is wrong because 'Continued business justification' is about ensuring there is a valid Business Case throughout the project, not about stakeholder representation on the governance body.

Practice this question →
12
MCQhard

A project manager is working in an environment where senior management demands rigid adherence to a strict, unmodified, multi-year PRINCE2 methodology, despite the project being a small, two-week internal event. Which PRINCE2 principle is being violated by management's approach?

A.Learn from experience
B.Tailor to suit the project
C.Focus on products
D.Manage by exception
AnswerB

PRINCE2 must be scaled to the project's size, complexity, and risk. Applying an unmodified multi-year methodology to a two-week internal event ignores that requirement, violating the Tailor to suit the project environment principle, which demands adaptation rather than rigid adherence.

Why this answer

The PRINCE2 principle 'Tailor to suit the project' requires that the method be adapted to the project's size, complexity, importance, capability, and risk. A rigid, unmodified multi-year methodology applied to a two-week internal event is a textbook violation because the project's scale does not justify the full PRINCE2 framework. Tailoring ensures that PRINCE2 remains fit for purpose rather than becoming bureaucratic overhead.

Exam trap

PRINCE2-Practitioner often tests the misconception that PRINCE2 must be applied rigidly in all projects, confusing tailoring with abandoning the method, when in fact tailoring is a mandatory principle that requires adapting the method to the project's context.

How to eliminate wrong answers

Option A is wrong because 'Learn from experience' concerns capturing and applying lessons from previous projects, which is not the issue here—the problem is the inappropriate application of the method, not a failure to learn. Option C is wrong because 'Focus on products' is about defining and delivering products that meet quality criteria, and nothing in the scenario suggests that product definition is being neglected. Option D is wrong because 'Manage by exception' relates to delegating authority within defined tolerances, and the scenario describes rigid control, not a lack of exception management.

Practice this question →
13
Multi-Selectmedium

Which THREE of the following statements correctly describe how the PRINCE2 principle 'Manage by stages' is applied?

Select 3 answers
A.Breaking a project into stages allows risks to be reviewed and managed more effectively over time.
B.Management stages are identical to technical stages such as design, build, and test.
C.Management stages provide the Project Board with key decision-making points to authorize continuation.
D.Detailed planning is done for the current stage, while higher-level planning is maintained for later stages.
E.Projects must always have exactly three management stages regardless of their size.
AnswersA, C, D

Manage by stages divides the project into manageable chunks, each with its own plan, tolerances and end-of-stage assessment. This lets the Project Board review risks, business justification and progress at defined points, adjusting direction before committing further resources.

Why this answer

Option A is correct because dividing a project into management stages creates regular review points at which risks can be reassessed and managed as the project progresses, which is a core benefit of the 'Manage by stages' principle. Option C is correct because each management stage ends at a decision point where the Project Board reviews progress and business justification and authorizes (or refuses) continuation to the next stage. Option D is correct because PRINCE2 applies the 'manage by exception' and staged-planning approach: the current stage is planned in detail while later stages are only planned at a higher level until they are reached.

Option B is incorrect because management stages are governance/decision boundaries and are not the same as technical stages (such as design, build, and test), which relate to specialist work and may span or sit within management stages. Option E is incorrect because the number of management stages is not fixed at three; it depends on the size, complexity, and risk of the project and is determined during initiation.

Exam trap

PRINCE2-Practitioner often tests the confusion between management stages (governance decision points owned by the Project Board) and technical stages (specialist delivery phases), and the false belief that PRINCE2 prescribes a fixed number of stages.

Practice this question →
14
MCQeasy

A project is underway to develop a new logistics system. During execution, a major industry regulation changes, rendering the current business case unviable. Which PRINCE2 principle is primarily being applied when the Project Board recommends stopping the project?

A.Continued business justification
B.Focus on products
C.Tailor to suit the project
D.Manage by exception
AnswerA

Continued business justification requires the project to remain viable and aligned with a valid Business Case throughout. When the regulation change invalidates that justification, the Project Board is obliged to stop or re-scope, so the principle directly drives the recommendation to halt.

Why this answer

The Continued business justification principle states that a PRINCE2 project must have a valid Business Case at all times, and if it ceases to be viable the project should be stopped. When a regulatory change invalidates the business case, the Project Board's recommendation to stop the project is the direct application of this principle — it is the 'stop' half of 'continue or stop' decision-making. This is why the Business Case is reviewed at every stage boundary and exception.

Exam trap

PRINCE2-Practitioner often tests the confusion between Continued business justification (should we still do this?) and Manage by exception (escalate when tolerances are breached) — candidates pick Manage by exception because a 'major change' sounds like an exception, but the trigger here is viability, not tolerance breach.

How to eliminate wrong answers

Option B is wrong because Focus on products is about defining outputs and their quality criteria, not about evaluating whether the project should continue. Option C is wrong because Tailor to suit the project concerns adapting PRINCE2 methods to project size, complexity, and environment, not terminating a project. Option D is wrong because Manage by exception is about delegating tolerance and escalating only when tolerances are forecast to be breached — it is a control mechanism, not the principle that mandates stopping when justification fails.

Practice this question →
15
Multi-Selecthard

Which THREE of the following statements correctly characterize the application of the PRINCE2 principle 'Focus on products'?

Select 3 answers
A.A project's outputs and their quality requirements must be defined and agreed upon before work begins.
B.Deliverables must satisfy acceptance criteria before being formally signed off by the customer.
C.Product Descriptions are essential management products used to define each output's quality and criteria.
D.Focus on products means ignoring project schedules and focusing solely on deliverables.
E.The Project Manager is responsible for independently writing all Product Descriptions without consulting stakeholders.
AnswersA, B, C

Focus on products requires defining and agreeing outputs and their quality requirements before work commences, ensuring effort is directed at delivering specified products rather than activity for its own sake. This matches the principle's emphasis on agreed product definition.

Why this answer

Option A is correct because the 'Focus on products' principle requires that a project's outputs and their quality requirements be clearly defined and agreed upon before work begins, ensuring a shared understanding of what will be delivered. Option B is correct because deliverables must satisfy their defined acceptance criteria before being formally signed off by the customer, which is the mechanism by which the principle ensures fitness for purpose. Option C is correct because Product Descriptions are essential management products in PRINCE2 that define each output's purpose, composition, quality criteria, and quality method, directly supporting the 'Focus on products' principle.

Option D is incorrect because focusing on products does not mean ignoring schedules; PRINCE2 integrates product definition with plans and timescales, so schedules remain essential. Option E is incorrect because Product Descriptions are typically developed collaboratively with stakeholders and those with relevant expertise, not independently by the Project Manager alone.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that 'Focus on products' means ignoring schedules or that the Project Manager alone writes Product Descriptions, but the exam expects recognition of collaborative definition and quality criteria.

Practice this question →
16
MCQhard

An organization is executing a tiny internal improvement project that will last only two weeks and involve two people. The Project Manager suggests scaling down the standard PRINCE2 management products, governance boards, and reporting structures to match the scale. Which principle supports this decision?

A.Manage by exception
B.Tailor to suit the project
C.Focus on products
D.Manage by stages
AnswerB

Tailor to suit the project requires scaling PRINCE2's management products, governance and reporting to the project's size, complexity and risk. For a two-week, two-person project, this principle justifies the reduced documentation and lighter boards described.

Why this answer

'Tailor to suit the project' is the PRINCE2 principle that explicitly requires the method to be adapted to the project's size, complexity, risk, and environment. Scaling down management products, governance boards, and reporting for a two-week, two-person project is the textbook application of this principle. PRINCE2 is designed to be tailored, not applied rigidly.

Exam trap

PRINCE2-Practitioner often tests the difference between 'Tailor to suit the project' (adapting the method) and 'Manage by exception' (delegating authority) — candidates see 'scaling down' and may wrongly pick the latter.

How to eliminate wrong answers

Option A is wrong because 'Manage by exception' concerns delegating authority with tolerances so the Board only intervenes when thresholds are breached — it does not address scaling the method itself. Option C is wrong because 'Focus on products' is about defining and delivering products to agreed quality criteria, not about adapting governance artefacts. Option D is wrong because 'Manage by stages' is about dividing the project into governance stages with decision points, not about scaling documentation and boards.

Practice this question →
17
Multi-Selectmedium

Which TWO of the following statements correctly describe the application of the PRINCE2 principle 'Continued business justification'?

Select 2 answers
A.If the business justification for a project ceases, the project should be stopped.
B.Project managers are solely responsible for writing and owning the Business Case.
C.Business justification is only required during project initiation and final closure.
D.Business justification metrics must be strictly financial and cannot include qualitative benefits.
E.The business case must remain valid throughout the entire lifecycle of the project.
AnswersA, E

A project lacking valid business justification must be discontinued, satisfying the principle's requirement that justification remains valid throughout. PRINCE2 mandates that if the Business Case no longer demonstrates viable justification, the project board should stop the project rather than continue investing, ensuring resources are not wasted on unjustified work.

Why this answer

Option A is correct because the PRINCE2 principle 'Continued business justification' mandates that a project must have a justifiable reason to continue; if the Business Case no longer demonstrates viable justification (e.g., benefits no longer outweigh costs and risks), the project should be stopped rather than continued by inertia. Option E is correct because this principle requires the Business Case to be reviewed and revalidated at every stage boundary and whenever significant changes occur, ensuring justification remains valid throughout the entire project lifecycle, not just at initiation. Option B is incorrect because the Business Case is owned by the Executive (senior responsible owner), while the Project Manager typically writes and maintains it on the Executive's behalf.

Option C is incorrect because business justification must be continuously reviewed at stage boundaries and exception situations, not only at initiation and closure. Option D is incorrect because PRINCE2 explicitly allows both financial and non-financial/qualitative benefits (e.g., compliance, reputation, social value) to justify a project.

Exam trap

PRINCE2-Practitioner often tests the misconception that the Project Manager owns the Business Case and that justification is only checked at initiation and closure, when in fact the Executive owns it and it is re-validated at every stage boundary.

Practice this question →
18
MCQmedium

A project is using PRINCE2 to deliver a new healthcare information system. The Project Manager is reviewing the project's progress and notices that the project's business case has not been updated since the project was initiated six months ago. During this time, the regulatory environment has changed, and the expected benefits are now less certain. Which PRINCE2 principle is being violated?

A.Learn from experience
B.Manage by stages
C.Continued business justification
D.Focus on products
AnswerC

This is correct because the principle 'Continued business justification' requires that the business case is reviewed and updated throughout the project to ensure that the project remains viable and aligned with the business objectives. Failing to update the business case despite significant changes in the regulatory environment violates this principle.

Why this answer

The principle 'Continued business justification' mandates that a project must have a justified business case that is reviewed and updated throughout the project lifecycle. In this scenario, the business case has not been updated despite significant regulatory changes that affect the expected benefits, which means the project may no longer be justified. This is a clear violation of the principle.

Exam trap

The trap here is to focus on the review aspect and attribute it to 'Manage by stages', but the specific violation is the lack of ongoing justification, which is the domain of 'Continued business justification'.

Practice this question →
19
Multi-Selectmedium

Which THREE of the following principles are among the seven core principles of PRINCE2?

Select 3 answers
A.Learn from experience
B.Continuous risk elimination
C.Tailor to suit the project
D.Focus on products
E.Manage by consensus
AnswersA, C, D

Learn from experience is one of the seven PRINCE2 principles, requiring lessons to be sought, recorded and acted upon throughout the project rather than only at closure. This satisfies the principle-selection constraint by naming a genuine core principle that governs continual improvement.

Why this answer

Option A (Learn from experience) is correct because PRINCE2's seven principles explicitly include 'Learn from experience,' requiring the project team to capture and apply lessons throughout the project, not just at closure. Option C (Tailor to suit the project) is correct because 'Tailor to suit the project environment' is a core PRINCE2 principle, ensuring the method's processes, themes, and documentation are scaled appropriately to the project's size, complexity, and risk. Option D (Focus on products) is correct because 'Focus on products' is a PRINCE2 principle that directs the project to define and deliver products meeting agreed quality criteria, using product descriptions and the product breakdown structure.

Option B (Continuous risk elimination) is not a PRINCE2 principle; PRINCE2 addresses risk through the Risk theme and 'Manage by exception,' and it does not aim to eliminate all risk. Option E (Manage by consensus) is not a PRINCE2 principle; PRINCE2 uses 'Manage by exception' with defined tolerances and a single accountable Project Board, rather than consensus-based decision-making.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between the seven principles, seven themes, and seven processes — candidates pick plausible-sounding but non-existent principles like 'continuous risk elimination' or 'manage by consensus'.

Practice this question →
20
MCQhard

An organization is executing a software development project where user requirements change rapidly. The Project Manager ensures that every delivered software increment has a clear Product Description outlining its acceptance criteria before development starts. Which PRINCE2 principle is being rigorously applied?

A.Continued business justification
B.Manage by stages
C.Focus on products
D.Tailor to suit the project
AnswerC

Focus on products requires defining each product's purpose, composition and quality criteria, here via Product Descriptions with acceptance criteria, before work begins. This satisfies the stem's constraint of rapidly changing requirements by basing development on agreed product definitions rather than shifting specifications.

Why this answer

'Focus on products' requires that projects define and deliver products against agreed Product Descriptions, which specify purpose, composition, quality criteria, and acceptance criteria. The scenario explicitly states that every delivered increment has a clear Product Description with acceptance criteria before development starts — this is the direct application of the principle.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between 'focus on products' and 'manage by stages' — candidates see 'increments' and 'delivery' and wrongly pick manage by stages, missing that the defining feature of the scenario is the Product Description and acceptance criteria.

How to eliminate wrong answers

Option A is wrong because 'continued business justification' concerns whether the project remains viable and aligned with the Business Case, not the definition of product acceptance criteria. Option B is wrong because 'manage by stages' concerns dividing the project into authorised increments, not the product definition itself. Option D is wrong because 'tailor to suit the project' concerns adapting PRINCE2 to the project context, not the rigorous definition of product acceptance criteria.

Practice this question →
21
MCQeasy

A project is initiated to build a new corporate headquarters. During project preparation, the executive team establishes that the project must deliver a positive return on investment within three years. Which PRINCE2 principle underpins this requirement?

A.Manage by stages
B.Continued business justification
C.Defined roles and responsibilities
D.Focus on products
AnswerB

Continued business justification requires a justifiable reason to start and continue the project, expressed through the business case. The three-year positive return on investment is that justification, so this principle underpins the executive's requirement and mandates ongoing viability review.

Why this answer

The requirement that the project must deliver a positive return on investment within three years is a statement of business justification — the 'why' behind the project. The PRINCE2 principle 'Continued business justification' requires that a project has a justifiable business case at initiation and that this justification is reviewed and remains valid throughout the project lifecycle. ROI is a core component of the Business Case, so this principle directly underpins the requirement.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between principles that sound similar — candidates may confuse 'Continued business justification' with 'Manage by exception' when financial thresholds are mentioned, but ROI is fundamentally about the Business Case, not tolerance delegation.

How to eliminate wrong answers

Option A is wrong because 'Manage by stages' is about dividing the project into manageable stages with decision points, not about financial justification. Option C is wrong because 'Defined roles and responsibilities' concerns the organizational structure and accountability (e.g., Executive, Senior User, Senior Supplier), not ROI. Option D is wrong because 'Focus on products' is about defining and delivering products that meet quality criteria, not about the financial rationale for the project.

Practice this question →
22
MCQhard

An R&D project has high uncertainty regarding whether the final technology can be successfully developed. To mitigate risk, the Project Manager recommends dividing the project into very short, high-frequency stages with explicit go/no-go decision gates. Which PRINCE2 principle is being leveraged most directly to control this uncertainty?

A.Manage by exception
B.Manage by stages
C.Continued business justification
D.Tailor to suit the project
AnswerB

Manage by stages divides the work into discrete management stages, each authorised by the project board and closed before the next begins. Very short stages with go/no-go gates let the board stop funding if the technology proves unviable, directly controlling uncertainty.

Why this answer

Manage by stages is the principle that requires the project to be planned, monitored, and controlled on a stage-by-stage basis, with a Project Board decision (go/no-go) at each stage boundary. Dividing an uncertain R&D project into short, high-frequency stages with explicit decision gates is the textbook application of this principle to control uncertainty. It allows the project to be stopped or redirected at each boundary based on the latest viability assessment.

Exam trap

PRINCE2-Practitioner often tests the overlap between Manage by stages and Manage by exception — candidates pick Manage by exception because 'go/no-go decision gates' sound like escalation, but the principle that mandates staged control and decision boundaries is Manage by stages.

How to eliminate wrong answers

Option A is wrong because Manage by exception is about delegating tolerances and escalating only when forecasts breach them — it does not by itself create stage boundaries or go/no-go gates. Option C is wrong because Continued business justification is about whether the project remains viable, which is assessed at stage boundaries but is not the principle that prescribes the staged structure. Option D is wrong because Tailor to suit the project is about adapting the method to the project's context, not about the control mechanism of staged decision gates.

Practice this question →
23
MCQmedium

A Project Manager wants to ensure that all project team members understand their reporting lines, decision-making authorities, and stakeholder representation. Which PRINCE2 principle requires this clarity?

A.Manage by exception
B.Continued business justification
C.Tailor to suit the project
D.Defined roles and responsibilities
AnswerD

Defined roles and responsibilities requires every team member to have a clear, agreed role with defined reporting lines, decision-making authority and stakeholder representation. This directly satisfies the stem's demand for clarity on reporting lines, authorities and representation, making it the applicable PRINCE2 principle.

Why this answer

The 'defined roles and responsibilities' principle requires that every project has clearly defined roles, responsibilities, and reporting lines. This ensures that all stakeholders understand who does what, who decides what, and how they interact, which directly addresses the Project Manager's need for clarity on reporting lines and decision-making authorities.

Exam trap

PRINCE2-Practitioner often tests the seven principles by presenting scenarios that sound like they fit multiple principles, but the key is to identify the principle that most directly addresses the specific need described.

How to eliminate wrong answers

Option A is wrong because 'Manage by exception' is about setting tolerances and escalating only when they are forecast to be breached, not about defining roles. Option B is wrong because 'Continued business justification' focuses on ensuring the project remains viable and aligned with business objectives. Option C is wrong because 'Tailor to suit the project' is about adapting PRINCE2 to the project's size, complexity, and environment, not about role clarity.

Practice this question →
24
MCQeasy

A project team encounters a technical flaw in a deliverable. Instead of fixing it quietly, they log the flaw and review it against the Product Description to ensure the final output meets agreed expectations. Which PRINCE2 principle is being demonstrated?

A.Focus on products
B.Defined roles and responsibilities
C.Learn from experience
D.Manage by exception
AnswerA

Logging the flaw and checking it against the Product Description applies product-based planning: quality is defined by the product's agreed criteria, not by ad hoc fixes. This satisfies the stem's constraint that the final output must meet expectations, which is precisely what Focus on products demands.

Why this answer

The team is logging a technical flaw and reviewing it against the Product Description to ensure the final output meets agreed expectations, which demonstrates the 'Focus on products' principle. This principle requires defining and agreeing on product descriptions and quality criteria up front, then verifying deliverables against them. By checking the flaw against the Product Description, the team is ensuring the product meets its defined requirements.

Exam trap

PRINCE2-PRACTITIONER often tests the distinction between principles; the trap is confusing 'Focus on products' with 'Learn from experience' when the scenario involves reviewing a flaw against a Product Description.

How to eliminate wrong answers

Option B is wrong because 'Defined roles and responsibilities' concerns clear accountability structures, not product quality verification. Option C is wrong because 'Learn from experience' involves capturing lessons and improving, which is not the primary action described here. Option D is wrong because 'Manage by exception' is about tolerances and escalation, not about reviewing a flaw against a Product Description.

Practice this question →
25
Multi-Selecthard

Which TWO of the following practices are characteristic of the PRINCE2 principle 'Manage by exception'?

Select 2 answers
A.Tolerances are established for six aspects of project performance, including time and cost.
B.Project team members have the authority to alter project scope whenever they encounter delays.
C.Exception management means that no plans are needed for individual stages.
D.The Project Manager must immediately escalate via an Exception Report if stage tolerances are forecast to be breached.
E.The Project Board micro-manages the daily tasks of the team to ensure high quality.
AnswersA, D

Tolerances define the delegated limits for the six aspects of project performance — time, cost, scope, quality, risk and benefits — that allow the next management level to work within agreed boundaries without seeking approval, which is the mechanism enabling management by exception.

Why this answer

Option A is correct because 'Manage by exception' in PRINCE2 requires that tolerances be defined for the six aspects of project performance — time, cost, scope, quality, risk, and benefit — so that the Project Board delegates authority within agreed limits and only gets involved when those limits are forecast to be exceeded. Option D is correct because when the Project Manager forecasts that stage tolerances will be breached, the principle dictates escalation to the next management level (the Project Board) via an Exception Report, which triggers an Exception Plan or a decision to stop/redirect the project. Option B is wrong because team members cannot unilaterally alter scope; scope changes must go through the agreed change control and tolerances, not ad hoc authority.

Option C is wrong because exception management does not remove the need for stage plans — PRINCE2 still requires stage plans and work packages; exceptions only change how deviations are escalated. Option E is wrong because micro-management by the Project Board directly contradicts 'Manage by exception', which is designed to push decisions down to the appropriate level and keep senior management focused on exceptions.

Exam trap

PRINCE2-Practitioner often tests the misconception that 'manage by exception' means no planning or that it allows team members to make scope changes, when in fact it relies on pre-agreed tolerances and formal escalation.

Practice this question →
26
MCQmedium

A newly appointed Project Manager wants to ensure that all project outputs are clearly defined, agreed upon, and understood in terms of quality criteria before work begins. Which PRINCE2 principle should guide this effort?

A.Focus on products
B.Learn from experience
C.Defined roles and responsibilities
D.Continued business justification
AnswerA

Focus on products directs the team to define each output and its quality criteria before committing to activities. This satisfies the stem's constraint that outputs be clearly defined, agreed and understood prior to work starting, shifting emphasis from tasks to deliverable specifications.

Why this answer

Focus on products is the PRINCE2 principle that requires projects to be defined and driven by their products — the outputs — with clearly defined product descriptions and quality criteria agreed before work begins. Ensuring outputs are defined, agreed, and understood in terms of quality criteria is the direct application of this principle. It shifts the emphasis from 'doing activities' to 'delivering defined products.'

Exam trap

PRINCE2-Practitioner often tests the confusion between Focus on products (define outputs and quality criteria) and Defined roles and responsibilities (who does the work) — candidates pick the roles principle because the question mentions 'agreed,' but the trigger is product definition and quality criteria.

How to eliminate wrong answers

Option B is wrong because Learn from experience is about capturing and applying lessons throughout the project, not about defining products and quality criteria. Option C is wrong because Defined roles and responsibilities is about who does what in the project organization, not about product definition. Option D is wrong because Continued business justification is about the ongoing viability of the Business Case, not about specifying outputs and their quality criteria.

Practice this question →
27
MCQmedium

A Project Manager is reviewing lessons learned from a previous failed marketing campaign project within the same organization to improve the current project's initiation stage. Which PRINCE2 principle does this action directly demonstrate?

A.Defined roles and responsibilities
B.Learn from experience
C.Tailor to suit the project
D.Manage by stages
AnswerB

Reviewing lessons from a previous failed campaign to shape the current initiation stage directly applies the Learn from experience principle, which requires seeking and applying prior knowledge throughout. This satisfies the stem's constraint, since the lessons are being fed into initiation rather than merely recorded.

Why this answer

Reviewing lessons learned from a previous failed project to improve the current project's initiation stage directly demonstrates the 'learn from experience' principle. This principle requires that project teams learn from previous projects and external sources, and apply those lessons to improve current and future project performance.

Exam trap

PRINCE2-Practitioner often tests the distinction between principles, so candidates may confuse 'learn from experience' with 'tailor to suit the project' when the scenario involves adapting based on past projects.

How to eliminate wrong answers

Option A is wrong because 'defined roles and responsibilities' focuses on establishing clear roles within the project organization, not on using historical lessons. Option C is wrong because 'tailor to suit the project' involves adapting PRINCE2 to the project's size, complexity, and environment, not specifically learning from past projects. Option D is wrong because 'manage by stages' is about dividing the project into manageable stages for control, not about incorporating lessons learned.

Practice this question →
28
MCQeasy

A software development project is divided into distinct planning increments of three months each, at the end of which the Project Board reviews progress and decides whether to authorize the next increment. Which PRINCE2 principle is being applied?

A.Focus on products
B.Manage by exception
C.Manage by stages
D.Tailor to suit the project
AnswerC

Dividing the project into three-month increments, each ending in a Project Board review and authorisation decision, directly instantiates the manage by stages principle. It requires defined stages with decision points where the Board controls continuation, satisfying the stem's constraint of incremental planning and explicit authorisation before the next increment begins.

Why this answer

'Manage by stages' requires the project to be divided into distinct management stages, each with its own plan and a Project Board decision point (the 'end stage assessment') to authorise the next stage. The scenario describes exactly this: three-month planning increments with Project Board authorisation at each boundary. This is the defining characteristic of the principle.

Exam trap

PRINCE2-PRACTITIONER often tests the confusion between 'manage by stages' and 'manage by exception' — candidates see 'Project Board reviews and authorises' and wrongly pick manage by exception, missing that the authorisation at stage boundaries is the stage-management mechanism.

How to eliminate wrong answers

Option A is wrong because 'focus on products' concerns defining products and their quality criteria, not the division of the project into authorised increments. Option B is wrong because 'manage by exception' concerns tolerances and escalation, not the stage-boundary authorisation process itself. Option D is wrong because 'tailor to suit the project' concerns adapting PRINCE2 to the project context, not the structural division into stages.

Practice this question →
29
MCQeasy

A new Project Manager asks why the Business Case needs to be updated at the end of each stage. Which PRINCE2 principle provides the foundation for this requirement?

A.Learn from experience
B.Focus on products
C.Manage by stages
D.Continued business justification
AnswerD

Continued business justification requires the Business Case to remain valid throughout the project, not merely at initiation. Reviewing it at each stage boundary confirms the project still aligns with strategic objectives and remains viable, satisfying the principle that investment must be justified continuously. This directly explains the stage-end update requirement the new Project Manager queried.

Why this answer

The PRINCE2 principle 'Continued business justification' mandates that a project must have a valid Business Case at all times, and if it ceases to be justified, the project should be stopped. Updating the Business Case at the end of each stage ensures that the project remains aligned with strategic objectives and that the investment continues to be worthwhile. This principle directly drives the requirement for regular reviews and updates to the Business Case, particularly at stage boundaries where the project board decides whether to continue.

Exam trap

PRINCE2-Practitioner often tests the distinction between principles that seem related to stage boundaries, such as 'Manage by stages' and 'Continued business justification', causing candidates to confuse the mechanism (managing by stages) with the underlying reason (maintaining business justification).

How to eliminate wrong answers

Option A is wrong because 'Learn from experience' focuses on capturing and applying lessons throughout the project, not on maintaining the Business Case. Option B is wrong because 'Focus on products' emphasizes defining and delivering products that meet requirements, not on the ongoing justification of the project. Option C is wrong because 'Manage by stages' provides the control mechanism for reviewing progress at stage boundaries, but it is the principle of continued business justification that specifically requires the Business Case to be updated and reviewed at those points.

Practice this question →
30
Multi-Selectmedium

Which THREE of the following statements are true regarding the application and governance of PRINCE2 principles?

Select 3 answers
A.The principles empower behavior and good practice rather than prescribing rigid bureaucratic steps.
B.Applying the principles helps determine whether a project is genuinely being managed using PRINCE2.
C.The principles provide a universal foundation of good practice for any project regardless of industry.
D.The principles only apply during the initiation stage and can be ignored during delivery.
E.An organization can choose to adopt only four of the seven principles and still claim to use PRINCE2.
AnswersA, B, C

PRINCE2 principles are guiding obligations that shape behaviour and good practise, deliberately avoiding prescriptive bureaucracy. This satisfies the stem's requirement for a true governance statement, since tailoring is expected and principles are applied according to project scale, complexity and risk.

Why this answer

Option A is correct because PRINCE2 principles are explicitly designed to shape behavior and embed good practice rather than impose rigid, prescriptive bureaucratic steps, giving projects flexibility in how they are applied. Option B is correct because the seven principles act as the definitive test of whether a project is genuinely being managed using PRINCE2 — if any principle is not applied, the project is not truly following PRINCE2. Option C is correct because the principles are described as universal, applying to every project regardless of industry, scale, organization, geography, or culture, which is why they form the foundation of the method.

Option D is incorrect because principles must be applied throughout the entire project lifecycle, from starting up through delivery and closure, not just during initiation. Option E is incorrect because all seven principles must be applied for a project to claim it is using PRINCE2; adopting only four would mean the project is not following PRINCE2 at all.

Exam trap

PRINCE2-Practitioner often tests whether candidates know that all seven principles are mandatory and apply throughout the project, catching those who treat the principles as optional guidance or as applicable only to certain stages.

Practice this question →
31
Multi-Selectmedium

Which TWO of the following statements accurately reflect the PRINCE2 principle 'Learn from experience'?

Select 2 answers
A.Lessons should be sought, recorded, and acted upon throughout the life of the project.
B.Learning from experience is the primary responsibility of the Project Board only.
C.Project teams should draw on historical data from previous projects when planning.
D.Once a lesson is recorded in the Lesson Log, no further action is required by the project team.
E.Lessons learned are exclusively derived from internal organizational failures.
AnswersA, C

Lessons are not a one-off activity confined to stage boundaries or closure. The principle demands continuous capture and application, so seeking, recording and acting on lessons throughout the project lifecycle directly satisfies the stem's requirement for an accurate reflection of 'Learn from experience'.

Why this answer

Option A is correct because the PRINCE2 'Learn from experience' principle requires that lessons are proactively sought, recorded in the Lessons Log, and acted upon at every stage of the project lifecycle, not just at closure. Option C is correct because PRINCE2 expects teams to review historical data and lessons from similar past projects during planning activities such as the Project Initiation Documentation and stage plans, so that proven approaches are reused and past mistakes avoided. Option B is wrong because learning is a shared responsibility across all roles — the Project Board, Project Manager, Team Manager, and team members — not the Project Board alone.

Option D is wrong because recording a lesson is only the first step; the principle demands that lessons are also analysed and acted upon, with actions tracked and reviewed. Option E is wrong because lessons can come from internal and external sources, including successes, failures, and other projects or industry practice, not exclusively from internal failures.

Exam trap

PRINCE2-PRACTITIONER often tests the misconception that lessons are only from failures or that recording them is sufficient, but the exam expects recognition that lessons must be acted upon and can come from successes.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Principles questions.

Start 20-question session