Free IIBA CBAP Practice Exam with Questions & Answers | Set: 3

A work product is any output of the business analysis process that is used to communicate, document, or manage requirements1. Examples of work products include requirements documentation, interview questions and notes, meeting agendas and minutes, models, diagrams, matrices, traceability reports, and business cases2. Presentation slides are not a work product, as they are not used to capture or manage requirements, but rather to present or summarize them to an audience. Presentation slides may contain information from work products, but they are not work products themselves. References:

Work Product Definition & Meaning | Merriam-Webster Legal

Examples of ownership of work product clauses in contracts - Afterpattern

 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

 Root cause analysis is a technique that helps identify the underlying causes of failures or difficulties in accomplishing business analysis work. It involves asking a series of questions to determine the origin of a problem and the factors that contributed to it. By finding and addressing the root causes, the business analyst can prevent the problem from recurring and improve the performance of the business analysis process. References:

CBAP® Handbook, page 18, section 4.5. Manage Business Analysis Performance

BABOK® Guide, page 387, section 10.25. Root Cause Analysis

Tips for Earning a Business Analysis Certification, section 2. Understand the BABOK® Guide

 Scope modeling is a technique that can be used to establish appropriate boundaries for the solution, as it describes the essence of one or more boundaries and places components inside or outside those boundaries. Scope modeling can help to define the scope of control, change, solution, or need for the project. Scope modeling can also help to identify the in-scope and out-of-scope elements, as well as the relationships and dependencies among them. Scope modeling can provide the foundation for understanding the scope of the solution and the value it delivers to the organization12. Scope modeling can be represented as a blend of diagrams, matrices, and textual descriptions, such as context diagrams, use case models, Venn diagrams, etc134. References: 1: Scope modelling in business analysis – The Functional BA1 2: 10.41 Scope Modelling | IIBA®2 3: Business Analysis Scope Modeling Training | Netmind Course3 4: How Should a Business Analyst Define “Project Scope?”4

To calculate the break-even point, we need to compare the total costs of the internal solution and the vendor’s solution over time. The internal solution has a higher initial cost ($78,000) and a higher monthly cost ($8,765) than the vendor’s solution ($61,000 and $7,990 respectively). Therefore, the internal solution will take longer to break even with the vendor’s solution. The formula for the break-even point is:

Break-even point = (Initial cost difference) / (Monthly cost difference)

Plugging in the numbers, we get:

Break-even point = ($78,000 - $61,000) / ($8,765 - $7,990) Break-even point = $17,000 / $775 Break-even point = 21.94 months

Rounding up to the nearest whole month, we get 22 months as the break-even point. References: This question is based on the concept of financial feasibility analysis, which is part of the business analysis planning and monitoring knowledge area in the BABOK® Guide. Financial feasibility analysis is the process of comparing the costs and benefits of different solutions to determine the optimal one for the organization. One of the techniques for financial feasibility analysis is break-even analysis, which calculates the point in time when the costs of a solution equal the benefits of the solution. You can find more information about financial feasibility analysis and break-even analysis in the following sources:

BABOK® Guide, section 3.4.5.5, pages 76-77

CBAP / CCBA Certified Business Analysis Study Guide, chapter 3, pages 85-86

Certified Business Analysis Professional™ (CBAP®) | Coursera, course 2, week 3, video 3.3

Scenario and uses cases and user stories are conduct stakeholder analysis techniques that identify stakeholder roles that may serve as a useful starting point for identifying actors and roles. These techniques describe how stakeholders interact with the solution or the business process, and what their goals, needs, and expectations are. By creating scenarios and use cases and user stories, the business analyst can identify the primary and secondary stakeholders, as well as their roles and responsibilities. These techniques can also help to elicit, validate, and prioritize the requirements, as well as to communicate and collaborate with the stakeholders1234. References: 1: Scenarios, Use Cases, and User Stories1 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders2 3: Use Cases and Scenarios3 4: User Stories4

The requirements analysis processes are the activities that prioritize, organize, specify, model, verify, and validate the requirements for the solution. They ensure that analysis and implementation efforts focus on the most critical requirements that deliver the most value to the stakeholders and the organization. They also help to resolve any conflicts or inconsistencies among the requirements and the stakeholders. References:

CBAP® Handbook, page 6, section 2.4 Review the Exam Blueprint

BABOK® Guide, page 30, section 3.2 Requirements Analysis and Design Definition

CBAP / CCBA Certified Business Analysis Study Guide, page 111, chapter 5 Requirements Analysis

 An assumption is a factor that is considered to be true, real, or certain without proof or demonstration. In this case, the vendor’s belief about the hardware delivery date is an assumption because it is not verified or guaranteed. The other options are not assumptions, but rather requirements, constraints, or criteria that the business solution must meet. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 2: Business Analysis Planning and Monitoring, page 62. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

Enterprise analysis is a knowledge area that describes the business analysis activities that take place for an enterprise to identify business opportunities, build a business architecture, determine the optimal project investment path for the enterprise and implement new business and technical solutions1. Enterprise analysis can be triggered by different need generation approaches, such as bottom-up, external drivers, middle management, or top-down2. In this case, the business need stems from external drivers, which are factors outside the organization that influence its performance, such as customers, competitors, regulations, or market trends3. A customer requesting new software for collecting customer information is an example of an external driver that creates a business need for the organization. The organization should conduct enterprise analysis to understand the customer’s requirements, assess the current capabilities and gaps, evaluate the feasibility and risks of the proposed solution, and define the business case and scope for the project. References:

What is Enterprise Analysis: does it differ from Enterprise Architecture?

[Enterprise Analysis - Business Analyst Training]

[External Drivers: Definition & Examples - Video & Lesson Transcript | Study.com]