CBAP IIBA Certified Business Analysis Professional Free Practice Exam Questions (2025 Updated)

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

The implementation approach is a component of the solution scope that describes how the chosen solution approach will deliver the solution scope. The solution approach is the method or process that will be used to implement the solution, such as a predictive or adaptive approach. The solution scope is the set of capabilities and features that the solution must provide to meet the business need1. The implementation approach explains how the solution approach will be applied to achieve the solution scope, such as the phases, activities, tasks, deliverables, and resources involved. The implementation approach also considers the risks, issues, assumptions, and constraints that may affect the implementation process23.

The other options are not correct. A. The implementation approach is not described in terms of the major features and functions that are to be included, as this is part of the solution scope, not the implementation approach. B. The implementation approach does not define major business and technical dependencies that impose constraints to the effort to deploy the solution, as this is part of the risk analysis, not the implementation approach. C. The implementation approach does not describe the new capabilities required to meet the business need, as this is part of the solution scope, not the implementation approach. References:

Solution Scope - IIBA®

Defining the Business Analysis Approach in 2023 | Free Template

Business Analysis Planning and Monitoring - IIBA®

A plan-driven approach to business analysis follows a sequential and linear process, where each phase must be completed before moving on to the next. This approach requires thorough planning upfront, reducing uncertainties later on. Therefore, communication in a plan-driven approach is likely to be formal, structured, and documented. Formal communication ensures that information is relayed in a clear, consistent, and accurate manner, and that stakeholders are aware of their roles and responsibilities. Formal communication also helps to manage changes, risks, and issues that may arise during the project lifecycle. Formal communication may include written reports, presentations, meetings, emails, and memos. References:

How to create a business analysis communication plan

How to Choose the Right Business Analysis Approach

Plan Business Analysis Approach - iiba.org

Defining the Business Analysis Approach in 2023 | Free Template

Total cost of ownership (TCO) is a financial estimate that helps consumers and enterprise managers determine direct and indirect costs of a product or system. TCO goes beyond the initial purchase price or implementation cost to consider the full cost of an asset over its useful life. It is a key concept in the business analysis tasks of enterprise analysis and solution assessment and validation. TCO can help evaluate the feasibility and viability of different solution options and compare them with the business need and expected benefits. References:

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

CBAP 150 Practice Questions Flashcards, Question 1

Production Costs: What They Are and How to Calculate Them - Investopedia

Cost of Solution vs. Cost of Problem · Jens Oliver Meiert

The T in SWOT analysis stands for Threats. These are external factors that may pose risks or challenges to the organization, its projects, or its solutions. Threats can be related to the market, the industry, the technology, the environment, the society, the regulation, or the competition. Business analysts should identify and assess the potential threats and their impact on the organization’s objectives and strategies, and recommend ways to mitigate or avoid them. References:

CBAP® Handbook, page 15, section 4.1.2.3

BABOK® Guide, page 32, section 3.2.3

SWOT Analysis: How To With Table and Example

SWOT Analysis Threats: Definition & Examples

The number of communication channels in a project is an indicator of the complexity of communication among the stakeholders. It is calculated by using the following formula1:

Number of communication channels = N x (N - 1) / 2

Where N = Number of stakeholders

In this case, N = 65, so the number of communication channels is:

65 x (65 - 1) / 2 = 2080

Therefore, the correct answer is A. 2080. References:

Number of Communication Channels (+ PMP® Formula & Calculator)

 A vision statement is a document that defines the business needs, identifies key stakeholders, and describes the positive impact the solution will provide on the key stakeholders. A vision statement is a high-level summary of the purpose, scope, and objectives of the project or initiative. It helps to align the stakeholders’ expectations, communicate the value proposition, and guide the decision making throughout the project lifecycle. A vision statement is one of the key inputs for the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business case1234. References: 1: BABOK® Guide v3, section 3.4.1 Define Business Need, page 69 2: CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 106 3: Business Analysis Techniques: Developing the Vision, pages 23-24 4: How to Write a Vision Statement for Your Business5

 A business analysis plan is a document that describes the scope of work, the deliverable Work Breakdown Structure (WBS), the activity list, and estimates for the business analysis activities. It also includes the business analysis approach, the roles and responsibilities of the business analyst and other stakeholders, the communication plan, the requirements management plan, the change management plan, and the risk management plan12. A business analysis plan is an important input for the business analysis execution and monitoring process, as it helps to guide and control the business analysis work, and to ensure that the business analysis deliverables meet the quality standards and stakeholder expectations3.

The other options are not correct. A project management plan is a document that describes how the project will be executed, monitored, and controlled. It covers the project scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder management. An implementation plan is a document that describes how the solution will be deployed, transitioned, and integrated into the business operations. It covers the implementation strategy, schedule, resources, tasks, roles, responsibilities, risks, and issues. A requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, verified, prioritized, traced, and maintained throughout the project lifecycle. It is a component of the business analysis plan, not a separate document. References:

Business Analysis Plan - IIBA®

Business Analysis Planning and Monitoring - IIBA®

Business Analysis Execution and Monitoring - IIBA®

[Project Management Plan - PMI]

[Implementation Plan - PMI]

[Requirements Management Plan - IIBA®]

 Requirements elicitation is not a business analysis planning and monitoring approach, but a business analysis task that involves identifying and documenting the needs and expectations of stakeholders. Business analysis planning and monitoring is the knowledge area that covers the tasks of defining the business analysis approach, planning the business analysis activities, managing the business analysis performance, and communicating the business analysis information. The other three options are examples of techniques that can be used in business analysis planning and monitoring, such as structured walkthroughs for validating the business analysis approach, decision analysis for selecting the best solution option, and process modeling for defining the business analysis process. References: BABOK Guide, Business Analysis Planning and Monitoring, Requirements Elicitation and Collaboration

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

 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.

 A dependency is a relationship or a condition that affects the completion or the quality of a task or an activity. A dependency can be internal or external, mandatory or discretionary, or positive or negative. In this case, the inspector’s signoff on the initial deliverables is a dependency because it is a condition that must be met before the task can be completed. The inspector’s signoff is an external and mandatory dependency, as it involves an outside party and it is required by the project scope or contract. A dependency is not the same as an assumption (A), which is a factor that is considered to be true without proof, a milestone ©, which is a significant point or event in the project, or a constraint (D), which is a factor that limits the options or performance of the project. References:

What is a Dependency in Project Management? - Wrike, paragraph 1

Project Dependencies: Types, Examples, and Tips for Project Managers, paragraph 1

CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.3: Trace Requirements, page 4-10

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.1

Functional decomposition is a technique that breaks down a complex solution scope into smaller and manageable work products or deliverables. It helps to understand the scope of work that needs to be completed, and to organize and prioritize the requirements. Functional decomposition can be represented in various ways, such as hierarchical diagrams, tables, or lists. It can also be used to create a work breakdown structure (WBS) for the project management. Functional decomposition is useful for projects that have a large or unclear solution scope, as it helps to reduce ambiguity and complexity, and to identify dependencies and gaps. References:

Using Scope Models to Manage Solution Scope

Solution Scope vs. Project Scope

Solution Scope – An Insight

SMART is an acronym that stands for Specific, Measurable, Achievable, Relevant, and Time-bound. It is a widely used approach to assess the business goals and their validity and longevity. SMART helps to ensure that the business goals are clear, realistic, and aligned with the business vision and strategy. SMART also helps to monitor and evaluate the progress and outcomes of the business goals. By using SMART, business analysts can define the business needs and requirements more effectively, and communicate them to the stakeholders more efficiently12. References:

SMART Goals: Definition and Examples | Indeed.com

How to Set SMART Goals: Guide for Supervisors and Employees

 Functional decomposition is the analysis of complex systems by breaking them down into smaller simpler elements. It involves breaking down processes, systems, functional areas, or deliverables into simpler components, so that each part can be analyzed separately12. By breaking down larger components into smaller parts, it allows the organization to measure and track each work effort involved in implementing the solution. It also helps in the assessment of the effectiveness of each sub-component as it relates to other larger or smaller components3. Functional decomposition is a technique used in business analysis to facilitate the understanding and management of large and complex processes2. It is also used in systems engineering, software architecture, database theory, machine learning, and a variety of other fields2. References: 1: Functional decomposition in business analysis – The Functional BA 2: Functional Decomposition: Definition, Diagrams, and Applications 3: 10.22 Functional Decomposition | IIBA®

Alternative generation is a business analysis element that tries to identify as many potential options as possible to meet the business objectives and fill identified gaps in capabilities. Alternative generation is part of the strategy analysis knowledge area, which involves defining the business need, assessing the current state, defining the future state, identifying solution options, and recommending a solution. Alternative generation helps to explore the possible ways to achieve the desired outcomes, and to evaluate the feasibility, viability, and suitability of each option. Alternative generation can use various techniques, such as brainstorming, benchmarking, market analysis, or SWOT analysis, to generate and compare different solution alternatives. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 100, section 5.41

[CBAP Certification Study Guide v3.0], Chapter 5: Strategy Analysis, Section 5.4: Identify Solution Options, page 5-152

What Is Business Analysis and Why Is It Important? - Indeed, paragraph 4

More CBAP Preparation Questions – The Functional BA, question 4

According to the Wikipedia article on requirements traceability1, tracing a requirement means to follow the life of a requirement in both a forwards and backwards direction, from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration. Tracing a requirement helps to ensure that the requirement is linked to a business objective, that it is consistent and aligned with other requirements and deliverables, and that it is verified and validated by the stakeholders. Tracing a requirement can also help to identify the impact of changes, the source of defects, and the gaps in the requirements.

Option A is incorrect because it does not mention the business requirements, which are the high-level needs and objectives of the organization or the customer. Option C is incorrect because it does not mention the stakeholder and solution requirements, which are the detailed and specific requirements that define the scope and functionality of the solution. Option D is incorrect because it describes tracking a requirement, not tracing a requirement. Tracking a requirement means to monitor the progress and status of a requirement throughout the project lifecycle, not to link it to other related artifacts.

 A solution approach is a description of the proposed method for delivering a solution that meets the business need. It is one of the outputs of the enterprise analysis tasks, along with business need, capability gaps, solution scope, and business case. A solution approach defines the type, nature, and complexity of the solution, and provides a high-level view of how the solution will be implemented. It also identifies the major components, features, and functions of the solution, as well as the key stakeholders, risks, assumptions, and constraints. A solution approach helps to evaluate the feasibility and viability of different solution options and compare them with the business need and expected benefits. References:

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

An Overview of Enterprise Analysis - Modern Analyst

How Do You Know When You Are Doing Enterprise Analysis

 A RACI chart is a graphical representation of roles and responsibilities of different project team members. It is a matrix that shows the relationship between the project activities and the project roles. RACI stands for Responsible, Accountable, Consulted, and Informed. These are the four levels of involvement that a project team member can have in a project activity. A RACI chart can help to clarify the expectations, avoid confusion, and improve communication among the project team and stakeholders. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 343

Business Analysis Professional Resources | IIBA®, under Business Analysis Body of Knowledge (BABOK ®) Guide

What is a RACI Chart? | RACI Chart Definition & Example | ASQ