CBAP Exam Dumps - IIBA Certified Business Analysis Professional Questions and Answers

According to the BABOK Guide, “prioritization is the process of ranking requirements in order of importance or urgency”. However, not all requirements can be prioritized at the same time, especially if they are not stable or well-defined. In such cases, the BA should leave the priority unfilled until the requirements are clarified and agreed upon by the stakeholders. This will avoid premature decisions that may lead to rework, conflicts, or missed expectations. The BA should also communicate the rationale for leaving the priority unfilled and the criteria for assigning it later. References: BABOK Guide, Version 3, Section 6.2.4.3, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8, Page 287

According to the CBAP competencies, one of the skills required for business analysis planning and monitoring is to guide practice in performing stakeholder analysis1. Stakeholder analysis is the process of identifying and assessing the needs, interests, and influence of stakeholders on a project or initiative2. One of the outputs of stakeholder analysis is a stakeholder list, which identifies the key stakeholders and their roles, responsibilities, and expectations3. A stakeholder list can also include information on the potential risks and issues that may arise from stakeholder involvement or lack thereof4. Therefore, developing a risk plan to anticipate negative behavior from the Director of Human Resources is a valid activity that is included in performing a stakeholder analysis. This can help the team to mitigate the impact of the Director’s bitterness and resistance on the project’s success.

The other options are not included in performing a stakeholder analysis. Comparing the expertise of the Director of Human Resources to other stakeholders is not relevant to the stakeholder analysis process, as it does not help to understand the Director’s needs, interests, or influence. Recommending excluding the Director of Human Resources as a stakeholder is not a good practice, as it may create more conflict and resentment, and ignore the Director’s legitimate role and authority in the project. Implementing all of the Director of Human Resources suggestions to relieve tension is not a realistic or effective strategy, as it may compromise the quality and feasibility of the project, and disregard the needs and interests of other stakeholders. References:

• 1: CBAP Competencies - International Institute of Business Analysis
• 2: BABOK Guide v3, Section 2.2.2: Conduct Stakeholder Analysis
• 3: BABOK Guide v3, Section 2.2.2.3: Outputs
• 4: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 3: Business Analysis Planning and Monitoring, p. 83

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.

Dependencies are the relationships among requirements that indicate that one requirement is reliant on another requirement for its implementation, verification, or validation. Dependencies can influence the prioritization of requirements, as some requirements may need to be implemented before others to ensure the functionality, quality, or feasibility of the solution. In this case, the requirement ‘parsing of data’ must be implemented before other requirements, which means that it has a dependency relationship with them. Therefore, the BA has given this requirement a high priority to reflect its importance and urgency. References: Prioritization techniques in business analysis, CBAP / CCBA Certified Business Analysis Study Guide, BABOK Guide

The business analyst (BA) will create a Data Model to meet Requirement ID FE10001, as it is related to the entity classification, specifically stating “The solution shall use the CrewContactID field as a primary key.” This requirement indicates the need for structuring data and defining how data elements are related, which is typically addressed through a Data Model. References: The answer can be verified from the following sources:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 9: Data Modeling, p. 326-331.
• Business Analysis Professional (CBAP) Learning documents or resources available on IIBA’s official website and bookstore.

A collaborative approach is a type of elicitation approach that involves working with multiple stakeholders simultaneously to elicit, analyze, and validate requirements. A collaborative approach can help to complete requirements elicitation activities in a short period of time, as it can:

• Reduce the number of individual meetings and interviews that need to be conducted
• Increase the quality and quantity of information that can be gathered from different perspectives and sources
• Enhance the communication and understanding among the stakeholders and the BA
• Promote the consensus and agreement on the requirements and the solution scope
• Identify and resolve any conflicts, issues, or gaps in the requirements

Some examples of collaborative elicitation techniques are:

• Requirements workshops: A structured and facilitated session that brings together a group of stakeholders to elicit, analyze, and prioritize requirements
• Brainstorming: A technique that generates a large number of ideas or solutions from a group of stakeholders in a creative and spontaneous manner
• Focus groups: A technique that collects the opinions, preferences, and feedback of a group of stakeholders on a specific topic or issue
• Prototyping: A technique that creates a simplified or partial version of the solution to elicit, demonstrate, and validate requirements

The other options are not correct because they are not types of elicitation approaches, but rather techniques that can be used within an elicitation approach. An experiment is a technique that tests a hypothesis or an assumption by observing the results of a controlled or simulated scenario. An estimation is a technique that approximates the size, cost, duration, or effort of a project or a solution. A research is a technique that collects and analyzes information from existing sources, such as documents, reports, databases, etc.

References:

• [BABOK Guide v3], Section 4.2: Conduct Elicitation, p. 100-101
• Types of Elicitation Techniques for the Business Analyst, Blog Post, September 2018
• Elicitation Techniques Used by Business Analysts – Tips and Guidance, Blog Post, July 2023

The driver’s average throughput is 0.6 tons/hour. To deliver 100 tons of merchandise, the total hours required would be ( \frac{100 \text{ tons}}{0.6 \text{ tons/hour}} = 166.67 \text{ hours} ). If there are 15 drivers, then each driver would need to work ( \frac{166.67 \text{ hours}}{15 \text { drivers}} = 11.11 \text { hours/driver} ). However, since the options provided do not include 11, and it is not possible for a driver to work a fraction of an hour in this context, we round down to the nearest whole number which gives us option B: 9 hours per day. References: This answer and explanation are inferred from general mathematical calculations as specific references from Business Analysis Professional (CBAP) Learning documents or resources were not provided.

Mind mapping is a technique that involves creating a visual representation of information, using a central idea and branching out to related topics, subtopics, and details. Mind mapping can help the BA to identify and categorize which information is to be managed, as it allows the BA to organize, structure, and classify information in a hierarchical and logical way. Mind mapping can also help the BA to discover gaps, overlaps, and relationships among information, and to communicate information effectively to stakeholders. The other options are not the best techniques for this objective, as they are more focused on tracking the status, behavior, or appearance of items, creating a working model of a solution, or observing the actions and interactions of stakeholders. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

An activity diagram is a technique that is used to model the dynamic aspects of a system or a domain. It shows the sequence and conditions of the actions (or activities) that are performed by the actors or components involved in a business process or a use case. An activity diagram can also show the inputs, outputs, and resources required for each action, as well as the exceptions and alternative paths that may occur. An activity diagram can help to identify and analyze the business processes that need to be performed and managed in the future state of the solution. References: The answer can be verified from the following sources:

• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 9: Data Modeling, p. 326-331; Chapter 10: Data Flow Diagrams, p. 336-339; Chapter 10: Activity Diagrams, p. 340-343.
• Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 125-126, 131-132.

Option D shows the correct use of the include relationship between the three use cases. This means that the “Pass a two-factor authentication” use case is a mandatory part of both the “Change system parameters” and the “Setup new supervisor” use cases, and it always occurs whenever either of them is executed. The arrow points from the base use case to the included use case, as per the UML notation. Option C is incorrect because it uses the protect relationship, which is a non-standard extension of the UML notation. It indicates that the “Pass a two-factor authentication” use case is a security requirement for the other two use cases, but it does not specify how or when it is executed. Options A and B are incorrect because they use the extend relationship, which means that the “Pass a two-factor authentication” use case is an optional extension of the other two use cases, and it only occurs under certain conditions. This does not reflect the requirement that the two-factor authentication is mandatory for both functions. References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 424-425.
• [UML 2.5 Specification], Chapter 18: Use Cases, pp. 637-638.