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 CBAP Exam - Topic 2 Question 109 Discussion

Actual exam question for IIBA's CBAP exam
Question #: 109
Topic #: 2
[All CBAP Questions]

A business analyst (BA) has been coordinating several meetings with stakeholders to reach consensus regarding the solution design to implement a global currency exchange system for an international bank. Consensus has not been reached yet, although BA has great communication skills and is trusted by all stakeholders. The stakeholders formally approved the business need initially.

Why is there disagreement?

Show Suggested Answer Hide Answer
Suggested Answer: C

A change control process is a technique that helps to manage the changes to the requirements or the solution throughout the project lifecycle. A change control process defines the roles and responsibilities, the criteria and procedures, the tools and techniques, and the documentation and communication for handling the changes. A change control process helps to ensure that the changes are properly identified, analyzed, approved, implemented, verified, and tracked. A change control process can help the BA to keep this situation from occurring in the future by creating a clear and consistent mechanism for managing the changes and avoiding any unauthorized or uncontrolled changes that may affect the quality or scope of the solution. A risk strategy is a technique that helps to identify, analyze, and manage the uncertainties and threats that may affect the project or the solution. A risk strategy defines the risk appetite, tolerance, and thresholds, the risk identification and assessment methods, the risk response and monitoring plans, and the risk roles and responsibilities. A risk strategy can help the BA to mitigate the potential impacts of the changes, but it does not prevent the changes from occurring. A prioritization approach is a technique that helps to rank the requirements or solution options based on their relative importance, urgency, value, or dependency. A prioritization approach defines the criteria and methods, the tools and techniques, and the roles and responsibilities for prioritizing the requirements or solution options. A prioritization approach can help the BA to determine the optimal scope and sequence of the solution delivery, but it does not control the changes to the requirements or solution options. A stakeholder engagement plan is a technique that helps to plan and manage the interactions and communications with the stakeholders throughout the project. A stakeholder engagement plan defines the stakeholder identification and analysis, the stakeholder communication and collaboration methods, the stakeholder feedback and approval mechanisms, and the stakeholder roles and responsibilities. A stakeholder engagement plan can help the BA to ensure that the stakeholders are informed, engaged, and satisfied with the project progress and outcomes, but it does not regulate the changes requested by the stakeholders.Reference:BABOK Guide v3, Chapter 10: Techniques, Section 10.11: Change Control Process, p. 510-512; Section 10.51: Risk Analysis and Management, p. 567-569; Section 10.38: Prioritization, p. 550-552; Section 10.24: Focus Groups, p. 532-533.


by Chaya at Mar 21, 2025, 07:27 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Barney
3 months ago
Incorrectly traced requirements could definitely be a factor too!
upvoted 0 times
...
Carol
3 months ago
Wait, are we sure they even need more solution alternatives?
upvoted 0 times
...
Jacklyn
4 months ago
I’m not so sure about that, maybe it’s just unclear approval authority?
upvoted 0 times
...
Willodean
4 months ago
Totally agree, that’s usually the case in these situations.
upvoted 0 times
...
Sabine
4 months ago
I think the requirements are interpreted differently by each stakeholder.
upvoted 0 times
...
Desiree
4 months ago
I recall a practice question about generating more alternatives when there's disagreement. It makes sense that option D could apply here too, but I'm not convinced it's the main issue.
upvoted 0 times
...
Louann
4 months ago
I feel like the approval authority could definitely play a role in this situation. If it's unclear, stakeholders might hesitate to agree on the solution. So, option C could be a strong contender.
upvoted 0 times
...
Mariann
5 months ago
I'm not entirely sure, but I think if the requirements were traced incorrectly, it could cause confusion among stakeholders. That makes me lean towards option B.
upvoted 0 times
...
Ira
5 months ago
I remember studying that different interpretations of requirements can lead to disagreements, so option A seems likely.
upvoted 0 times
...
Jamal
5 months ago
I'm feeling pretty confident about this one. The key seems to be figuring out if the requirements are being traced properly.
upvoted 0 times
...
Titus
5 months ago
Okay, I think I've got a strategy here. I'll focus on identifying any gaps in the solution alternatives that have been generated so far.
upvoted 0 times
...
Kerry
5 months ago
Hmm, I'm a bit confused on this one. I'll need to think through the approval process and whether that could be causing the disagreement.
upvoted 0 times
...
Alonzo
6 months ago
This seems like a tricky one. I'll need to carefully consider the different stakeholder perspectives and how the requirements might be interpreted differently.
upvoted 0 times
...
Kandis
10 months ago
Wait, so they all agreed on the business need, but can't agree on the solution? Sounds like a classic case of 'the devil's in the details'.
upvoted 0 times
Becky
9 months ago
D) More solution alternatives need to be generated.
upvoted 0 times
...
Daniel
9 months ago
C) The approval authority for the solution is unclear.
upvoted 0 times
...
Franklyn
9 months ago
B) The requirements are incorrectly traced.
upvoted 0 times
...
Jani
10 months ago
A) The requirements are interpreted differently by each stakeholder.
upvoted 0 times
...
...
Izetta
10 months ago
I've got to go with A. Stakeholders interpreting requirements differently? That's like a certifiable case of 'too many cooks in the kitchen'.
upvoted 0 times
...
Lacresha
10 months ago
I'm leaning towards D. Maybe the stakeholders just need more solution options to choose from. Sometimes a fresh perspective can help break a deadlock.
upvoted 0 times
Kristofer
10 months ago
C: That could be a good approach. It might help us find a solution that everyone can agree on.
upvoted 0 times
...
Shawnda
10 months ago
B: Maybe we should brainstorm some new ideas to present to the stakeholders.
upvoted 0 times
...
Nydia
10 months ago
A: I think you're right. More solution alternatives could definitely help.
upvoted 0 times
...
Estrella
10 months ago
C) The approval authority for the solution is unclear.
upvoted 0 times
...
Reiko
10 months ago
B) The requirements are incorrectly traced.
upvoted 0 times
...
Alpha
10 months ago
A) The requirements are interpreted differently by each stakeholder.
upvoted 0 times
...
...
Jess
11 months ago
Maybe we should generate more solution alternatives to address the disagreement.
upvoted 0 times
...
Lacresha
11 months ago
I agree with Emmanuel, it's important to ensure everyone is on the same page with the requirements.
upvoted 0 times
...
Vivienne
11 months ago
Ooh, C is an interesting one. If the approval authority is unclear, that could be the root of the problem. Everyone's probably trying to push their own agenda without a clear decision-maker.
upvoted 0 times
Stephaine
10 months ago
C) The approval authority for the solution is unclear.
upvoted 0 times
...
Annamae
11 months ago
A) The requirements are interpreted differently by each stakeholder.
upvoted 0 times
...
...
Jamey
11 months ago
I'm going with B. If the requirements aren't properly traced, it's no wonder the stakeholders can't agree on the solution. Sounds like the BA needs to do some more digging.
upvoted 0 times
...
Stephaine
11 months ago
Hmm, I think it's definitely option A. With so many stakeholders, it's not surprising that they're interpreting the requirements differently. Communication is key in these situations, but sometimes it's just not enough.
upvoted 0 times
Nieves
10 months ago
Harley: Definitely, clear communication is crucial in reaching consensus.
upvoted 0 times
...
Cordelia
10 months ago
User 3: It's important to ensure everyone is on the same page.
upvoted 0 times
...
Harley
10 months ago
User 2: Maybe more clarification is needed on the requirements.
upvoted 0 times
...
Hester
10 months ago
User 1: I agree, different interpretations can cause disagreements.
upvoted 0 times
...
Earlean
10 months ago
Vanda: Absolutely, clear communication is crucial in these situations.
upvoted 0 times
...
Louisa
10 months ago
User 3: It's important to address these differences early on to avoid delays in the project.
upvoted 0 times
...
Vanda
10 months ago
User 2: Maybe more clarification is needed to align everyone's understanding.
upvoted 0 times
...
Noel
11 months ago
User 1: I agree, option A makes sense. Different interpretations can lead to disagreements.
upvoted 0 times
...
...
Emmanuel
12 months ago
I think the disagreement is because the requirements are interpreted differently by each stakeholder.
upvoted 0 times
...

Save Cancel