PRINCE2F Practice Question: Overview of PRINCE2 and the project environment

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 always raised by the Project Manager

  Why it's wrong here

  An Off-specification may be raised by anyone, including team members or suppliers, not solely the Project Manager. It is tempting because the Project Manager often escalates them, but the defining difference from a Request for Change is that an Off-specification covers something the project should deliver but currently cannot.

• ✗

  A Request for Change is always urgent; an Off-specification is not

  Why it's wrong here

  Urgency is not a defining criterion; both are handled through the same change control approach, and either can be urgent. It is tempting because changes are often perceived as time-critical, but the real distinction is that a Request for Change proposes altering baselined products, whereas an Off-specification flags a failure to meet an agreed requirement.

• ✗

  There is no difference

  Why it's wrong here

  A Request for Change proposes an alteration to baselined products or scope, whereas an Off-specification reports that agreed tolerances have already been breached. Claiming no difference ignores that one is proactive and the other reactive. It tempts candidates who see both as change-related paperwork, yet they are distinct PRINCE2 issue types requiring different handling.

• ✓

  A Request for Change proposes a modification; an Off-specification identifies a gap in requirements

  Why this is correct

  An RFC proposes modifying a baselined product, whereas an Off-specification records where a product fails to meet its agreed requirements. This separates proposed change from identified non-conformance, satisfying the stem's requirement to distinguish the two PRINCE2 change control types.

Go deeper

Related to this question