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 PL
Mob_nav_barsMENU

IIBA Exam CBAP 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:

Submit Cancel
Jess
8 days ago
Maybe we should generate more solution alternatives to address the disagreement.
upvoted 0 times
...
Lacresha
10 days ago
I agree with Emmanuel, it's important to ensure everyone is on the same page with the requirements.
upvoted 0 times
...
Vivienne
11 days 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
...
Jamey
13 days 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
16 days 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
...
Emmanuel
19 days ago
I think the disagreement is because the requirements are interpreted differently by each stakeholder.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77