Sign in
Home/PRINCE2/PRINCE2 Foundation/Free questions

PRINCE2 Foundation — Free Practice Questions

10 free sample questions from a bank of 573, with the correct answers and explanations. No signup required — start practising right now.

1Which product records any project outcomes perceived as negative by stakeholders?
  • Business Case
  • Project Plan
  • Communication Management Strategy
  • Project Product Description
Answer: A

The short version

A — Business Case records perceived negative outcomes. Benefits plus disbenefits live in the Business Case, and negative stakeholder impacts are tracked as disbenefits. Other products plan delivery or describe quality, not value trade-offs.

Key concepts in this question

  • Business Case purpose: justify the project through benefits, costs, risks and disbenefits over time.
  • Disbenefit meaning: an outcome seen as negative by one or more stakeholders yet accepted for net value.
  • Project Plan and Product Description: schedule plus scope detail without value appraisal.
  • Communication Strategy: stakeholder messaging plan, not the value ledger itself.

Why A is correct

PRINCE2 places every outcome perceived as negative into the Business Case as a disbenefit for continued justification. The question asks exactly where such perceived negatives are recorded. Only the Business Case owns that value versus harm balance, so A is the settled answer.

Why the others are wrong

  • B. Project Plan shows stages and resources, not stakeholder value judgments.
  • C. Communication Management Strategy plans messaging, not benefit accounting.
  • D. Project Product Description defines acceptance criteria, not disbenefits.

PRINCE2-Foundation exam tip

Negative outcome perceived by stakeholders always means disbenefit in the Business Case.

2What needs to be in place to ensure effective issue and change control?
  • Configuration management system
  • Manage by exception
  • Quality planning
  • Information needs for stakeholders
Answer: A

The short version

A — Configuration management enables issue and change control. Baselines plus version control let the board assess impact against the correct product states. Without that system, change decisions lack a trusted reference.

Key concepts in this question

  • Configuration management system: identifies, baselines and tracks every product version.
  • Issue and change control: evaluates requests, decides responses and protects approved baselines.
  • Manage by exception and quality planning: tolerance governance and criteria design, not version truth.
  • Stakeholder info needs: messaging scope, not the control mechanism itself.

Why A is correct

Effective control requires recalling baselines and ensuring the right versions reach the customer. The configuration system provides that product truth for impact analysis and implementation. Vendor prose cites baseline recall as the enabler, so A is correct.

Why the others are wrong

  • B. Manage by exception sets tolerance escalation, not product version control.
  • C. Quality planning defines criteria and methods, not change baselines.
  • D. Stakeholder information needs shape comms, not issue disposition.

PRINCE2-Foundation exam tip

Issue and change control always needs a configuration management system for baselines.

3Which is a recommended quality review team role?
  • Project Manager
  • Assurance
  • Project Support
  • Administrator
Answer: D

The short version

D — Administrator is a quality review team role. The review team uses Chair, Presenter, Reviewer and Administrator to run the check. Project Manager, Assurance and Support sit outside that review roster.

Key concepts in this question

  • Quality review technique: structured peer check of a product against its quality criteria.
  • Four review roles: chair controls, presenter introduces, reviewer checks, administrator records.
  • Project management roles: manager plus support deliver and assist, assurance oversees independently.
  • Memorization test: exam swaps delivery roles into the review list as distractors.

Why D is correct

PRINCE2 defines Administrator as the scribe who records agreed actions and responsibilities during the review. That role is unique to the review meeting structure. The other options name valid project roles that never serve as review team seats, so D is correct.

Why the others are wrong

  • A. Project Manager owns delivery and does not sit as a review team role.
  • B. Assurance provides independent oversight, not review meeting administration.
  • C. Project Support assists the manager and is not a review scribe.

PRINCE2-Foundation exam tip

Review team equals Chair Presenter Reviewer Administrator, memorize that quartet.

4Which is a purpose of a Project Product Description?
  • Records the costs and timescales for delivery of the project's final product
  • Shows the dependencies between the project's products to aid planning
  • Provides a list of all the products to be delivered by the project
  • Defines what the project must deliver in order to gain acceptance
Answer: D

The short version

D — Project Product Description defines acceptance for the final product. It states what must be delivered for the customer to accept the project outcome. Plans, diagrams and lists support that goal but do not set the acceptance bargain.

Key concepts in this question

  • Project Product Description: top-level definition of the final product plus acceptance criteria and methods.
  • Acceptance focus: the conditions that prove the project delivered what was promised.
  • Cost timescale and dependencies: plan and flow diagram details that implement, not define, acceptance.
  • Product list: breakdown inventory without the acceptance test itself.

Why D is correct

PRINCE2 uses the Project Product Description to gain agreement on what acceptable looks like before stages begin. Only D captures that must-deliver-to-gain-acceptance purpose. Other options describe planning artifacts that assume acceptance is already defined.

Why the others are wrong

  • A. Costs and timescales belong to stage and project plans, not the product bargain.
  • B. Dependencies aid planning through flow diagrams, not acceptance definition.
  • C. A list of products inventories scope without stating acceptance conditions.

PRINCE2-Foundation exam tip

What must be delivered to gain acceptance always means Project Product Description.

5Which of the following statements about quality assurance and Project Assurance is true?
  • Project Assurance is the responsibility of the corporate organization; quality assurance is the responsibility of the Project Board
  • Project Assurance is independent of the Project; quality assurance is only independent of the Project Manager
  • Project Assurance may be delegated within a project; quality assurance must be undertaken by the Project Board
  • Project Assurance ensures compliance to standards within the project environment; quality assurance ensures compliance across the organization
Answer: D

The short version

D — Project Assurance is in-project, quality assurance is corporate. Project Assurance is the board owning correct conduct inside the project, while quality assurance checks standards across the organization independently. That split is the tested distinction.

Key concepts in this question

  • Project Assurance: board-side business, user and supplier checks that the project runs correctly.
  • Quality assurance: independent corporate audit that management and direction fit standards.
  • Independence scope: QA independent of the project, Project Assurance independent only of the manager.
  • Delegation nuance: board retains Project Assurance duty even when tasks are delegated.

Why D is correct

PRINCE2 guidance states Project Assurance guards compliance within the project environment while quality assurance guards compliance to wider corporate or programme standards. Option D is the only wording that keeps both scope statements correct. Other options swap responsibilities or independence levels.

Why the others are wrong

  • A. Reverses ownership by giving Project Assurance to corporate and QA to the board.
  • B. Misstates independence by making Project Assurance fully project-independent.
  • C. Wrongly forces QA onto the board and misplaces delegation rules.

PRINCE2-Foundation exam tip

Inside project equals Project Assurance, across organization equals quality assurance.

6Who carries out audits that are independent of the project?
  • Quality assurance
  • Project Assurance
  • Project Support
  • Project Manager
Answer: A

The short version

A — Quality assurance carries independent audits. Corporate QA sits outside the project and can audit objectively. Project Assurance, Support and Manager all work inside delivery and lack that independence.

Key concepts in this question

  • Independent audit need: stakeholders want confidence from eyes outside delivery pressure.
  • Quality assurance position: corporate function separate from the project team.
  • Project Assurance position: board members assuring their own project, still inside it.
  • Delivery roles: manager plus support execute work and cannot audit themselves.

Why A is correct

Only a body independent of the project can credibly audit its management. PRINCE2 assigns that to quality assurance at corporate or programme level. The other roles are embedded in project governance or delivery, so they fail the independence test.

Why the others are wrong

  • B. Project Assurance is tied to the board and therefore not independent of the project.
  • C. Project Support assists delivery and cannot provide independent audit.
  • D. Project Manager delivers the work being audited and lacks independence.

PRINCE2-Foundation exam tip

Independent of the project audit always means quality assurance, never Project Assurance.

7Identify the missing word(s) in the following sentence. During a quality review meeting [ ? ] any identified defects.
  • a solution should be designed for
  • an issue should be created for
  • the agreed actions should be recorded for
  • the chair will approve the solution to
Answer: C

The short version

C — Record agreed actions for defects in the review. The meeting does not solve every defect live, it captures actions plus owners for later fix. Solution design or chair approval overstates the meeting purpose.

Key concepts in this question

  • Quality review meeting flow: check product line by line, agree actions, record owners.
  • Administrator duty: log each question, action and responsibility as raised.
  • No live redesign: solving defects belongs to follow-up work, not the review itself.
  • Issue creation nuance: actions are recorded directly, not always as formal issues.

Why C is correct

PRINCE2 procedure says the team agrees actions on each question as raised and the administrator records them. Option C repeats that record-agreed-actions rule for identified defects. Other wordings add solution or approval steps the method does not require.

Why the others are wrong

  • A. Designing solutions live turns a check into rework and is not the meeting rule.
  • B. Creating an issue for every defect adds process the review step does not mandate.
  • D. Chair approval of solutions confuses facilitation with product approval.

PRINCE2-Foundation exam tip

Defects in a review means record agreed actions, never design the fix there.

8Which statement about the quality review technique is FALSE?
  • It enables a check to be made on a product's fitness for purpose
  • It defines the quality responsibilities of the project team
  • It supports the management of future changes by providing a baseline for a product
  • It is used to gain wider acceptance of a product by involving key interested parties
Answer: B

The short version

B — It defines quality responsibilities is the FALSE claim. The review technique checks fitness, baselines products and builds acceptance, but responsibility definition lives in role descriptions and strategies. Spotting that outlier is the test.

Key concepts in this question

  • Quality review objectives: assess conformity, involve parties, confirm readiness and baseline the product.
  • FALSE pattern: three true benefits plus one outsider from organization design.
  • Responsibility definition: set in Project Board duties and quality strategies, not in a review meeting.
  • Baseline and acceptance value: reviews freeze approved versions and widen buy-in.

Why B is correct

PRINCE2 lists conformity checks, stakeholder acceptance, completion confirmation and change baseline as review goals. Defining team quality responsibilities never appears in that list. Option B is therefore the only false statement about the technique.

Why the others are wrong

  • A. Fitness for purpose checking is a core true objective of the review.
  • C. Providing a future change baseline is an explicit true review benefit.
  • D. Gaining wider acceptance through involvement is a stated true goal.

PRINCE2-Foundation exam tip

FALSE about quality review usually means responsibilities, which live elsewhere.

9Which should be funded by a change budget?
  • Increase in agreed scope
  • Initiation stage
  • Change Authority
  • Handover activities
Answer: A

The short version

A — Change budget funds scope increases. Agreed extra scope needs customer plus supplier money outside tolerances. Initiation, authority costs and handover belong to project budgets or tolerances, not change funds.

Key concepts in this question

  • Change budget purpose: ring-fenced sum for authorized requests for change to baselines.
  • Scope increase case: more output than approved, requiring funded change control.
  • Tolerance boundary: within-tolerance fixes use project budget, only baseline change uses change budget.
  • Initiation and handover: planned stage costs covered by normal project funding.
  • Change Authority nuance: the body that approves, not the thing being funded.

Why A is correct

PRINCE2 funds an increase in agreed scope from the change budget after change approval. That keeps baseline funding clean and shows the customer pays for added scope. Other options describe standard delivery costs that never need change money, so A stands out clearly.

Why the others are wrong

  • B. Initiation stage is planned project work funded from the project budget.
  • C. Change Authority operating cost comes from overall budget, not change funds.
  • D. Handover activities are planned closure costs, not scope change.

PRINCE2-Foundation exam tip

Increase in agreed scope always points to change budget funding for baseline change.

10Which of the following statements about customer's quality expectations and acceptance criteria are true? 1. Customer's quality expectations form a specific and precise list of measurable criteria that a project product should meet in order to be acceptable to key stakeholders. 2. Acceptance criteria are often expressed in broad terms as a means to gain common understanding of general quality requirements.
  • Only 1 is true
  • Only 2 is true
  • Both 1 and 2 are true
  • Neither 1 or 2 are true
Answer: D

The short version

D — Neither statement about expectations and criteria is true. Customer quality expectations are broad, acceptance criteria are precise and measurable. Both stems swap those definitions, so neither stands.

Key concepts in this question

  • Customer quality expectations: high-level broad desires such as robust or long lasting.
  • Acceptance criteria: specific measurable tests such as material grade or twenty-year life.
  • Swap trap: statement one calls expectations precise, statement two calls criteria broad.
  • Classroom example: water pump robust versus cast iron grade shows broad versus measurable split.
  • Both false outcome: when each definition is reversed, Neither is the only verdict.

Why D is correct

PRINCE2 teaches expectations as common-understanding broad terms and criteria as measurable proof points. Statement one reverses the first, statement two reverses the second. With both reversed, Neither 1 or 2 are true is the settled result for this bank row.

Why the others are wrong

  • A. Only 1 is true fails because expectations are broad, not precise lists.
  • B. Only 2 is true fails because criteria are measurable, not broad terms.
  • C. Both true would require both definitions correct, yet both are swapped.

PRINCE2-Foundation exam tip

Expectations broad plus criteria measurable means swapped stems equal Neither true.

Want the full bank of 573 questions for PRINCE2 Foundation? See all practice exams.