The answer is scope creep due to frequent changes, along with inadequate documentation and an unclear final system specification. These three risks are common in the prototyping methodology because its iterative, user-driven nature encourages continuous feedback and rapid modifications, which can easily expand the original project boundaries without formal change control. The lack of a fixed, detailed requirements document from the outset means each new user request or visual adjustment can subtly shift the project’s scope, while the focus on building working models often sidelines the creation of thorough design records and user agreements. On the Certified Information Systems Auditor CISA exam, this concept tests your understanding of how development methodologies directly impact governance and control objectives; a common trap is confusing prototyping’s flexibility with agility, forgetting that without disciplined documentation, audit trails and maintenance suffer. To remember the core triad, think “Scope, Specs, and Paperwork”—if any of these three is missing, prototyping risks escalate.
CISA Practice Question: Information Systems Acquisition, Development and Implementation
This CISA practice question tests your understanding of information systems acquisition, development and implementation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE of the following are common risks associated with the prototyping methodology?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Lack of adequate documentation
Option B is correct because prototyping often prioritizes rapid iteration over formal documentation, leading to incomplete or outdated records of system specifications, design decisions, and user agreements. This lack of adequate documentation creates risks for maintenance, knowledge transfer, and auditability, as the final system may lack the necessary artifacts for ongoing support and compliance.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Incomplete requirements specification
Why it's wrong here
Prototyping helps clarify requirements, so this is less of a risk.
✓
Lack of adequate documentation
Why this is correct
Documentation is often overlooked in prototyping.
Related concept
Read the scenario before looking for a memorised answer.
✓
Prototype being accepted as the final production version
Why this is correct
This is a common risk if prototyping is not managed.
Related concept
Read the scenario before looking for a memorised answer.
✗
User misunderstanding of prototype limitations
Why it's wrong here
Users generally understand prototypes are not final.
✓
Scope creep due to frequent changes
Why this is correct
Frequent changes in prototyping can lead to scope creep.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse 'incomplete requirements specification' (a general risk) with a prototyping-specific risk, but the exam expects recognition that prototyping actually reduces this risk through iterative user feedback, while the three correct answers (B, C, E) are directly tied to the methodology's iterative and informal nature.
Detailed technical explanation
How to think about this question
In prototyping, the iterative cycle of 'build-evaluate-refine' can cause the prototype to evolve into a production system without formal transition controls, increasing the risk of accepting an unstable or non-scalable version as final. This is particularly dangerous in rapid application development (RAD) environments where the prototype lacks security hardening, performance tuning, and full integration testing, leading to technical debt and operational failures in production.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CISA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Information Systems Acquisition, Development and Implementation — This question tests Information Systems Acquisition, Development and Implementation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Lack of adequate documentation — Option B is correct because prototyping often prioritizes rapid iteration over formal documentation, leading to incomplete or outdated records of system specifications, design decisions, and user agreements. This lack of adequate documentation creates risks for maintenance, knowledge transfer, and auditability, as the final system may lack the necessary artifacts for ongoing support and compliance.
What should I do if I get this CISA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.