PRINCE2F People: organizations, teams, and leadership Practice Question
What is the key difference between Project Assurance and quality review?
⚠ Common exam trap
PRINCE2F often tests the categorical distinction between PRINCE2 elements — candidates lose marks by assuming Project Assurance is a process or activity rather than a role, and by confusing quality review with a phase gate rather than a technique.
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; quality review is a technique
In PRINCE2, Project Assurance is defined as a role (or set of responsibilities) assigned to individuals who monitor the project on behalf of the Business, User, and Supplier interests, ensuring the project remains viable and aligned with the Business Case. Quality review, by contrast, is a technique — specifically a quality inspection technique used within the 'Quality' theme to assess whether products meet their quality criteria. The distinction is therefore one of category: a role versus a technique, not a focus area, performer, or timing.
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 focuses on the Business Case; quality review focuses on the project plan
Why it's wrong here
Project Assurance is a continuous role monitoring the project's viability against the Business Case, not a plan-focused activity; quality review is a structured inspection of a specific product against its quality criteria. The option swaps both focal points, so it misstates the actual axis: assurance monitors viability, review inspects products.
- ✓
Project Assurance is a role; quality review is a technique
Why this is correct
Project Assurance is a defined role with assigned responsibilities, whereas a quality review is a technique applied to products. This axis of difference — role versus technique — directly answers what distinguishes the two, rather than their timing, scope or who performs them.
- ✗
Project Assurance is performed by the Project Manager; quality review is performed by the team
Why it's wrong here
Project Assurance is an independent check of the project’s compliance with PRINCE2, performed by someone not in the Project Manager’s direct line of responsibility, whereas quality review is a structured examination of a product’s fitness for purpose. The option is tempting because both activities involve verification, but it wrongly assigns Project Assurance to the Project Manager, who cannot provide independent oversight of their own work.
- ✗
Project Assurance is done at the end of a stage; quality review is done continuously
Why it's wrong here
Project Assurance runs continuously throughout the project, not at stage end; quality reviews are scheduled events triggered when a product is ready for inspection. The timing axis is reversed here. End-of-stage activity describes End Stage Assessments, which is where this option would fit.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PeopleCert exam blueprint
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.