New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

GAQM CBAF-001 Exam - Topic 4 Question 72 Discussion

Actual exam question for GAQM's CBAF-001 exam
Question #: 72
Topic #: 4
[All CBAF-001 Questions]

Which of the following requirements elicitation techniques is ineffective at defining the future requirements of a system?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Earleen at Jul 09, 2025, 12:28 PM

Limited Time Offer

25%

Off

Get Premium CBAF-001 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Loren
2 months ago
Wait, are we saying shadowing is ineffective? That seems off!
upvoted 0 times
...
Carman
2 months ago
Workshops can be hit or miss, but they usually gather good insights.
upvoted 0 times
...
Aliza
3 months ago
I think prototyping is super effective for future requirements!
upvoted 0 times
...
Lorrie
3 months ago
Scenario analysis is great for exploring future possibilities.
upvoted 0 times
...
Janine
3 months ago
Shadowing is often overlooked but really helps understand user needs.
upvoted 0 times
...
Denae
3 months ago
Scenario analysis seems like it could be useful, but I vaguely recall something about shadowing being less effective for future requirements.
upvoted 0 times
...
Rozella
4 months ago
I feel like prototyping is often used to clarify requirements, so that can't be the right answer either.
upvoted 0 times
...
Demetra
4 months ago
I'm a bit unsure, but I think shadowing might not really help in defining future requirements since it's more about observing current processes.
upvoted 0 times
...
Dianne
4 months ago
I remember we discussed that workshops are usually effective for gathering requirements, so I don't think it's A.
upvoted 0 times
...
Ricki
4 months ago
I think the key here is to focus on techniques that allow you to imagine and test out future scenarios, rather than just documenting existing processes. Based on that, I'd say prototyping is probably the most effective approach for defining future requirements.
upvoted 0 times
...
Erick
4 months ago
Shadowing seems like it would be the least effective technique for defining future requirements. It's more focused on observing current user behaviors and workflows, rather than exploring new possibilities for the future system.
upvoted 0 times
...
Buck
4 months ago
Hmm, I'm a bit unsure about this one. I know workshops and prototyping are both common requirements elicitation techniques, but I can't quite remember which one is less effective for future requirements. I'll have to think this through carefully.
upvoted 0 times
...
Ramonita
5 months ago
I'm pretty confident that prototyping is the most effective technique for defining future requirements. Workshops and scenario analysis are good for eliciting current needs, but prototyping lets you explore and test potential future features.
upvoted 0 times
...
Chi
6 months ago
What kind of crazy question is this? Everyone knows the best way to define future requirements is to consult a crystal ball and a tarot deck. Duh.
upvoted 0 times
...
Ciara
6 months ago
I'm gonna have to agree with Marshall on this one. Shadowing is just observing the present, not defining the future. That's like trying to drive while only looking in the rearview mirror.
upvoted 0 times
Lai
5 months ago
I think Marshall makes a good point about shadowing not defining the future requirements.
upvoted 0 times
...
...
Mari
7 months ago
Haha, I bet the answer is A. Workshops are like herding cats. Good luck getting anything useful out of that chaos.
upvoted 0 times
...
Marshall
7 months ago
I'm gonna have to go with D. Shadowing is just watching someone else do their job - how's that supposed to help us figure out what we need in the future?
upvoted 0 times
Ming
6 months ago
A) Workshops.
upvoted 0 times
...
...
Eulah
7 months ago
Hmm, I see your point. Maybe I should reconsider my answer.
upvoted 0 times
...
Daniel
7 months ago
I agree with Curtis, prototyping can be effective in defining requirements.
upvoted 0 times
...
Curtis
7 months ago
But prototyping helps visualize the future system.
upvoted 0 times
...
Eulah
8 months ago
I disagree, I believe it's D) Shadowing.
upvoted 0 times
...
Suzi
8 months ago
Definitely not B. Prototyping is super effective for defining future requirements. How else would we know what the users really want?
upvoted 0 times
Beckie
7 months ago
D) Shadowing.
upvoted 0 times
...
Louvenia
7 months ago
C) Scenario analysis.
upvoted 0 times
...
Wenona
7 months ago
A) Workshops.
upvoted 0 times
...
...
Curtis
8 months ago
I think the answer is B) Prototyping.
upvoted 0 times
...

Save Cancel