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

Risk identification is a process that can start with the source of problems or with the problem itself. Risk identification is the process of determining the risks that may affect the project or the solution, and documenting their characteristics. Risk identification can be performed by analyzing the sources of risks, such as the project environment, the stakeholders, the requirements, the assumptions, the constraints, or the dependencies. Risk identification can also be performed by analyzing the problems or issues that may arise during the project or the solution, such as the gaps, conflicts, ambiguities, uncertainties, or changes. Risk identification helps to create a list of potential risks and their causes, impacts, and probabilities for further analysis and response planning12. Risk estimation is a process that follows risk identification. Risk estimation is the process of assessing the likelihood and impact of the identified risks, and prioritizing them according to their severity. Risk estimation helps to quantify the level of risk exposure and the expected value of the risk for decision making12. Risk analysis is a process that follows risk estimation. Risk analysis is the process of evaluating the identified and prioritized risks, and determining the appropriate responses to them. Risk analysis helps to develop strategies and actions to avoid, reduce, transfer, or accept the risks, and to allocate resources and contingency reserves for risk management12. Risk management is a process that encompasses risk identification, risk estimation, risk analysis, and risk monitoring and control. Risk management is the process of planning, identifying, analyzing, responding to, and monitoring and controlling the risks throughout the project or the solution lifecycle. Risk management helps to minimize the negative effects and maximize the positive opportunities of the risks, and to ensure the project or the solution objectives are met12. References: CBAP® Handbook, CBAP® Exam Prep Study Guide

 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”

A change log is a tool that helps to manage and monitor the changes that affect the requirements, the solution, or the project. A change log tracks all characteristics and status of changes that have been received, such as the source, description, priority, impact, approval, and resolution of the changes. A change log can help to ensure that the changes are properly documented, communicated, and controlled, and that they are aligned with the stakeholder needs and expectations. References: BABOK Guide v3, page 54; CBAP / CCBA Certified Business Analysis Study Guide, page 161.

 A test plan is a document that describes the scope, objectives, strategy, and activities of testing a software product or system. A test plan is mandatory in most software development projects because it ensures that the software meets the quality standards and requirements of the stakeholders. A test plan also helps to identify and mitigate the risks, defects, and issues that may affect the software functionality, performance, usability, and security. A test plan is different from a communication management plan, which is a document that describes how the project information will be communicated to the stakeholders. A test plan is also different from a disaster recovery plan, which is a document that describes how the project will resume its operations in the event of a disaster or emergency. A test plan is not a procurement plan, which is a document that describes how the project will acquire the goods and services needed from external sources. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 9: Solution Assessment and Validation, page 329-330.

How to write a software requirement document (with template), paragraph 6

These testing methods should be mandatory for any software, paragraph 1

Software Testing Plan - Tutorialspoint, paragraph 1

 A cost-benefits justification is a term that matches management’s request to include the projected costs and benefits to be realized and how those and benefits will be assessed and evaluated in the business case. A cost-benefits justification is a process that compares the costs of implementing a project or a solution with the benefits that it will generate, both in monetary terms. It helps to determine the feasibility, profitability, and return on investment of the project or solution, and to support the decision-making process. A cost-benefits justification also includes the methods and criteria for measuring and evaluating the costs and benefits, such as net present value, internal rate of return, payback period, or cost-benefit ratio12. References:

Cost-Benefit Analysis: A Quick Guide with Examples and Templates

Cost-Benefit Analysis: What It Is & How to Do It

The business analysis process that ensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work is verify requirements. According to the BABOK® Guide1, this process involves checking that the requirements are well-defined, clear, consistent, complete, correct, feasible, modifiable, testable, and traceable. It also involves resolving any defects or issues that may affect the quality of the requirements. The purpose of this process is to confirm that the requirements specifications and models accurately reflect the stakeholder needs and expectations, and that they are ready for validation and approval.

The other options are not correct, but rather:

A. Identify constraints and assumptions is a task within the assess capability gaps process, which involves comparing the current and future states of the organization to identify the gaps that must be addressed by a solution.

B. Validate requirements is a process that ensures that the requirements support the delivery of value to the stakeholders and achieve the goals and objectives of the project or initiative. It involves evaluating the alignment, acceptability, and approval of the requirements by the stakeholders.

D. Specify and model requirements is a process that involves defining and representing the requirements in various formats, such as textual, graphical, or tabular. It helps to communicate, analyze, and refine the requirements more effectively.

References:

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

BABOK® Guide, page 33, section 4.2.3: Verify Requirements

How Do Business Analysts Verify Requirements? (BABOK 6.5)

What Is Requirements Analysis? Process and Techniques

The solution approach is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. It involves identifying and evaluating different options for creating or acquiring new capabilities, such as products, services, processes, or systems, that will deliver value to the stakeholders and solve the business problem. The solution approach also considers the constraints, risks, assumptions, and dependencies that may affect the solution. The solution approach provides the basis for defining the solution scope, which specifies the features and functions of the solution, and the project scope, which specifies the work required to deliver the solution123.

The other options are not correct definitions of the solution approach. Option A is the definition of scope change control, which is the process of managing and documenting the changes to the product scope as approved by the project stakeholders. Option C is the definition of a risk, which is an uncertain event or condition that may have a positive or negative impact on the project objectives. Option D is the definition of decomposition, which is a technique that breaks down the project scope into smaller deliverables; each deliverable is subdivided repeatedly until the deliverable cannot or should not be broken down any further4. References: 1: BABOK® Guide v3, section 11.2 Define Solution Approach, page 402 2: CBAP® Exam Prep Study Guide, chapter 9, page 323 3: How to Choose the Right Business Analysis Approach 4: PMBOK® Guide, Sixth Edition, section 5.4.2.1 Decomposition, page 156

 Requirements prioritization is the process of ranking the requirements in the order of their importance or value to the stakeholders and the solution. Requirements prioritization helps to ensure that the most critical and beneficial requirements are implemented first, and that the project focuses on delivering the maximum value to the stakeholders within the available time and resources. Requirements prioritization also helps to manage the scope, schedule, budget, and quality of the project, as well as to handle changes and risks effectively123. References: 1: Five Requirements Prioritization Methods1 2: What is Requirements Prioritization?2 3: The 6 Most Important Requirements Practices3

Benchmarking is a business analysis approach that involves comparing one’s own performance, processes, or products with those of other organizations, especially the best performers or industry leaders, to identify gaps and opportunities for improvement. Benchmarking can help business analysts understand the competitive landscape, identify best practices, set realistic goals, and measure progress. In this question, Sally and her business analysis team are using benchmarking to determine what the competition is offering and how they can increase their revenue by remaining competitive. References:

CBAP® Handbook, page 15, section 4.1.2.3

BABOK® Guide, page 32, section 3.2.3

CBAP / CCBA Certified Business Analysis Study Guide, page 96, section 3.2.3

What is a Competitive Analysis — and How Do You Conduct One?

 Identifying the stakeholders early on in the business analysis duties helps the business analyst to understand the needs, expectations, and interests of the stakeholders, as well as their influence and authority on the project. This helps the business analyst to plan and manage the requirements activities, communicate effectively with the stakeholders, and address any issues or conflicts that may arise. By involving the stakeholders throughout the business analysis process, the business analyst can ensure that the requirements deliverables are aligned with the stakeholder needs and expectations, and that they are delivered on time and within budget. References:

IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, 2015, p. 30-311

IIBA, Business Analysis Competency Model, Version 4, 2018, p. 142