mediumMultiple Choice
CISA Practice Question: A project team is using a prototyping approach…
A project team is using a prototyping approach for a new system. Which of the following is the BEST control to ensure the prototype accurately reflects user needs?
⚠ Common exam trap
It's easy for candidates to confuse regression testing (option D) with validation of user needs, but regression testing only ensures existing features still work, not that the prototype matches user expectations.
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
✓
Involve users in each iteration and obtain formal sign-off.
In prototyping, iterative user involvement with formal sign-off at each iteration ensures that evolving requirements are captured and validated continuously. This control directly verifies that each prototype increment aligns with user needs before proceeding, reducing the risk of building a system that fails to meet expectations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Conduct a post-implementation review.
Why it's wrong here
A post-implementation review happens after the system is live, too late to correct the prototype's alignment with user needs during development. It suits assessing realised benefits and lessons learned, whereas ensuring prototype accuracy requires user validation at each iteration.
- ✓
Involve users in each iteration and obtain formal sign-off.
Why this is correct
Prototyping succeeds only when users review each iteration and formally accept the evolving design, because requirements emerge through that feedback loop. Continuous user involvement with sign-off keeps the prototype aligned to actual business needs rather than developer assumptions, satisfying the accuracy constraint.
- ✗
Require the project sponsor to approve the final design.
Why it's wrong here
Sponsor approval confirms funding and business alignment, not that the prototype reflects the users' actual requirements. It is appropriate for authorising scope and budget, but user needs are validated by the users themselves reviewing each prototype iteration, not by executive sign-off.
- ✗
Perform regression testing after each prototype iteration.
Why it's wrong here
Regression testing verifies that changes have not broken existing functionality; it does not gather user feedback on whether the prototype meets their needs. It would be correct when validating stability after code changes, but prototype accuracy depends on iterative user review and sign-off of requirements.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CISA question from scratch — 934 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CISA practice question is part of Courseiva's free ISACA 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 CISA exam.