IIBA CCBA Certificate of Capability in Business Analysis CCBA Exam Practice Test

Answer : B

Requirements are dynamic and may change throughout the project life cycle due to various factors, such as changing business needs, stakeholder feedback, new opportunities, or risks. Business analysis planning and monitoring involves defining the process for managing changes to requirements, including how to assess the impact, prioritize, approve, and communicate the changes. The business analyst should be prepared to handle changes to requirements at any time and ensure that they are aligned with the project objectives and stakeholder expectations.Reference:

Business Analysis Expert Certification, CCBA | IIBA, section ''The Experienced Business Analysis Professional''

CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, section ''4. Review the Exam Blueprint''

Answer : B

Comprehensive and Detailed Additional requirement attributes(such as priority, complexity, and status) improve clarity and organization, making requirements easier to understand.

BABOK Guide (Chapter 5.3 - Specify and Model Requirements)states that providingdescriptive attributes helps stakeholders interpret requirements correctly and improve usability.

Traceability matrices (Option A)help link requirements but do not improve clarity.

Matrix documentation formats (Option C)improve organization but do not enhance requirement clarity.

ISO 29148 standards (Option D)define best practices but do not directly improve readability for stakeholders.

Answer : B

The three categories of risk tolerance associated with the stakeholders areneutrality,risk-seeking, andrisk-aversion1. These categories describe how willing the stakeholders are to accept the uncertainty and potential negative consequences of the requirements and the solution. Neutrality means that the stakeholders are indifferent to the risk level and do not have a preference for more or less risky options. Risk-seeking means that the stakeholders are willing to take on more risk in exchange for higher rewards or benefits. Risk-aversion means that the stakeholders prefer to avoid or minimize risk and opt for safer or more reliable options.Mitigation is not a category of risk tolerance, but rather a strategy or technique for reducing the impact or likelihood of a risk2.Reference:Business Analysis Expert Certification, CCBA | IIBA,Certification of Capability in Business Analysis (CCBA)

Answer : D

A work breakdown structure (WBS) is a tool that decomposes the project scope into smaller, manageable components. A WBS is useful for identifying activities in the business analysis approach, as it helps to define the tasks, dependencies, and resources required for each deliverable. A WBS also helps to estimate the effort, duration, and cost of the business analysis work, as well as to monitor and control the progress and quality of the deliverables. A WBS is different from project management input, which is an input to the business analysis approach, not a tool for identifying activities; BABOK, which is a guide that provides the best practices and standards for business analysis, not a tool for identifying activities; and a list of deliverables, which is an output of the business analysis approach, not a tool for identifying activities.Reference:

CCBA Handbook, page 15

[BABOK Guide], page 38

[Business Analysis for Practitioners: A Practice Guide], page 42

[Business Analysis: The Question and Answer Book], page 28

Answer : D

A . Supporting training activities and knowledge management: This is acorrectobjective of specifying and modeling requirements, as it helps to document and share the knowledge and information that are needed to understand, implement, and use the solution. Specifying and modeling requirements also helps to create training materials and guides for the end-users and other stakeholders who will interact with the solution.

B . Facilitating communication among stakeholders: This is acorrectobjective of specifying and modeling requirements, as it helps to convey the needs, expectations, and preferences of the stakeholders in a clear, consistent, and unambiguous way. Specifying and modeling requirements also helps to resolve conflicts, negotiate trade-offs, and reach agreements among the stakeholders who have different perspectives and interests.

C . Compliance with contracts and regulations: This is acorrectobjective of specifying and modeling requirements, as it helps to ensure that the solution meets the legal, ethical, and contractual obligations and standards that are applicable to the project and the organization. Specifying and modeling requirements also helps to identify and mitigate the risks and issues that may arise from non-compliance or violation of the contracts and regulations.

D . Increasing revenue and/or reducing costs within an organization: This is anincorrectobjective of specifying and modeling requirements, as it is not directly related to the business analysis tasks, but to the business objectives and benefits of the solution. Specifying and modeling requirements helps to define the scope, features, and quality of the solution that will address the business problem or opportunity, but it does not guarantee that the solution will increase the revenue or reduce the costs within the organization. The actual impact of the solution on the organization's performance and profitability depends on many other factors, such as the market demand, the customer satisfaction, the operational efficiency, the competitive advantage, etc.

Answer : C

Cost-benefits analysis is a technique used in the business case development task, not in the requirements verification task. The other options are all general techniques that can be used to verify the requirements with the stakeholders and ensure they are complete, correct, and consistent.Reference:BABOK Guide, section 4.5.3, page 117; section 4.6.3, page 123.

Answer : D

Requirements verification is the task of ensuring that the requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work.It involves checking that the requirements are clear, consistent, complete, correct, feasible, and testable, and that they conform to the agreed standards and conventions12. Defining assumptions and constraints, organizing requirements, and specifying and modeling requirements are other tasks in the requirements analysis knowledge area, but they do not focus on the quality of the requirements as much as requirements verification does[3][3].Reference:

1: BABOK Guide, Version 3.0, p. 41

2:Business Analysis Expert Certification, CCBA | IIBA

[3][3]:A Comprehensive Guide to CCBA Certification - Business Analysis Blog