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

System thinking is a type of analytical thinking that involves understanding how the components of a system interact with each other and affect the whole. System thinking helps the business analyst to see the big picture, identify the root causes of problems, and design solutions that address the system as a whole. System thinking is essential for conducting requirements elicitation for a process that involves people, processes, and technology, as these are interrelated and interdependent elements of a system. The other options are not types of analytical thinking, but rather techniques or skills that can be used in different situations. References:

9.1 Analytical Thinking and Problem Solving, paragraph 1

Business Analysis Blog | Systems Thinking – An Analyst’s Essential Trait, paragraph 1

Top 11 Most Effective Business Analysis Techniques | 2024, paragraph 2

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency. References: BABOK Guide v3, page 142; CBAP / CCBA Certified Business Analysis Study Guide, page 191.

 Surveys are a conduct stakeholder analysis technique that is useful for identifying shared characteristics of a stakeholder group. Surveys are structured questionnaires that are distributed to a large number of stakeholders to collect quantitative and qualitative data about their needs, expectations, preferences, and opinions. Surveys can help to identify common patterns, trends, and themes among the stakeholder group, as well as to measure the level of agreement, satisfaction, or importance of the requirements. Surveys can also be used to segment the stakeholder group based on their characteristics, such as roles, responsibilities, interests, or influence.

Scope modeling, brainstorming, and interviews are other conduct stakeholder analysis techniques, but they are not as effective as surveys for identifying shared characteristics of a stakeholder group. Scope modeling is a technique that defines the boundaries and context of the business domain and the solution. Brainstorming is a technique that generates a large number of ideas or solutions in a creative and collaborative way. Interviews are a technique that involves one-on-one or group discussions with the stakeholders to elicit detailed information about their needs, expectations, preferences, and opinions. These techniques are more suitable for exploring the specific and individual characteristics of the stakeholders, rather than the general and collective ones. References:

BABOK® Guide, p. 104-105, 377-378

CBAP / CCBA Certified Business Analysis Study Guide, p. 49-50, 52

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 3, Video: “Stakeholder Analysis”

 A requirements management plan is a business analysis plan that defines and describes the process to be followed in managing the solution scope and requirements. It includes the following items12:

The requirements structure and traceability

The requirements prioritization and approval process

The requirements change control process

The requirements communication and reporting process

The requirements validation and verification process

The requirements configuration management process

The requirements reuse and disposal process

A requirements management plan is an important component of the business analysis plan, as it helps to ensure that the requirements are aligned with the business needs and objectives, and that they are delivered and maintained in a consistent and effective way. References:

Requirements Management Plan - IIBA®

Requirements Management Plan Template

The creative thinking process is a technique to generate and evaluate new ideas for solving problems or improving situations. The effectiveness of the creative thinking process can be measured by three values: novelty, usefulness, and feasibility1. Novelty refers to how original, unique, or different the ideas are. Usefulness refers to how well the ideas address the problem or opportunity. Feasibility refers to how practical, realistic, or implementable the ideas are. Generating a pre-determined number of new ideas for a business solution is not a measurement of effective creative thinking, as it does not reflect any of these values. The quantity of ideas is not as important as the quality of ideas in terms of novelty, usefulness, and feasibility. References: BABOK® Guide

1: https://www.iiba.org/globalassets/standards-and-resources/babok/babok-guide-v3.pdf

 Crashing is a process of adding labor to a project to reduce the project duration. Crashing involves increasing the resources, such as staff, equipment, or materials, to accelerate the completion of critical activities. Crashing may also involve paying overtime, hiring consultants, or outsourcing some tasks. Crashing is usually done when the project is behind schedule or when there is a need to meet a deadline. Crashing may increase the project cost and risk, so it should be done carefully and only when necessary.

Forming, storming, and rolling wave planning are not related to the process of adding labor to a project. Forming and storming are stages of team development, where the team members get to know each other and resolve conflicts. Rolling wave planning is a technique of iterative planning, where the work to be done in the near term is planned in detail, while the work in the distant future is planned at a higher level. References:

CBAP Certification Study Guide v3.0, page 33

BABOK Guide v3, page 16

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 3, Week 3, Video: “Project Management Concepts”

 The solution development team is appearing to change the prioritization of the requirements based on overstated complexity of the project work. This means that they are exaggerating the difficulty and effort involved in implementing a certain portion of the requirements, in order to lower their priority or avoid doing them altogether. This may indicate that the team does not want to implement those requirements for some reason, such as lack of interest, skills, resources, or alignment with the solution vision. This may also result in a loss of trust and collaboration between the business analyst and the solution development team, and a compromise of the quality and value of the solution.

The other options are not correct. A. Changing the prioritization of the requirements based on the past project is not what the solution development team is appearing to do, as they are insisting that this is a different type of requirements than the previous project. C. Getting the requirements removed from the project scope is not what the solution development team is appearing to do, as they are not explicitly asking for that, but rather expressing the difficulty of the requirements. D. Having the business analyst report the difficulty of the project work to the project customer is not what the solution development team is appearing to do, as they are not suggesting that, but rather complaining about the complexity of the project work. References:

Business Analysis Professional (CBAP) Certification Study Guide, page 131, section 4.2.3 Requirements Prioritization

Prioritizing Requirements - IIBA®

How to Prioritize Requirements: Techniques, Tools, and Examples

A requirements workshop is a type of elicitation technique that involves carefully selected stakeholders and subject matter experts for a short, intensive period (usually for one to a few days) to define and document the requirements for a solution. A requirements workshop is also known as a joint application development (JAD) session or a facilitated workshop. The benefits of a requirements workshop include increased stakeholder collaboration, consensus building, creativity, and productivity. A requirements workshop is facilitated by a business analyst or a professional facilitator, who guides the participants through a structured agenda and ensures that the objectives of the workshop are met. References:

BABOK Guide, section 4.2.5.1, page 108

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

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

 Business goals and objectives are the desired outcomes that the organization wants to achieve through the project. They are not the same as the solution requirements, which describe the features and functions of the solution. Business goals and objectives are also not the same as the project scope, which describes the work that needs to be done to deliver the solution. Business goals and objectives are the ends, not the means, of the project. References:

IIBA BABOK Guide, section 5.1.1, page 97

CBAP/CCBA Study Guide, chapter 5, page 217

 A desired outcome is a statement of what the organization wants to achieve as a result of the business analysis work. A desired outcome should be specific, measurable, achievable, relevant, and time-bound (SMART). A desired outcome should also be aligned with the organizational goals and objectives, and provide value to the stakeholders. Examples of desired outcomes are increase sales, reduce costs, and reduce time to deliver a product or service. Implement new machinery to complete the work processes faster is not an example of a desired outcome, but rather a possible solution or requirement that may help to achieve a desired outcome. References: BABOK Guide v3, page 97; CBAP / CCBA Certified Business Analysis Study Guide, page 217.

The opportunity cost is the value of the best alternative forgone when choosing one option over another. In this case, the opportunity cost of choosing solution A is the value of solution B minus the value of solution A, which is $565,000 - $456,000 = $109,000. This means that by choosing solution A, the organization is giving up the potential benefit of $109,000 that could have been gained from solution B. References: CBAP Certification Study Guide v3.0, page 33; BABOK Guide v3, page 16.

 Decision analysis is a technique of evaluating the possible outcomes of different alternatives and choosing the best one based on the criteria and preferences of the stakeholders. Decision analysis can be used to assess potential risks that may impact the solution and the cost and benefits associated with it, by using methods such as decision trees, decision tables, or expected value analysis. Decision analysis can help to select the optimal solution that maximizes the value and minimizes the risk for the organization. References: BABOK Guide v3, page 130; CBAP / CCBA Certified Business Analysis Study Guide, page 185.

 A regulator is not a stakeholder that is considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A regulator is an external entity that imposes rules, standards, or guidelines that the organization and the solution must comply with. A regulator is not directly involved in the business analysis process, but rather in the governance and validation of the solution. Therefore, a regulator does not influence the choice of the business analysis approach, which is based on the characteristics and needs of the project and the organization.

The other options are stakeholders that are considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A tester is a stakeholder who verifies and validates the quality and functionality of the solution. A project manager is a stakeholder who oversees and coordinates the project activities, resources, and deliverables. A functional manager is a stakeholder who manages a specific business function or department, such as finance, marketing, or human resources. These stakeholders have different roles, responsibilities, expectations, and interests in the business analysis process, and they may affect or be affected by the choice of the business analysis approach. References:

BABOK® Guide, p. 29, 32, 66

CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 48, 133

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

Work breakdown structure creation is a technique that can be used to plan and manage the business analysis work, but it is not a technique to specify or model requirements. Organization modeling, data modeling, and state diagrams are all techniques that can be used to describe different aspects of the requirements, such as the stakeholders, the data, and the behavior of the solution. References:

CBAP Handbook, page 6, Exam Blueprint, Knowledge Area 4: Requirements Analysis and Design Definition

BABOK Guide, Chapter 10: Techniques, Section 10.1: Acceptance and Evaluation Criteria Definition, Section 10.8: Data Modeling, Section 10.34: State Modeling, Section 10.37: Work Breakdown Structure

 Decision analysis is a business analysis technique that involves evaluating the feasibility, benefits, risks, and impacts of various options and selecting the best one based on predefined criteria and stakeholder preferences. In this scenario, the business analyst is considering using decision analysis to rate the available methodologies against the organizational needs and objectives, and to choose the most suitable one for the business analysis approach. Decision analysis can help the business analyst to align the business analysis activities with the project and enterprise goals, and to optimize the value delivery of the solution. References:

BABOK® Guide, p. 66-67

CBAP / CCBA Certified Business Analysis Study Guide, p. 133

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

 The project manager is the stakeholder who is responsible for assessing the solution scope to determine the project scope. The solution scope defines the features and functions of the product or service that will meet the business needs and requirements. The project scope defines the work that needs to be done to deliver the solution. The project manager is the person who plans, executes, monitors, and controls the project activities, and ensures that the project scope is aligned with the solution scope, the project objectives, and the stakeholder expectations. References: BABOK Guide v3, page 36; CBAP / CCBA Certified Business Analysis Study Guide, page 74.

 The communications management plan is a document that defines the approach, methods, frequency, and responsibilities for communicating with the stakeholders throughout the business analysis process. The communications management plan also specifies how the business analysis communications will be stored, distributed, updated, and disposed of at the end of the project. Therefore, the business analyst must follow the communications management plan to determine what to do with all of the communication documents created as part of the project.

The other options are incorrect because they do not reflect the best practice for managing the business analysis communications. All formal communication must not be destroyed once the project is completed, as they may contain valuable information and lessons learned that can be used for future reference or audit purposes. All communications must not be documented and passed onto the solution’s project manager for analysis and to serve as supporting detail, as this may create unnecessary duplication, confusion, and overhead. The project manager may not be the best person to analyze and use the business analysis communications, as they may have different objectives and perspectives than the business analyst. All communications must not be archived and will become part of the organizational process assets, as this may not be appropriate or feasible for all types of communication. Some communication may be confidential, sensitive, or irrelevant for the organization, and may not need to be archived or shared with others. References:

BABOK® Guide, p. 29, 32

CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 48

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

According to the BABOK® Guide, one of the tasks of the business analyst is to obtain stakeholder approval on requirements. This task involves ensuring that the stakeholders have a shared understanding of the requirements and that they agree on their validity and priority. The business analyst also has to address any concerns, issues, or conflicts that may arise during the approval process. The business analyst has to communicate the requirements clearly and effectively, using appropriate techniques and tools, such as presentations, prototypes, models, or simulations. The business analyst also has to document the approval decisions and track the status of the requirements throughout the project lifecycle. The other options are not relevant to this task. The stakeholders’ ability to pay for the solution is not a factor in the approval of the requirements, but rather a factor in the feasibility and viability of the solution. The project manager’s input on the solution is not a substitute for the stakeholder approval, but rather a complement to it. The project manager may have a different perspective and interest in the solution than the stakeholders. Getting all the stakeholders to sign off on the requirements is not enough to ensure their understanding and agreement. The business analyst has to verify that the stakeholders have reviewed and comprehended the requirements before obtaining their signatures. References:

BABOK® Guide, Version 3, Section 4.5: Obtain Stakeholder Approval on Requirements, page 118-120.

Getting Back to Basics: Delivering Approved Requirements - Modern Analyst, paragraph 2-3.

Requirements approvals – The Functional BA, paragraph 1-2.

The lead BA should implement key performance measures to identify areas of improvement, as this is the most effective way to assess the current state of the business analysis practices and the value they deliver to the organization. Key performance measures are quantifiable indicators that reflect the critical success factors of a project, process, or activity. They can be used to evaluate the quality, efficiency, and effectiveness of the business analysis deliverables and outcomes, as well as the satisfaction and engagement of the stakeholders. By measuring and analyzing the key performance indicators, the lead BA can identify the gaps, issues, and opportunities for improvement in the business analysis practices, and propose solutions to enhance them.

The other options are not the best actions to take. A BA time tracking system may help to monitor the effort and duration of the business analysis activities, but it does not provide information on the quality and value of the deliverables and outcomes. Templates for BAs to use may help to standardize and document the business analysis deliverables, but they do not ensure the alignment and agreement of the requirements and the stakeholder needs. Workload plans of the BA may help to manage the resources and priorities of the business analysis activities, but they do not measure the impact and benefits of the business analysis outcomes. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 2: Business Analysis Planning and Monitoring, p. 40-41, 48-49, 51-52.

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Requirements Life Cycle Management, p. 93-94, 97-98.