IIBA Updated CCBA Exam Questions and Answers by ferne

According to the BABOK® Guide, reviewing stakeholder concerns is a technique that involves identifying and analyzing the issues, expectations, and interests of the stakeholders that may affect the acceptance or implementation of the solution. The purpose of reviewing stakeholder concerns is to address potential problems or issues that may arise during the solution delivery or operation, and to develop strategies to mitigate or resolve them1. References: 1: BABOK® Guide, version 3, section 10.29, page 341.

The high-level requirements list that the business analyst may create when using a change-driven approach is also known as requirements envisioning. This is a technique for eliciting and documenting the high-level features and characteristics of the solution, and defining the scope and boundaries of the initiative12. Requirements envisioning helps to establish a common understanding and vision among the stakeholders, and to guide the iterative and incremental delivery of the solution. The other options are not terms that are equivalent to the high-level requirements list, but rather terms that describe different aspects of the solution or the project, such as project scope (B), which is the work that must be performed to deliver the solution3, product scope ©, which is the features and functions that characterize the solution3, or requirements foundation (D), which is a term that refers to the core set of requirements that are essential for the solution4. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis

When you assess a solution, what you are actually looking for is to determine the value of the proposed solution to the stakeholder requirements. This is the main purpose of the solution assessment and validation knowledge area, which involves measuring and evaluating the performance and benefits of the solution, and ensuring that it meets the stakeholder needs and expectations12. Value is defined as the worth, importance, or usefulness of something to a stakeholder within a context3. To determine the value of the proposed solution, you need to identify and analyze the value proposition, the value drivers, the value measures, and the value delivery4. The other options are not what you are actually looking for when you assess a solution, but rather aspects that may contribute to the value of the solution, such as the quality (B), which is the degree to which a solution meets the requirements and delivers the expected benefits5, the cost ©, which is the amount of resources expended or consumed to implement and operate the solution, or the accuracy (D), which is the extent to which a solution represents the true or exact state of the problem or the need. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, [Certification of Capability in Business Analysis (CCBA®) - Simplilearn], [A GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE]

The signoff on the requirements represents the formal acceptance and approval of the requirements by the stakeholders. It indicates that the stakeholders agree that the requirements are accurate and complete, and that they meet the business need and the solution scope12. The signoff does not imply that the requirements are constrained by time, cost, and quality, or that the project can now be launched, or that the business analyst’s work is done. These are other aspects of the project management and business analysis processes that are not directly related to the signoff on the requirements. References:

• 1: BABOK® Guide, Version 3.0, p. 41
• 2: Business Analysis Expert Certification, CCBA® | IIBA®