Deal of The Day! 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

IIBA CCBA Exam - Topic 6 Question 129 Discussion

A business analyst (BA) is eliciting requirements for a pharmaceutical distribution company with an expansion plan across many states, each with its own tools and methods. To make the requirements as reusable as possible, what should the BA do?
A) Describe the requirements at a high level of abstraction.
B) Provide details for the requirements.
C) Limit the relationships between requirements.
D) Make specific references to applications or departments.

IIBA CCBA Exam - Topic 6 Question 129 Discussion

Actual exam question for IIBA's CCBA exam
Question #: 129
Topic #: 6
[All CCBA Questions]

A business analyst (BA) is eliciting requirements for a pharmaceutical distribution company with an expansion plan across many states, each with its own tools and methods. To make the requirements as reusable as possible, what should the BA do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Comprehensive and Detailed To makerequirements reusable, they must beabstracted from specific tools, applications, or regions. TheBABOK Guide (Chapter 5.3 - Specify and Model Requirements)suggests thathigh-level abstraction ensures that requirements remain applicable across different locations. Adding too many specifics limits adaptability and reuse.


by Alex at Jun 27, 2026, 05:25 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Rory
2 days ago
Yes, we need a framework that can grow with the company.
upvoted 0 times
...
Josphine
7 days ago
Exactly! A keeps it broad and applicable everywhere.
upvoted 0 times
...
Jacki
12 days ago
D is too specific. It won't work across all states.
upvoted 0 times
...
Eleonora
18 days ago
C seems risky. Limiting relationships might cause issues later.
upvoted 0 times
...
Bea
23 days ago
True, but too many details can limit adaptability.
upvoted 0 times
...
Marica
28 days ago
But what about B? Details can help clarify requirements.
upvoted 0 times
...
Rory
1 month ago
I agree, A makes sense. It keeps things flexible for different states.
upvoted 0 times
...
Josphine
1 month ago
I think A is the best choice. High-level abstraction helps in reusability.
upvoted 0 times
...
Jamika
1 month ago
I think A) is right, but B) shouldn't be ignored completely.
upvoted 0 times
...
Crista
2 months ago
C) makes sense. Keeping relationships simple can help with clarity.
upvoted 0 times
...
Kayleigh
2 months ago
Surprised that anyone would choose D). That limits flexibility!
upvoted 0 times
...
Lilli
2 months ago
I disagree, B) is more important. Details matter for implementation.
upvoted 0 times
...
Phuong
2 months ago
A) is definitely the way to go! High-level abstraction helps with reusability.
upvoted 0 times
...
Clarinda
2 months ago
Making specific references to applications or departments could limit reusability, right? I think we should focus on a more general approach instead.
upvoted 0 times
...
Kirk
2 months ago
Limiting relationships between requirements seems risky; I feel like they need to be interconnected to make sense, but I can't recall the exact reasoning.
upvoted 0 times
...
Stacey
3 months ago
I remember a practice question where we had to decide between high-level and detailed requirements, and I think high-level was favored for broader applicability.
upvoted 0 times
...
Lavelle
3 months ago
I think describing the requirements at a high level of abstraction makes sense for reusability, but I'm not entirely sure if that's the best approach.
upvoted 0 times
...

Save Cancel