CBAP Exam Dumps : Certified Business Analysis Professional

 The BA should recommend to assign the feature a lower priority for future release. This means that the feature will not be included in the initial release of the solution, but it may be considered for later releases depending on the availability of resources, the feedback from the stakeholders, and the alignment with the business objectives. This approach can help to balance the value and the effort of the feature, as well as to avoid scope creep and unnecessary complexity in the initial release. The other options are not the best recommendations, as they may either ignore the needs of the stakeholders, disrupt the existing business process, or increase the risk and cost of the project. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 255-256

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 155-156

 The BA is performing an enterprise assessment, which is the process of evaluating the current state and capabilities of the enterprise in relation to the desired future state and the proposed solution. An enterprise assessment can include reviewing the existing processes, tools, systems, culture, structure, and strategy of the enterprise, and identifying their strengths, weaknesses, opportunities, and threats. An enterprise assessment can help the BA to determine the feasibility, readiness, and risks of adopting a potential solution, and to recommend the appropriate change strategy and transition plan. The other options are not the best answers, as they are more specific types of assessments that focus on a particular aspect of the enterprise, such as the stakeholders, the organization, or the operations. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

 Scalability is a non-functional requirement that refers to the ability of a system to handle increasing workloads or demands without compromising its performance or functionality. System B supports scalability over System A, as it can process double the number of claims that System A can, and it rarely goes offline. System A, on the other hand, would be at capacity if it were to process all of the company’s claims, and it must go offline for two hours each day. References: The answer can be verified from the Business Analysis Professional (CBAP) learning documents or resources, such as:

IIBA BABOK Guide, Section 4.2.3, Non-Functional Requirements

Non-Functional Requirements: Definition, Types, and Examples, ReQtest

Non-Functional Requirements: Scalability, Software Engineering Stack Exchange