How Candidates Mis-read Questions and How to Outsmart the Exam
This cheat-sheet focuses on the most common traps caused by poor exam technique, not lack of knowledge. Every trap follows the same format:
- The Trap
- What the Exam Is Really Testing
- How to Spot It Quickly
- What the Correct PRINCE2 Thinking Looks Like
This builds true Practitioner-level thinking and positions your learners as high-value professionals.
“Most Appropriate” Does NOT Mean “Any Acceptable”
The Trap:
Candidates select an answer that would work in reality, but not the best aligned with PRINCE2.
What Is Being Tested:
Your ability to rank PRINCE2 actions, not just choose a valid one.
How to Spot It:
The question includes words like most appropriate, best response, or most effective.
Correct Thinking:
You must choose the option that best reflects Governance and Role authority
Formal process order
Not the fastest or most practical action.
“First Action” Is About Sequence, Not Outcome
The Trap:
Candidates choose the correct action, but at the wrong point in the process.
What Is Being Tested:
Your knowledge of process flow.
How to Spot It:
Look for: First step, Initial action, What should be done next
Correct Thinking:
Always ask:
“What MUST happen formally before anything else can happen?”
Confusing “Issue” With “Change”
The Trap:
Logging everything as a Request for Change.
What Is Being Tested:
Understanding of Issue Types: Problem, Concern, Request for Change
How to Spot It:
The scenario describes an event but does not request scope change.
Correct Thinking:
Not all issues are changes.
Only scope-affecting items become Requests for Change.
Misusing “Manage by Exception”
The Trap:
Escalating everything to the Project Board.
What Is Being Tested:
Your understanding of tolerance and delegation.
How to Spot It:
Look for tolerance values in the scenario.
Correct Thinking:
If tolerances are NOT forecast to be breached, the Project Manager stays in control.
Ignoring the Business Justification
The Trap:
Candidates solve operational problems without checking viability.
What Is Being Tested:
The Continued Business Justification principle.
How to Spot It:
The scenario mentions: Falling benefits, Rising costs, Reduced demand
Correct Thinking:
PRINCE2 always protects the business case before anything else.
Treating the Project Manager as the Decision Authority
The Trap:
Giving approval powers to the Project Manager that belong to the Board.
What Is Being Tested:
Role authority and governance separation.
How to Spot It:
Look for decisions involving: Stage approval, Exception approval, Project closure
Correct Thinking:
These belong to the Project Board, not the Project Manager.
Misreading “Stage” Versus “Project”
The Trap:
Applying project-level controls at stage level and vice versa.
What Is Being Tested:
Understanding of the timeline and control layers.
How to Spot It:
The question explicitly says: “Current stage”, “End of stage”, “Project nearing completion”
Correct Thinking:
Stage boundaries trigger formal review and re-authorisation.
Choosing Informal Action Over Formal Control
The Trap:
Selecting a conversation or informal fix instead of a required PRINCE2 product.
What Is Being Tested:
Discipline of formal management products.
How to Spot It:
One answer sounds easy and quick, and the other sounds structured and formal.
Correct Thinking:
PRINCE2 always favours defined controls over informal fixes.
Confusing “Risk” With “Issue”
The Trap:
Treating something that has already happened as a risk.
What Is Being Tested:
Your ability to distinguish: Risk = future uncertainty, and Issue = something that has occurred
How to Spot It:
The wording says the event has already happened.
Correct Thinking:
Register it as an Issue, not a Risk.
Ignoring Product-Based Planning
The Trap:
Planning by activities instead of products.
What Is Being Tested:
The PRINCE2 planning philosophy.
How to Spot It:
The scenario mentions confusion over outputs or quality.
Correct Thinking: Define products first, then plan activities.
Forgetting Tailoring
The Trap:
Assuming PRINCE2 must always be applied in full.
What Is Being Tested:
Your understanding of tailoring to suit the project.
How to Spot It:
The scenario describes a small, low-risk, or agile project.
Correct Thinking: PRINCE2 should scale down when appropriate.
Selecting the Right Action for the Wrong Role
The Trap:
Correct action, wrong owner.
What Is Being Tested:
You know what must happen, but not who must do it.
How to Spot It:
Two answers look similar except for the role named.
Correct Thinking:
Always validate: Authority, Accountability, Governance level
Treating Quality as Testing Only
The Trap:
Quality is reduced to inspection at the end.
What Is Being Tested:
Full Quality Management Practice: Planning, Control, Assurance
How to Spot It:
The question talks about unclear acceptance criteria.
Correct Thinking:
Quality starts at definition, not at delivery.
Misinterpreting “Progress” as Only Time-Tracking
The Trap:
Progress is treated as schedule only.
What Is Being Tested:
Control of: Time, Cost, Scope, Risk, Quality, Benefits, Sustainability
How to Spot It:
The scenario mentions unexpected trends.
Correct Thinking:
Progress control uses tolerances across all dimensions.
Ignoring the Change Authority Concept
The Trap:
Sending every change to the Project Board.
What Is Being Tested:
Understanding of delegated change approval.
How to Spot It:
The scenario mentions predefined authority limits.
Correct Thinking:
Low-impact changes can be handled by the Change Authority.
Assuming the Project Board Manages Day-to-Day Work
The Trap:
Letting the Board control tasks.
What Is Being Tested:
Separation between: Directing, Managing, Delivering
How to Spot It:
Answers involve Board members managing operational work.
Correct Thinking:
Board directs. Team Managers deliver.
Misreading Negative Questions
The Trap:
Failing to spot least likely, not, or except.
What Is Being Tested:
Precision in reading.
How to Spot It:
The word NOT changes everything.
Correct Thinking:
You must reverse your usual selection logic.
Jumping to Closure Too Early
The Trap:
Ending the project before formal closure activities.
What Is Being Tested:
Understanding of: Acceptance, Benefits review planning, Lessons learned
How to Spot It:
The scenario says delivery is complete.
Correct Thinking:
Delivery completion is not project closure.
Selecting “Good Leadership” Over “Correct Governance”
The Trap:
Choosing answers that sound inspirational rather than controlled.
What Is Being Tested:
PRINCE2 is a governance framework, not a leadership style guide.
How to Spot It:
Some answers sound motivational rather than procedural.
Correct Thinking:
Always choose the governed option.
Overthinking the Scenario
The Trap:
Adding imagined problems that do not exist in the text.
What Is Being Tested:
Your ability to work only with stated facts.
How to Spot It:
You find yourself saying “what if”.
Correct Thinking:
Only respond to what is explicitly in the scenario.
Why This Cheat-Sheet Directly Improves Career Value
Candidates who master these traps do not just pass exams. They:
- Think in structured governance terms.
- Escalate correctly.
- Use formal control rather than emotional reaction.
- Protect the business case.
- Maintain professional authority.
These behaviours directly align with what employers expect from:
- Project Managers
- Programme Support Officers
- PMO Analysts
- Delivery Leads
- Business Change Managers
