mediumMultiple Choice
CISA Implementing a new procurement system Practice Question
A company is implementing a new procurement system. The project team is considering using a rapid application development (RAD) methodology. Which of the following is a potential risk of using RAD?
⚠ Common exam trap
Many candidates assume RAD reduces stakeholder involvement due to its fast pace, but in reality RAD demands more frequent and active stakeholder participation to validate prototypes and provide feedback.
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
✓
Inadequate documentation
RAD prioritizes speed and iterative prototyping over formal documentation. Because the focus is on quickly delivering working software through user feedback and short development cycles, comprehensive documentation is often neglected or produced after the fact, leading to inadequate records for maintenance, auditing, and compliance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Inadequate documentation
Why this is correct
RAD prioritises rapid prototyping and iterative user feedback over formal deliverables, so written specifications and design records are often minimal or skipped. That directly creates the risk of inadequate documentation, leaving insufficient records for future maintenance, audit or knowledge transfer once the project closes.
- ✗
Reduced stakeholder involvement
Why it's wrong here
RAD depends on continuous, intensive user collaboration through workshops and iterative prototypes, so stakeholder involvement increases rather than drops. Reduced involvement is the risk associated with waterfall-style phases, where users are consulted mainly at requirements sign-off and acceptance.
- ✗
Longer development time
Why it's wrong here
RAD compresses delivery through iterative prototyping and timeboxing, so schedules shorten rather than lengthen. Longer development time characterises sequential waterfall projects with heavy upfront specification; RAD's recognised risks concern scope creep and weak architectural discipline instead.
- ✗
Difficulty in prototyping
Why it's wrong here
Prototyping is RAD's core mechanism, not its difficulty; the methodology is built around quickly building and refining working models. Difficulty arises where user availability is limited or requirements are unstable, but the technique itself makes prototyping routine rather than problematic.
Go deeper
Related to this question
About these practice questions
This CISA question is part of Courseiva's 934-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 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.