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

 In this scenario, the distributor is under pressure to fully meet the year-round market demand in order to stay in business. The primary objective is not directly related to making more profit, defeating competitors, or stabilizing its performance but rather ensuring that customer orders are fulfilled even during peak demand periods. This aligns with one of the key aspects of business analysis - understanding and prioritizing the needs and expectations of stakeholders (in this case, customers) to deliver value. References: Business Analysis Professional (CBAP) Learning documents or resources available at 1 and 2

 A cause-and-effect diagram, also known as an Ishikawa diagram, is a graphical tool that helps identify, sort, and display possible causes of a specific problem or quality characteristic. It can also be used to explore the root causes of a problem or a desired outcome. The diagram looks like the skeleton of a fish, hence the name fishbone diagram. The effect or problem is shown as the fish’s head, and the causes are shown as the bones along the spine. The diagram helps to organize the causes into categories, such as people, processes, equipment, materials, environment, etc. The diagram can be created by brainstorming the causes and grouping them into major categories. The diagram can then be analyzed to identify the most likely or significant causes of the problem or outcome.

A work breakdown structure (WBS) is a visual decomposition of the program scope and the resources needed in order to create the things defined within the program scope. A WBS is a hierarchical representation of the deliverables, activities, and tasks that are required to complete the program. A WBS defines the scope, schedule, cost, and quality of the program, and helps to allocate the resources and assign the responsibilities for the program. A WBS also helps to identify the dependencies, risks, and issues of the program, and to monitor and control the program performance12. A resource breakdown structure (RBS) is a visual decomposition of the resources that are needed to complete the program. An RBS is a hierarchical representation of the human and non-human resources that are required to perform the activities and tasks of the program. An RBS defines the types, categories, and quantities of the resources, and helps to estimate, acquire, and manage the resources for the program. An RBS also helps to identify the availability, utilization, and allocation of the resources, and to optimize the resource efficiency and effectiveness13. A product breakdown structure (PBS) is a visual decomposition of the products that are delivered by the program. A PBS is a hierarchical representation of the components and features that make up the products of the program. A PBS defines the scope, quality, and functionality of the products, and helps to design, develop, and test the products for the program. A PBS also helps to identify the requirements, specifications, and standards of the products, and to verify and validate the products14. A budgeted cost of work scheduled (BCWS) is a measure of the planned value of the program. A BCWS is the sum of the budgets for all the work packages and activities that are scheduled to be completed by a given date. A BCWS defines the expected cost of the program, and helps to compare the actual cost and the earned value of the program. A BCWS also helps to identify the cost variance and the cost performance index of the program, and to forecast the cost at completion and the estimate at completion1 . References:

CBAP® Handbook

Work Breakdown Structure - iiba.org

Resource Breakdown Structure - iiba.org

Product Breakdown Structure - iiba.org

[Budgeted Cost of Work Scheduled - iiba.org]

 A formal review with the stakeholders is a way to validate the elicitation results and ensure that nothing is missed or misunderstood. The review can also help to build trust and confidence among the stakeholders and the BA. The other options are not directly related to addressing the sponsor’s concerns. References: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 5: Elicitation and Collaboration, p. 173-174; [A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 4: Elicitation and Collaboration, Section 4.4: Confirm Elicitation Results, p. 107-108.

 A proven and tailored analysis approach is suitable for this project because it allows the business analyst to adapt to the specific needs and context of the project, while leveraging the best practices and standards of the profession. A proven and tailored analysis approach can also accommodate the different cultures, languages, regulations, and time zones of the countries involved in the project. A proven and tailored analysis approach is based on the following principles1:

Business analysis is performed in alignment with the organization’s strategy and objectives

Business analysis is driven by stakeholder needs and values

Business analysis is collaborative and iterative

Business analysis is adaptive and responsive to change

Business analysis is supported by effective communication and documentation

Business analysis is guided by ethical and professional conduct

References:

1: CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 1: Introduction to Business Analysis, page 82

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

Ad images are a strong candidate to be addressed while planning for requirements reuse, because they are likely to change frequently and have common elements that can be reused across different weeks. Requirements reuse is a technique that involves identifying, storing, and reusing requirements or requirement components for future projects or initiatives. It can help to reduce duplication, improve consistency, and save time and effort. Ad images can benefit from requirements reuse, because they can use a standard template, format, and style, and only change the specific image and text for each new topping. Dough preparation, toppings preparation, and topping recipes are not good candidates for requirements reuse, because they are either stable or unique for each week. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Life Cycle Management, page 124

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Requirements Life Cycle Management, section 3.7: Reuse Requirements, page 66

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 3: Requirements Life Cycle Management, page 124

Risk communication is the technique that involves coordinating and collaborating with other credible sources in risk. Risk communication is the process of exchanging information and opinions about the nature, magnitude, significance, and control of the risks among the stakeholders. Risk communication helps to create a common understanding of the risks, to build trust and confidence among the stakeholders, to inform and educate the stakeholders about the risk management activities and outcomes, and to solicit feedback and input from the stakeholders. Risk communication is an essential part of risk management, which also includes risk identification, risk analysis, and risk response. References: [IIBA BABOK Guide v3], section 11.2.4, page 389; CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 233; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 246.

The BA should review the future state with the process owner who expresses a strong opinion that the solution will not deliver the expected value. This is because the future state describes the desired outcomes, benefits, and capabilities of the solution, and how it will address the business need and stakeholder requirements. By reviewing the future state, the BA can help the process owner to understand the value proposition of the solution, clarify any misunderstandings or assumptions, and address any concerns or objections. This can help to increase the process owner’s engagement and support for the change. Updating the requirements, recording the feedback and continuing, or changing the governance approach are not the best options because they do not address the root cause of the problem and may result in resistance or conflict. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 254

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 5: Strategy Analysis, section 5.3: Define Future State, page 99

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 6: Strategy Analysis, page 254

 The medium is the component of the communication model that is responsible for transferring the message between two or more entities. The medium is the channel or the tool that is used to transmit the message from the sender to the receiver. The medium can be verbal, written, visual, or a combination of these. The medium can also be electronic, such as email, phone, or video conference, or physical, such as paper, board, or face-to-face meeting. The medium acts as a translator by converting the message into a form that can be understood by the receiver. The medium also influences the effectiveness and efficiency of the communication, as different mediums have different advantages and disadvantages, such as speed, cost, feedback, and noise. References: IIBA BABOK Guide v3, section 2.2.2.3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 236; CBAP Business Analyst Exam Prep | Practice Quiz, question 256.

 A requirement attribute is a characteristic or property of a requirement that provides additional information about it. Requirement attributes can help to manage, prioritize, trace, and verify the requirements. Some common requirement attributes are source, priority, status, owner, version, etc. One of the qualities of a good requirement is that it should be unambiguous, which means that it should have only one possible interpretation and avoid any confusion or misunderstanding. An unambiguous requirement is clear, precise, and consistent, and it can be easily verified and validated. An ambiguous requirement, on the other hand, can lead to errors, defects, rework, and conflicts among the stakeholders. References:

Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS) - Jama Software, under Qualities of Good Requirements

The Four Attributes of High-Quality Requirements - ArgonDigital, paragraph 1

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