CAPM Business Analysis Frameworks Practice Question
A business analyst has developed a working prototype for a new user interface. The prototype is used to demonstrate the workflow to stakeholders and gather feedback. Which type of requirements validation does this represent?
⚠ Common exam trap
The trap is confusing verification with validation — candidates see 'prototype' and think 'testing,' but the key phrase is 'gather feedback from stakeholders,' which is validation (right product), not verification (product built right).
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
✓
Validation
Validation confirms that the product meets the intended use and stakeholder needs — building the right product. Demonstrating a working prototype to stakeholders to gather feedback is a classic validation activity because it checks whether the requirements actually solve the business problem. Verification, by contrast, checks that the product was built correctly according to specifications.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Validation
Why this is correct
Validation confirms the built product meets stakeholder needs and intended use. Demonstrating a working prototype to stakeholders and gathering their feedback tests whether the artefact is fit for purpose, which is validation rather than verification against specifications.
- ✗
Quality assurance
Why it's wrong here
Quality assurance concerns process conformance and defect prevention, not eliciting stakeholder feedback on a prototype. It is tempting because QA underpins validation activities, but it would be the answer if the question asked how requirements are checked against defined standards rather than demonstrated for stakeholder agreement.
- ✗
Peer review
Why it's wrong here
Peer review validates requirements through structured inspection by colleagues, not through stakeholder interaction with a working prototype. It is tempting because reviews also verify requirements, but peer review would be correct where documented requirements are examined for defects before a prototype exists.
- ✗
Verification
Why it's wrong here
Verification confirms the product was built correctly against specifications; demonstrating a prototype to stakeholders to elicit feedback is validation, confirming the right product was built. Verification suits inspection and testing against documented requirements, not stakeholder walkthroughs.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 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 PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.