Free Practice Questions for IIBA CBAP Exam

 A change-driven approach to business analysis is one that adapts to the changing needs and priorities of the stakeholders and the business environment. It focuses on delivering business value in short iterations, rather than following a fixed and detailed plan. A change-driven approach is often associated with agile methodologies, such as Scrum, Kanban, or XP, which emphasize collaboration, feedback, and continuous improvement. A change-driven approach can help business analysts respond to uncertainty, complexity, and ambiguity, and deliver solutions that meet the customer’s expectations and satisfaction. References:

Defining Business Analysis, section 1.3.2, page 7

How to Choose the Right Business Analysis Approach, paragraph 4

Business Analysis Approach, paragraph 2

The Agile Business Analysis Approach Means…, paragraph 1

Defining the Business Analysis Approach in 2023, paragraph 2

Mitigation is not a category of risk tolerance, but rather a strategy for reducing the probability or impact of a risk. Risk tolerance refers to the degree of uncertainty that a stakeholder is willing to accept in relation to the achievement of the project or solution objectives. According to the BABOK® Guide1, there are three categories of risk tolerance associated with the stakeholders: risk-averse, risk-neutral, and risk-seeking. These categories are based on how much risk the stakeholders can tolerate and how they perceive the potential rewards of taking risks.

Risk-averse stakeholders prefer to avoid risks or minimize their exposure. They tend to choose safer options that have lower returns but higher certainty. They may require more analysis and evidence before making decisions or approving requirements.

Risk-neutral stakeholders are indifferent to risks and rewards. They base their decisions on the expected value of the outcomes, regardless of the uncertainty involved. They may accept higher risks if they are compensated by higher returns, or lower risks if they are accompanied by lower returns.

Risk-seeking stakeholders prefer to take risks or maximize their exposure. They tend to choose riskier options that have higher returns but lower certainty. They may be willing to accept lower levels of analysis and evidence before making decisions or approving requirements.

References:

CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Requirements Analysis and Design Definition, task 5.1: Prioritize Requirements

BABOK® Guide, page 33, section 4.2.1: Prioritize Requirements

Risk Tolerance - Overview, Factors, and Types of Tolerance

Applying stakeholder risk tolerance strategies in business

 A business analysis communication plan is a document that describes how the business analyst will communicate with the stakeholders, including the stakeholder groups, communication needs, level of formality, frequency, format, and methods of communication. It is one of the outputs of the business analysis planning and monitoring knowledge area, and it helps to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis process and deliverables. A business analysis communication plan is not the same as a project communication plan, which covers the overall communication needs of the project and is typically created by the project manager. A business analysis communication plan focuses on the specific communication needs related to the business analysis activities and requirements. References:

IIBA BABOK Guide v3, p. 36, 38, 40, 42

How to Create a Stakeholder Management Plan Smartsheet

CBAP 150 Practice Questions Flashcards, Question 5

How To Create an Effective Stakeholder Communication Plan

Stakeholders are individuals or groups who have an interest in the outcome of a project and can influence its success. Stakeholders can be classified into different categories based on their roles, responsibilities, and perspectives. One common way to categorize stakeholders is by using the RACI matrix, which stands for Responsible, Accountable, Consulted, and Informed. According to this matrix, the following stakeholders participate in the prioritization of requirements:

Project team: Responsible for delivering the solution that meets the requirements. They are directly involved in the prioritization process and provide input on the feasibility, effort, and risk of each requirement.

Domain subject matter expert: Consulted for their expertise and knowledge of the business domain and the needs of the end users. They provide input on the importance, value, and urgency of each requirement.

Project manager: Accountable for the overall success of the project and the alignment of the requirements with the project scope, schedule, and budget. They facilitate the prioritization process and ensure that the stakeholders reach a consensus on the priority levels.

The implementation subject matter expert is not a stakeholder who participates in the prioritization of requirements. They are Informed of the prioritized requirements and the rationale behind them, but they do not provide input or influence the prioritization process. They are responsible for implementing the solution according to the requirements and ensuring that it meets the quality standards and specifications. References:

IIBA BABOK Guide v3, p. 30, 176, 264

Five Requirements Prioritization Methods - Business Analyst Articles …

What Is Requirements Prioritization? Definition & Examples - airfocus

Business analysts : How to prioritize requirements - Adaptive US

[5 Popular Requirements Prioritisation Techniques]

This question is based on a case study that compares four scenarios for implementing a new system for a bank. The case study provides the following information about the duration of each scenario:

Scenario 1: 6 months

Scenario 2: 9 months

Scenario 3: 10 months

Scenario 4: 7 months

The question asks for the time difference in days between the shortest and longest implementation. The shortest implementation is Scenario 1, which is 6 months or 180 days. The longest implementation is Scenario 3, which is 10 months or 300 days. Therefore, the time difference in days is 300 - 180 = 120 days. References: The case study is available in the CBAP® Exam Sample Questions and Exam Blueprint document1. The answer is also verified by the CBAP® Exam Answer Key document2. Both documents are accessible from the IIBA® website3.

A performance assessment is a business analysis artifact that evaluates the effectiveness and efficiency of the business analysis work. It can be used to identify and document the improvement areas for the next piece of analysis work, as well as to measure the value delivered by the business analysis outcomes. A performance assessment can include metrics, indicators, targets, and feedback mechanisms that help the BA to monitor and improve the business analysis performance12. References:

1: BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Performance Improvements

2: Tasks Mapped To Artifacts(https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx)

Based on the table in the image, the total cost for each company over the three years can be calculated by adding the Year 0 license costs, Years 1 and 2 total license costs, and implementation costs. For Company A, the total cost is $323,458 (Year 0) + $270,092 (Years 1 and 2) + $28,500 (Phase Ia) + $55,000 (Phase Ib) + $121,500 (Phase 2) = $798,550. For Company B, it’s $373,555 (Year 0) + $202,056 (Years 1 and 2) + ($1.500 150 days of implementation)= $578611 which is less than the insurance company’s maximum budget of $310000. For Company C it’s = ($400244+$214096+($31.50159))= $695439 which exceeds the budget. References: The answer is derived from a direct calculation based on the provided information in the image and does not reference specific CBAP learning documents or resources.

 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

The BA should handle the change request by adding the feature to the product backlog for future prioritization. The product backlog is a list of features, functions, and requirements that are desired for the solution, but have not yet been planned or implemented. The product backlog is constantly updated and prioritized by the product owner, who represents the voice of the customer and the stakeholders. The BA should collaborate with the product owner to capture and document the change request and add it to the product backlog. The product owner will then decide when and how to prioritize the feature for the next iteration or release, based on the value and urgency of the feature and the feedback from the stakeholders. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 90-91

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 58-59

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.6: Communicate Business Analysis Information, p. 124-125

The other dimension that the feasibility analysis and the resource analysis should indicate is the timeline for instituting the change. The timeline is the schedule or plan that specifies the start and end dates, the milestones, the dependencies, and the deliverables for the change initiative. The timeline helps to estimate the duration, effort, and cost of the change, as well as to monitor and control the progress and performance of the change. The timeline also helps to communicate the expectations and commitments of the stakeholders and the change agents, and to manage the risks and issues that may arise during the change. The other options are not the other dimensions that the analysis should indicate, as they are either part of the existing or required resources, or the outcomes or agreements of the change. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Strategy Analysis, Section 5.3: Define Change Strategy, p. 215-216

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.3: Define Change Strategy, p. 114-115