PRINCE2F People: organizations, teams, and leadership Practice Question
In PRINCE2, what is the key difference between the Project Assurance role and a quality review?
⚠ Common exam trap
Watch out — candidates often confuse a role (Project Assurance) with a technique (quality review), leading candidates to mistakenly think they are interchangeable or that one is a subset of the other, when in fact they operate at different levels of project governance.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Project Assurance is a role, while quality review is a technique
Project Assurance is a role defined in PRINCE2, responsible for ensuring the project remains viable and compliant with its business justification, while a quality review is a technique used to assess the quality of a product or deliverable. The key difference is that Project Assurance is an ongoing role performed by individuals independent of the Project Manager, whereas a quality review is a specific, time-boxed event or technique for inspecting deliverables. Option A correctly identifies this fundamental distinction between a role and a technique.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Project Assurance is a role, while quality review is a technique
Why this is correct
Project Assurance is a role within the project management team structure, responsible for monitoring all aspects of project performance independently of the Project Manager. A quality review is a technique used to assess deliverables against quality criteria. The distinction is role versus technique, not responsibility scope.
- ✗
There is no difference; they are the same thing
Why it's wrong here
Project Assurance is a role on the project board, appointed to independently monitor the project on the board's behalf; a quality review is a structured event examining a product against its quality criteria. They differ in nature, timing and output. It is tempting only if assurance activities are confused with the reviews that produce approved products.
- ✗
Project Assurance is performed by the Project Manager, while quality review is performed by external auditors
Why it's wrong here
Project Assurance is delegated by the Project Board to monitor viability, not performed by the Project Manager, who cannot assure their own work. Quality review is a structured product inspection by those involved, not external auditors. The real distinction is ongoing board-level oversight versus a point-in-time product check.
- ✗
Project Assurance focuses on the Business Case, while quality review focuses on the project plan
Why it's wrong here
Project Assurance judges continued business justification across all seven PRINCE2 principles and themes, not merely the Business Case, and a quality review examines a specific product against its quality criteria, not the project plan. It is tempting because assurance does scrutinise the Business Case and reviews do use plans, but the axis is role versus event.
Go deeper
Related to this question
About these practice questions
One of 1,189 original PRINCE2F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PRINCE2F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PRINCE2F exam.