IIBA Updated CBAP Exam Questions and Answers by jaxxon

Relaying upper management support to stakeholders is a way to reduce employee discontent and resistance to change. This can help the employees feel more confident and secure about the change initiative, as they perceive that the leaders are committed and supportive of the change. It can also help the employees understand the vision and goals of the change, and how it aligns with the organizational strategy and values. By communicating the benefits and rationale of the change, and addressing the concerns and fears of the employees, the BA can foster a positive and collaborative attitude towards the change among the stakeholders. References:

Emotional Reactions to Change in the Workplace, CMI

Reactions to Change in an Organization, Wonder

IIBA BABOK Guide, Section 5.5, Assess Organizational Readiness

 In the context of risk assessment, the impact of a risk is often calculated by multiplying the Probability of Occurrence (POC) with the Cost of Impact. For each risk in this scenario:

Natural disasters: 0.2 * 15,000 = 3,000

Power surges: 0.5 * 20,000 = 10,000

Human errors: 0.9 * 3,000 = 2,700

System security: 0.4 *16,000 =6,400

Power surges have the highest negative impact to value at $10,000.

References: The calculation is based on standard risk assessment practices which involve evaluating both the probability and impact of risks to prioritize them effectively; as per Business Analysis Professional (CBAP) learning documents or resources

 A fishbone diagram is a technique that helps identify, explore, and display the possible causes of a specific problem or quality characteristic. It can also be used to analyze the root causes of a problem or a gap between the current and desired states of a solution. By using a fishbone diagram, the BA can understand the reason why the performance of the solution does not meet the expected benefits and identify potential corrective actions. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 10: Solution Evaluation, page 393

Business Analysis Body of Knowledge (BABOK ®) Guide, Version 3, Section 10.23: Fishbone Diagrams, page 382-383

A governance approach is a technique that helps to define and establish the roles, responsibilities, authorities, and decision-making processes for the business analysis work. A governance approach identifies the stakeholders who have the power and influence to approve, reject, or modify the requirements or the solution, and the criteria and mechanisms for obtaining their approval. A governance approach can help the BA to identify the stakeholder who can approve access to the database, as it can specify who owns the database, who has the authority to grant or deny access, and what are the steps and procedures to request and obtain access. A solution scope is a technique that helps to define the boundaries and context of the solution. A solution scope identifies the elements that are within the scope, the elements that are out of scope, and the interfaces and interactions between the elements. A solution scope can help the BA to clarify the objectives and requirements of the solution, but it does not identify the stakeholder who can approve access to the database. A requirements architecture is a technique that helps to organize and structure the requirements into a coherent and consistent framework. A requirements architecture defines the relationships, dependencies, and hierarchies among the requirements, and the level of detail and abstraction of each requirement. A requirements architecture can help the BA to manage the complexity and traceability of the requirements, but it does not identify the stakeholder who can approve access to the database. A change strategy is a technique that helps to plan and manage the changes to the requirements or the solution throughout the project lifecycle. A change strategy defines the roles and responsibilities, the criteria and procedures, the tools and techniques, and the documentation and communication for handling the changes. A change strategy can help the BA to ensure that the changes are properly identified, analyzed, approved, implemented, verified, and tracked, but it does not identify the stakeholder who can approve access to the database. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.14: Governance Approach, p. 516-517; Section 10.42: Scope Modeling, p. 554-556; Section 10.41: Requirements Architecture, p. 553-554; Section 10.11: Change Control Process, p. 510-512.