PRINCE2F PRINCE2 Practices Practice Question
A project's Senior User requests a change to the product specification after the product baseline has been approved. What should the Project Manager do first?
⚠ Common exam trap
PRINCE2F often tests the misconception that baselines are immutable or that Senior Users can approve changes, when in fact all changes must go through the Issue Register and impact assessment.
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
✓
Log the request in the Issue Register as a Request for Change and assess the impact
According to PRINCE2, any change to a baselined product must be managed via a Request for Change (RFC). The Project Manager should first log the request in the Issue Register and then assess its impact on the project's business case, plans, and risks before escalating to the Change Authority.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Inform the Senior User that changes are not allowed after baseline approval
Why it's wrong here
Baseline approval does not forbid changes; the request must enter the PRINCE2 change control procedure, so the Project Manager should log it in the Issue Register and obtain an impact assessment. Refusing outright is tempting because baselines freeze the specification, and that stance would be correct only where the project board has formally closed change control.
- ✓
Log the request in the Issue Register as a Request for Change and assess the impact
Why this is correct
Under PRINCE2, any proposed change after baseline approval must first be captured as a Request for Change in the Issue Register, then assessed for impact before the Change Authority decides. Raising it formally preserves the change control process rather than amending the specification directly.
- ✗
Reject the request because the baseline is already approved
Why it's wrong here
Rejecting outright ignores PRINCE2's change control process: the request must be logged, assessed for impact on the baseline, and escalated to the Change Authority. It is tempting because baselines exist to prevent uncontrolled scope creep, and rejection would be right only if the change fell outside the project mandate or the Change Authority had already refused it.
- ✗
Approve the request as it comes from the Senior User
Why it's wrong here
The Senior User's authority covers benefits and user requirements, not the project baseline; approval must follow the Change Authority's assessment of impact on cost, time and scope. It is tempting because the Senior User owns the business case and represents user interests, and would legitimately approve changes within a delegated change budget.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PRINCE2F question from scratch — 1,189 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.