Certified Business Analysis Professional ( CBAP) CBAP Exam Questions

Scope is the important factor that the BA needs to understand to ensure the workshop remains focused on the topic in question. Scope is the boundary or extent of the business analysis effort, which defines what is included and excluded from the change initiative. Scope also provides the contex t and direction for the requirements elicitation and analysis activities. By understanding the scope, the BA can plan and facilitate the workshop effectively, and avoid any irrelevant, out-of-scope, or conflicting discussions or issues. The other options a re not the best answers, as they are not as critical as scope for keeping the workshop focused, although they may be related to the topic in question. For example, future state is the desired outcome of the change initiative, assets are the resources or ca pabilities of the enterprise, and risk register is the document that records the identified risks and their responses.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

The BA needs to perform a root cause analysis to analyze the performance of the application and provide recommendations. A root cause analysis is a technique that involves identifying and addressing the underlying causes of a problem or an issue, rather than the symptoms or the effects. A root cause analysis can help the BA to find out why the solution implemented three months ago has decreased performance as the volume of transactions has increased, and to propose and implement appropriate solutions to improve the performance and prevent the problem from recurring. The other options are not the best actions for the BA to take, as they are more suitable for different purposes, such as measuring the per formance, evaluating the alternatives, or reviewing the existing metrics, rather than finding the root cause of the problem.  References :  Task: Assessing Solution Limitations ,  CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition ,  BABOK Guide

 The BA could have assessed the current state and stakeholder needs to prevent this situation. The current state is the description of the existing situation, including the problems, opportunities, capabilities, and constraints of the organization and its stakeholders. The stakeholder needs are the expectations, preferences, and requirements of the stakeholders that are relevant to the change initiative. By assessing the current state and stakeholder needs, the BA could have identified and documented the existing report “Consolidated Sales by Customer” as a requirement, and en sured that it was not affected or replaced by the new report “Customer Sales by Date”. The BA could have also verified and validated that the new report met the stakeholder needs and did not cause any negative impacts or trade-offs. The other options are n ot the best answers, as they are more related to the evaluation of the solution or the organization, rather than the identification and management of the requirements.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

 Business or technical risk is a requirements prioritization approach that involves ranking the requirements based on the potential negative consequences or uncertainties associated with their implementation or non-implementation. This approach can help to identify and mitigate the most critical risks early in the project and reduce the likelihood of project failure. Busi ness or technical risk can be assessed by considering factors such as the impact on the business value, the feasibility of the solution, the complexity of the requirements, the dependencies among the requirements, the volatility of the requirements, and th e stakeholder satisfaction.  Business or technical risk is one of the common criteria for requirements prioritization, as it helps to balance the benefits and costs of the requirem ents 1 2 3 4 .  References :  1 : Requirement prioritiza tion 3   2 : The Ultimate Guide to Requirements Prioritization 4   3 : Business Analysis Techniques: Prioritizing Requirements 5   4 : Requirements Prioritization: How to Prioritize Requirements

Interface analysis is a technique that identifies and specifies the information that is exchanged between systems or system components. It defines the communications protocol, data format, and timing of the information exchange. Interface analysis is useful for designing and documenting the interactions between the PS and other systems. It can also help to identify potential issues or risks related to the integration of the systems.

Vertical prototyping is a technique that creates a working model of one or more aspects of a solution, such as the user interface, functionality, or performance. It is used to validate the requirements and design of the solution, and to obtain feedback from stakeholders. It is not directly related to defining the communications protocol between the systems.

Concept modelling is a technique that defines the terms and concepts relevant to a domain or a problem. It establishes a common vocabulary and understanding of the domain among the stakeholders. It is not focused on the technical details of the system interactions.

System analysis is a broad term that refers to the process of studying and understanding the current or desired state of a system. It involves identifying the system components, functions, inputs, outputs, and relationships. It is not a specific technique for defining the communications protocol between the systems.  References :

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 402-403, 414-415, 420-421, 424-425.

[Business Analysis for Practitioners: A Practice Guide], Chapter 5: Requirements Analysis and Design Definition, pp. 123-124, 133-134, 140-141, 144-145.