IIBA Updated CCBA Exam Questions and Answers by evelina

The BA should select CRUD (Create, Read, Update, and Delete) matrix as the technique that would be appropriate for determining how and who uses data across the identified processes. CRUD matrix is a table that shows the actions that different roles or stakeholders can perform on data entities or objects within a system or solution. CRUD matrix can help to define the data access rights and permissions for each role or stakeholder, as well as the data dependencies and interactions among processes.

The other options are incorrect because:

Option A is incorrect because stakeholder list, map, or personas are not techniques for determining how and who uses data, but techniques for identifying and analyzing stakeholders. Stakeholder list, map, or personas are tools that provide information about the characteristics, needs, expectations, and influences of stakeholders. Stakeholders are individuals or groups who have an interest or stake in a change or solution.

Option B is incorrect because data dictionary is not a technique for determining how and who uses data, but a technique for defining and describing data. Data dictionary is a repository that contains the definitions, attributes, formats, and relationships of data elements or objects within a system or solution. Data dictionary can help to standardize and document the data requirements and specifications for a solution.

Option D is incorrect because decision model is not a technique for determining how and who uses data, but a technique for modeling and analyzing decisions. Decision model is agraphical representation of the logic, rules, criteria, and outcomes of decisions within a system or solution. Decision model can help to simplify and clarify the decision-making process and its impact on the solution.

References:

BABOK Guide v3, section 10.16: CRUD Matrix

CCBA Practice Test, question 5

Quantitative performance measure is being practiced by the software development company that evaluates solutions against the number of defects reported in the testing phase. Quantitative performance measures are those that use numerical values or statistics to assess the performance of a solution or an organization. They can help to measure aspects such as quality, efficiency, productivity, profitability, customer satisfaction, etc. The number of defects is a quantitative measure of quality that indicates how well a solution meets its specifications and expectations. References: : Quantitative Performance Measures

The BA recommended the requirement traceability approach because it is consistent with the organizational standards and the CCBA® or the BABOK® Guide, which suggest that requirement traceability is a core competency and a key technique for business analysis. Requirement traceability helps to ensure that the solution conforms to the requirements, that the requirements are aligned with the business objectives and stakeholder needs, and that the requirements are verified and validated. References: While I cannot provide direct links, I recommend reviewing the following sources for more information on requirement traceability:

CCBA® handbook1, which provides the eligibility requirements, exam blueprint, and application process for the CCBA® certification.

BABOK® Guide2, which defines the knowledge areas, tasks, techniques, and competencies for business analysis, including requirement traceability as a technique under the Requirements Life Cycle Management knowledge area.

Business Analysis Expert Certification, CCBA® | IIBA®3, which offers an overview of the CCBA® certification, its benefits, and its competencies.

Requirements traceability : What, why and how > Business Analyst …2, which explains the concept, purpose, and benefits of requirement traceability, and provides some examples and tips on how to implement it.

The previous task that could assist the BA in performing the impact analysis is to create requirement relationships. This is because creating requirement relationships is the process of identifying and documenting the connections or associations between different requirements or other elements. Creating requirement relationships can help to understand the dependencies, traceability, composition, generalization, or other types of relationships among the requirements. This can facilitate the impact analysis of a change by showing how it affects other related requirements or elements. The other options are not as helpful or relevant as creating requirement relationships. References:

BABOK Guide, section 4.3.2: Validate Requirements

CCBA Practice Test, question 107