PRINCE2F PRINCE2 Practices Practice Question
In the Change practice, what is the purpose of a Product Status Account?
⚠ Common exam trap
PRINCE2F often tests the distinction between the Product Status Account (a report on product status) and the Configuration Item Record (the detailed record of a product), and candidates confuse reporting with record-keeping.
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
✓
To report on the current status of one or more products
In PRINCE2's Change practice, a Product Status Account is a report that provides information on the current status of one or more products — for example, their version, status (draft, approved, baselined), and any changes applied. It is a reporting/visibility artifact, not a record-keeping or authorization mechanism. It answers 'what state are these products in right now?' for the project board or 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.
- ✗
To record configuration item records
Why it's wrong here
Configuration item records live in the Configuration Item Record itself, which holds version, variant and status detail per product. The Product Status Account summarises the status of products across a stage or project. It is tempting because both relate to configuration management, but recording individual items is not its purpose.
- ✓
To report on the current status of one or more products
Why this is correct
The Product Status Account reports the current status of one or more products, detailing their state, version and history. This satisfies the Change practice's need to establish which products are affected by a change before assessing it.
- ✗
To track issues
Why it's wrong here
Issues are recorded in the Issue Register, which captures problems, concerns and change requests; the Product Status Account reports the status of products, not issues. It is tempting because both inform change control decisions, but tracking issues is the Issue Register's defined purpose.
- ✗
To authorize changes to products
Why it's wrong here
Authorising changes is the Change Authority's responsibility, exercised through change control, not a Product Status Account. It is tempting because the account feeds status information into that decision. Its actual purpose is reporting the status of products, not granting authority to alter them.
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 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.