PRINCE2F PRINCE2 Practices Practice Question
Which TWO statements correctly describe the difference between a Request for Change (RFC) and an Off-specification?
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
✓
An Off-specification is a failure to meet a requirement; an RFC is a suggestion to add or change a requirement.
Options A and B are correct because they accurately capture the PRINCE2 distinction: an RFC is a proposal to add or modify a requirement (something not currently specified), while an Off-specification reports that a required product is missing, incorrect, or otherwise failing to meet its agreed specification. Option C is wrong because neither an RFC nor an Off-specification has an automatic, predetermined effect on the change budget; financial impact is assessed case by case. Option D is wrong because an Off-specification is not automatically accepted—it must be assessed and can be rejected, deferred, or handled via a change, just as an RFC can be rejected by 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.
- ✓
An Off-specification is a failure to meet a requirement; an RFC is a suggestion to add or change a requirement.
Why this is correct
An Off-specification records a product failing to meet an already agreed requirement, whereas an RFC proposes altering or adding to those requirements. This distinction separates conformance failure from scope change, which PRINCE2 handles through different tolerance and approval routes.
- ✓
An RFC proposes a change that is not currently specified; an Off-specification indicates a required product is missing or incorrect.
Why this is correct
An RFC seeks approval to modify something not yet baselined or specified, while an Off-specification reports that a required product is missing, incomplete or incorrect. The axis of difference is proposed change versus identified non-conformance against agreed requirements.
- ✗
An RFC always results in a change budget increase; an Off-specification always results in a decrease.
Why it's wrong here
Neither artefact mechanically alters the change budget in a fixed direction; an RFC may be approved without extra funds, and an Off-specification may be accepted within tolerance. It tempts because both often trigger budget review, but no such automatic increase or decrease exists.
- ✗
An RFC can be rejected by the Change Authority; an Off-specification must always be accepted.
Why it's wrong here
An Off-specification is not automatically accepted; the Project Board decides whether to approve it, so the claim that it must always be accepted is false. It tempts because RFCs genuinely can be rejected by the Change Authority, making the first half look accurate.
Go deeper
Related to this question
About these practice questions
This PRINCE2F question is part of Courseiva's 1,189-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.