Practice questions · Project Management
PRINCE2 Practitioner (PeopleCert): Practice Questions
Original, scenario-style practice questions for the PRINCE2 7 Practitioner exam, covering the people element, principles, practices, processes and tailoring. Each answer explains why it is right and why the other options are wrong. These are concept and application checks written for study - not questions from the live exam, and not a substitute for the official syllabus.
Answered 0 · Correct 0
-
Midway through a stage, a market change wipes out most of the expected benefits of a project, and the updated business case no longer shows a viable return on the investment. What does the principle of ensuring continued business justification require?
Correct answer: C. Continued business justification means a project that can no longer justify itself must be questioned immediately, so the board decides its future - closing early is a legitimate outcome. Waiting for the stage to end or finishing work packages continues spending without justification, and informally cutting scope bypasses change control while leaving the dead business case unaddressed. -
A project manager begins initiation without looking at how similar projects in the organisation ran before, saying the new project is unique. Which principle is being ignored?
Correct answer: A. Learn from experience obliges the team to seek lessons from earlier work at the start, record them during the project and pass them on afterwards; claiming uniqueness does not remove that duty. Manage by exception concerns tolerances and escalation, focus on products concerns defining deliverables, and no rule delays initiation until unrelated projects close. -
The corporate sponsor of a project regularly phones team managers directly with new instructions, bypassing both the project board and the project manager. Which principle does this behaviour undermine most directly?
Correct answer: B. PRINCE2 requires an agreed structure in which everyone knows who directs, who manages and who delivers; instructions that bypass the board and project manager dissolve that accountability. Business justification concerns whether the project remains worthwhile, focus on products concerns defining deliverables, and manage by stages concerns how commitment is released stage by stage. -
A project board asks to approve the whole project in one decision at the outset and then leave the team alone until handover. Which principle says this is not how PRINCE2 commits to a project?
Correct answer: D. Manage by stages means the board commits funding one management stage at a time and reviews the project at each stage boundary before authorising the next, so a single up-front approval with no further reviews is contrary to the method. Manage by exception governs when escalation happens within delegated limits, and the other two principles concern lessons and product focus rather than commitment points. -
A newly appointed project manager sends every routine decision to the project board for confirmation, even when stage forecasts sit comfortably within tolerance. Why is this a problem in PRINCE2 terms?
Correct answer: B. Manage by exception gives each level room to manage within agreed tolerances, so the board is involved only when a deviation is forecast - constant referrals waste the board's attention and defeat the point of delegation. Product descriptions record product requirements rather than decisions, boards also decide outside boundaries when exceptions arise, and a change authority handles requests for change, not routine management decisions. -
Planning workshops for a new service begin with a detailed activity schedule, while what the service must actually deliver and to what standard remains undefined. Which principle is being violated, and how should planning start?
Correct answer: A. Focus on products makes agreed product definitions the basis of planning: what will be delivered and to what quality comes before what work is done, which is why product-based planning starts from the project product description. Staging the schedule, reviewing lessons or adding tolerances are all real techniques, but none repairs the core error of scheduling activity before the products are defined. -
To keep a small internal project light, its board proposes dropping the business case altogether and skipping any benefit tracking, arguing that tailoring allows it. What is the correct assessment?
Correct answer: D. Principles are the non-negotiable part of the method: tailoring adjusts how they are met - a small project can carry a very light business case - but a project with no business justification at all is no longer following PRINCE2. Tailoring never removes principles, an informal cost note is not a justification, and the opposite extreme is also wrong because the format genuinely can be simplified. -
Which situation shows manage by exception operating as intended?
Correct answer: B. Manage by exception is working when each level manages freely inside agreed tolerances and escalates as soon as a deviation is forecast - not after it has happened. Reporting an overrun only after the stage ends is escalation after the fact, weekly re-approval of an unchanged plan is exactly the oversight burden the principle removes, and stopping work for every small problem ignores the delegated room to manage. -
A stage has spent just over half its budget with just under half the work done, and the project manager's forecast still lands inside the stage's cost tolerance. The project manager records the position in the next highlight report and takes no further action. Is this appropriate?
Correct answer: C. Escalation in PRINCE2 is triggered by a forecast tolerance breach, not by discomfort: while the forecast remains within stage tolerance the project manager manages on, keeping the board informed through time-driven highlight reports. An exception report without a forecast breach contradicts manage by exception, an early boundary is not a budget-reset device, and written team-manager guarantees are not a PRINCE2 control. -
According to the people element of PRINCE2 7, which activity is an example of leading rather than managing?
Correct answer: A. PRINCE2 7 distinguishes managing - structures, plans, registers, decisions - from leading, which is about direction, motivation and trust; building commitment to a shared vision is leadership. Updating plans, recording issues and checking products against quality criteria are all management or delivery activities that keep the machine running rather than move people. -
A programme replaces a core system used by hundreds of staff. The plans and product descriptions are excellent, yet staff first hear about the change the week the system goes live, and adoption is poor. Which element of PRINCE2 7 was neglected?
Correct answer: D. PRINCE2 7 treats leading change as central: outputs only produce outcomes and benefits when the people affected are prepared, informed and supported to adopt them, which is a people-element responsibility. More plan detail, more frequent checkpoints or extra acceptance criteria would all have polished delivery of the output while leaving the adoption failure - the actual cause - untouched. -
In PRINCE2 7, what does the project ecosystem that the people element refers to include?
Correct answer: B. The ecosystem view widens attention beyond the org chart: a project sits inside its organisation and among external parties - users, suppliers, regulators and others - whose culture and interests shape what will work. The named management team is only part of that picture, and neither the technical toolset nor the flow of management products is what the people element means by ecosystem. -
Two recently merged companies run a joint project, and their staff have clashing habits around decision-making and reporting. The project manager assumes the organisation chart will resolve this over time. What does PRINCE2 7 say about this assumption?
Correct answer: C. PRINCE2 7's people element treats culture and collaboration as things a project must work on explicitly - agreeing ways of working, communicating deliberately and building trust - because an organisation chart assigns accountability but does not change behaviour. Roles alone resolving culture is the exact assumption being challenged, culture inside a project is not merely an HR matter, and an exception requires a forecast tolerance breach. -
Key stakeholders complain that they keep discovering project decisions weeks after they are made. Which people-element failing does this point to?
Correct answer: C. Deliberate communication - the right information to the right stakeholders at the right time - is a core concern of the people element, and stakeholders repeatedly learning of decisions late is its classic failure signal. Producing more management products or holding more boundaries adds ceremony without fixing the information flow, and the change authority's budget governs change decisions, not stakeholder communication. -
Why does PRINCE2 7 link leading change so tightly to benefits realisation?
Correct answer: A. The chain from output to outcome to benefit runs through people: a delivered product creates value only when its users adopt new ways of working, which is why preparing and leading that change is treated as benefit-critical. Team managers deliver products rather than calculate benefits, the benefits management approach is not the change authority's product, and shortening stages has no automatic link to benefits. -
A project delivers a new booking system. Afterwards, staff handle reservations in a completely new way, and the organisation experiences measurably fewer booking errors. In business case terms, what is the new way of working?
Correct answer: B. The chain is output, outcome, benefit: the booking system is the output the project delivers, the changed way of handling reservations is the outcome that the output enables, and the measurable reduction in errors is the benefit. A dis-benefit would be a genuine negative consequence of the change, which a new working practice in itself is not. -
Closing a regional office will save money but will force some retained staff into longer commutes, which the organisation accepts and plans around. How does PRINCE2 classify the longer commutes?
Correct answer: D. A dis-benefit is a real, expected negative consequence of a change that the organisation accepts with open eyes and weighs against the benefits - exactly the longer commutes here. A risk is uncertain rather than expected, an issue is a specific event needing a response rather than a standing consequence, and tolerance is permitted deviation from a plan target, not an accepted downside. -
Months after handover, corporate management asks who should be demonstrating that the promised benefits of a completed project are being realised. Which role does PRINCE2 point to?
Correct answer: A. The senior user specifies the benefits on behalf of those who will use the products and is held to account for demonstrating that they are realised - a duty that continues after the project closes. The project manager's accountability ends with the project itself, the senior supplier represents the building side rather than benefit realisation, and project support is an administrative function. -
Late in a stage, the senior user and senior supplier disagree about whether extra scope should be funded, and the discussion stalls. As the single point of accountability for the business case, who owns the final decision?
Correct answer: C. The executive owns the business case and is ultimately the single decision-maker on the board; senior user and senior supplier advise and represent their interests, but the board is not a democracy. The project manager manages within delegated limits rather than owning funding decisions, majority voting misstates how the board works, and assurance checks on the board's behalf without deciding. -
To cut costs on a mid-sized project, the project manager offers to carry out the project assurance reviews personally, reporting the findings to the board. Why must the board refuse?
Correct answer: B. Assurance answers the question of whether the board can trust what it is being told, which collapses if the person being checked performs the checking - independence from the project manager is the non-negotiable rule. Board members may do their own assurance or delegate it, external consultants are optional rather than mandatory, corporate ownership is not required, and technical knowledge is beside the structural point. -
A project expects a steady stream of small change requests, and the board does not want to convene for each one. What does the organizing practice recommend?
Correct answer: D. PRINCE2 anticipates exactly this: the board can delegate change decisions within defined severity and cost limits to a change authority, funded through a change budget, keeping control without constant meetings. Team managers approving changes bypasses change control, project support is administrative and holds no decision authority, and corporate management sits above the board rather than inside routine change decisions. -
A planning session for a new stage opens with the team listing tasks and estimating durations. Applying product-based planning, what should have come first?
Correct answer: B. Product-based planning works from what to how: identify the products, write their descriptions with quality criteria, map their dependencies, and only then plan the activities that will build them. Tolerances, ownership and reporting cadence all matter to a stage plan, but each is set around a plan whose backbone is products - none of them replaces defining the products first. -
A stage's cost tolerance is forecast to be exceeded, the project manager has sent an exception report, and the board wants the project to continue. What does the board commission next, and what happens to the current stage plan?
Correct answer: A. When the board decides to continue after an exception report, it asks for an exception plan covering the period from now to the end of the stage; on approval it replaces the current stage plan. The project brief belongs to pre-project startup and is not revived, moving work to another team manager does not address the broken plan, and closure is one possible board choice rather than an automatic outcome. -
At handover, the customer refuses a product because 'finished' means something different to them than to the team that built it. Which earlier failure does the quality practice point to?
Correct answer: C. Quality in PRINCE2 is planned up front: the product description carries measurable quality criteria agreed with the customer, giving both sides one checkable definition of finished before work starts. The quality register records activities but does not define standards, the project manager's personal attendance at reviews is not required, and board composition is an organizing matter that would not repair undefined criteria. -
During an audit, the project is asked to show which quality activities were planned for the stage and what the results of the completed ones were. Where does PRINCE2 record this?
Correct answer: D. The quality register is the running record of quality activity: what checks are planned, when, by whom, and what results came back - precisely what an audit trail needs. The daily log holds the project manager's informal notes, product descriptions define requirements and criteria rather than logging results over time, and a highlight report is a periodic progress summary, not a quality record. -
One team reports that a key supplier might become insolvent in the coming months; another reports that the shared test environment failed this morning. How does the risk practice classify these two items?
Correct answer: B. The dividing line is uncertainty: a risk is an uncertain future event that would affect objectives if it occurred, while an issue is something that has already happened and needs handling now. The supplier's possible insolvency is uncertain and in the future, so it is a risk; the failed environment is a present fact, so it is an issue - which also rules out both remaining classifications. -
A project cannot tolerate the financial impact of a fire in its temporary warehouse, so it takes out an insurance policy covering the loss. Which threat response is this?
Correct answer: A. Insurance passes part of the financial impact of the threat to a third party in exchange for a premium, which is the transfer response; the fire itself remains possible. Avoid would mean removing the threat, for example by not using the warehouse; reduce would lower its probability or impact, such as installing sprinklers; accept would mean consciously living with the exposure unchanged. -
A supplier reveals it could finish a critical component well ahead of schedule, which would let the organisation start earning benefits early. The project team replans specifically to make sure this early finish is captured. Which opportunity response is this?
Correct answer: D. Exploit is the response that commits to capturing an opportunity, removing the uncertainty by replanning so the benefit will happen - which is what replanning to guarantee the early finish does. Enhance only improves the odds without securing the outcome, share distributes gains with another party under an agreed arrangement, and reject walks away from the opportunity altogether. -
Testing shows a delivered component misses one of the quality criteria in its product description, and the supplier asks for it to be accepted as it is. How does the issues practice classify the supplier's request?
Correct answer: C. A product that fails to meet its agreed specification is an off-specification, and accepting it unchanged is a concession that only the board or its delegated change authority can grant. A request for change asks to alter a baseline rather than waive it, a risk is an uncertain future event whereas this shortfall is already a fact, and recording a lesson does not decide what happens to the product. -
Which report does a team manager send to the project manager to show progress on an agreed work package?
Correct answer: B. Checkpoint reports run from team manager to project manager at the frequency agreed in the work package, giving the project manager visibility of delivery progress. The highlight report is the project manager's periodic report to the board, the end stage report belongs to a stage boundary, and an exception report is triggered by a forecast tolerance breach - not by routine progress within tolerance. -
Which process belongs to the project board rather than the project manager, and runs from initiation through to project closure?
Correct answer: A. Directing a project is the board's own process: it authorises initiation, the project itself, each stage or exception plan, gives ad-hoc direction and finally authorises closure, without managing day to day. Closing a project and initiating a project are carried out by the project manager, and starting up a project is pre-project preparation in which the executive and project manager are appointed - not a board-only activity. -
In which process is the project brief produced?
Correct answer: C. The project brief is assembled during starting up a project, giving the board just enough - outline business case, approach, team structure - to decide whether initiating the project is worthwhile. Initiating a project then expands the brief into the full project initiation documentation, directing a project consumes the brief rather than writing it, and stage boundaries come later still. -
The board has authorised initiation. Which process now assembles the project initiation documentation, and what is the PID for?
Correct answer: D. Initiating a project builds the PID: the assembled definition of the project's approaches, controls, plans and refined business case, agreed between board and project manager as the baseline for running the project. Starting up produces the earlier project brief instead, directing a project makes decisions rather than documents, and day-to-day stage control works from stage plans, not from drafting the PID. -
During a stage, who authorises a work package, and in which process does that authorisation happen?
Correct answer: B. Authorising work packages is part of controlling a stage: the project manager hands an agreed package of work to a team manager, who accepts it in managing product delivery. The board authorises stages rather than individual work packages, the team manager receives rather than issues the authorisation, and no countersigning step by assurance at a boundary exists in the method. -
Which sequence correctly describes a team manager's path through managing product delivery?
Correct answer: C. Managing product delivery mirrors controlling a stage from the team side: the team manager agrees and accepts the work package, develops the products to their descriptions with the agreed quality checks, sends checkpoint reports, and hands back completed work. Stage plans and stage closure belong to the project manager, work packages are issued rather than self-approved, and team managers escalate to the project manager, not the board. -
A stage is approaching its planned end with the project still viable. What does managing a stage boundary require the project manager to prepare for the board?
Correct answer: A. Managing a stage boundary packages the board's next commitment decision: how the ending stage performed (end stage report), whether the project still makes sense (updated business case and project plan), and what comes next (next stage plan, or an exception plan when that is the trigger). Closure recommendations belong to closing a project, the mandate is pre-project input, and an exception report needs a forecast breach, not near misses. -
At the end of the final stage, who formally authorises the closure of the project?
Correct answer: D. Closing a project is carried out by the project manager - confirming acceptance, handing over products, capturing lessons and drafting a closure recommendation - but the authority to close rests with the project board in directing a project. The project manager recommends rather than authorises, corporate management sits above the board's delegated authority, and project support is administrative with no decision power. -
Halfway through, the board concludes the project is no longer justified and instructs premature closure. What does the method require now?
Correct answer: B. Premature closure still goes through closing a project: the project manager agrees with the board what is worth salvaging, hands over anything usable, updates records, captures lessons and prepares the closure recommendation - a controlled stop rather than abandonment. An instant stop loses salvageable value and lessons, waiting for a boundary continues unjustified spending, and handing work packages to corporate management is not a PRINCE2 mechanism. -
What question is the starting up a project process designed to answer before any significant money is committed?
Correct answer: A. Starting up is a deliberately light pre-project filter: appoint the executive and project manager, capture lessons, outline the business case and assemble the project brief - just enough for the board to decide whether initiation is a sound investment. Full requirement detail is neither possible nor sought that early, initiation cannot be skipped, and supplier selection is delivery work, not the gateway question. -
After receiving an exception report, the board privately agrees the project should change direction, and one board member begins issuing revised task lists directly to the delivery teams. Which process boundary is being crossed?
Correct answer: C. The board directs: it responds to an exception report with a decision - request an exception plan, give guidance, or close - and its instructions flow as direction to the project manager, who manages the teams. An exception report never converts board members into line managers, checkpoint reporting is the team manager's duty rather than the issue here, and task-level change is not locked to stage boundaries. -
Which statement correctly describes tailoring in PRINCE2 7?
Correct answer: D. Tailor to suit the project is itself a principle: every project adapts the method's practices, processes, roles and products to its size, risk and environment, while the seven principles stay non-negotiable. There is no size threshold below which tailoring becomes allowed, principles can never be deselected, and applying the method untailored is a documented mistake rather than the default. -
On a small project, several role combinations are proposed to save people. Which one does PRINCE2 rule out?
Correct answer: A. Direction and management must stay separate: the executive owning the business case cannot also be the project manager executing it, or the board would be supervising itself. The other combinations are legitimate tailoring on small projects - the executive may double as senior user, the project manager may absorb the team manager role, and board members may perform their own assurance rather than delegating it. -
A five-person project proposes that the highlight report be a half-page email against the stage plan's targets. How should this proposal be judged?
Correct answer: B. Tailoring management products is normal: what matters is that the purpose survives - the board still receives the progress picture it needs at the agreed frequency - not the format it arrives in. Formats are not mandated, a shorter report can carry full control value on a small project, and a board waiving progress information altogether would abandon control rather than tailor it. -
To hit an aggressive deadline on a large, high-risk programme component, the project manager proposes skipping initiating a project entirely and starting delivery from the approved brief. What is the correct judgement?
Correct answer: C. Tailoring can make initiation lean, but it cannot delete it: without a PID there is no agreed baseline of controls, approaches and justification, which on a large, risky piece of work removes exactly the protection PRINCE2 exists to give. An outline business case is not a management baseline, tighter tolerances cannot substitute for undefined controls, and no special public-sector rule governs shortening initiation. -
Which factors does PRINCE2 7 expect to drive how a project tailors the method?
Correct answer: D. Tailoring decisions flow from project context: scale, complexity, risk, and the organisational environment and culture the project operates in, so the method stays proportionate to the situation. The project manager's certification, the board's funding rhythm and the available reporting tools are practical facts of life, but none of them is what the method names as the driver of tailoring.
Practice questions FAQ
- Are these real PRINCE2 Practitioner exam questions?
- No. These are original study questions written to test understanding. They are not real exam questions, exam dumps, or copied from any provider.
- How should I use these practice questions?
- Answer each one, read the explanation (including why the wrong options are wrong), and use the per-domain score below to focus your revision on weak areas. Revisit before exam day.
- How many questions should I do before the exam?
- Enough to score consistently across every domain, alongside full-length practice from official or reputable providers. Understanding why each answer is right matters more than raw volume.
- What score means I am ready?
- A good signal is consistently scoring around 80% or higher across all domains on questions you have not seen before, and being able to explain why the wrong options are wrong.
- Should I use exam dumps?
- No. Dumps (real or leaked questions) breach provider policy, can void your certification, and do not build the understanding the exam actually tests.