IIBA Certified Business Analysis Professional CBAP Exam Questions

Answer : D

Risk analysis is the process of analyzing the areas of a project that are most affected by risk. It involves estimating the probability and impact of each identified risk, as well as assessing the quality and reliability of the available data. Risk analysis helps to prioritize the risks based on their severity and potential effect on the project objectives and deliverables. Risk analysis also helps to identify the root causes and triggers of the risks, as well as the interrelationships and dependencies among the risks. Risk analysis is the second step of risk management, which also includes risk identification, risk response, and risk monitoring and control.Reference: [IIBA BABOK Guide v3], section 11.2.2, page 387;CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 231;CBAP Sample Questions, question 234.

Answer : B

The user interface is the part of a system that allows the actual users to interact with one another, the system, or data moved between two users. The user interface is the means by which the users can input, view, manipulate, or output information through the system. The user interface can be graphical, textual, auditory, tactile, or a combination of these. The user interface is an important aspect of the user experience and usability of the system. The user interface should be designed to meet the user needs, preferences, and expectations, as well as the system requirements and constraints.Reference:IIBA BABOK Guide v3, section 9.1.2, page 326;CBAP / CCBA Certified Business Analysis Study Guide, chapter 7, page 251;CBAP Exam Questions - Institute i4, question 241.

Answer : C

A data dictionary is a model that defines the name of the data, data aliases, and description of system data. A data dictionary is a collection of metadata that provides information about the data elements and structures in a system or a database. A data dictionary can include the following information for each data element: name, alias, description, data type, size, format, domain, constraints, default value, source, owner, and usage. A data dictionary can help the business analyst to understand the data requirements, design the data model, and ensure the data quality and consistency. A data dictionary is different from a class model, which is a model that defines the classes, attributes, operations, and relationships in an object-oriented system. A data dictionary is also different from an entity relationship model, which is a model that defines the entities, attributes, relationships, and cardinalities in a relational database. A data dictionary is not a CRUD matrix, which is a model that defines the create, read, update, and delete operations for each data element and user role in a system.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Requirements Analysis, page 288-289.

Data Dictionary - Tutorialspoint, paragraph 1-2

What is a Data Dictionary? | Definition and How To, paragraph 1-2

Data Dictionary - Project Management Knowledge, paragraph 1

Answer : B

A regulator is a stakeholder who may be responsible to dictate that a specific process or technique be followed during the requirements elicitation activities. A regulator is an external stakeholder who has the authority to enforce laws, rules, standards, or policies that affect the project or the solution. A regulator may impose certain requirements or constraints on the project or the solution, such as compliance, security, privacy, or quality. A regulator may also require the use of specific methods, tools, or documentation for eliciting, analyzing, or validating the requirements. The other options are not necessarily responsible for dictating the process or technique for requirements elicitation, although they may have some influence or preference. A project manager is a stakeholder who is responsible for planning, executing, monitoring, and controlling the project activities and resources. A project manager may collaborate with the business analyst to select the appropriate process or technique for requirements elicitation, but does not have the authority to dictate it. A functional management is a stakeholder who is responsible for the day-to-day operations of a specific function or department within the organization, such as finance, marketing, or human resources. A functional management may provide input or feedback on the requirements elicitation process or technique, but does not have the authority to dictate it. A project sponsor is a stakeholder who is responsible for initiating, funding, and supporting the project or the solution. A project sponsor may approve or endorse the requirements elicitation process or technique, but does not have the authority to dictate it.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 175-176.

Engaging Stakeholders in Elicitation and Collaboration, paragraph 4

Top 10 Most Common Requirements Elicitation Techniques, paragraph 2

A Review of Fundamental Tasks in Requirements Elicitation, paragraph 1

Answer : C

A data flow diagram (DFD) is a graphical representation of how data moves through a system or process. It shows the sources and destinations of data, the processes that transform data, and the data stores that hold data. A DFD can help the business analyst understand the current state of a system, identify gaps or inefficiencies, and design a new or improved system. A DFD is different from a network topology map, which shows the physical layout and connections of network devices. A DFD is also different from a data dictionary and glossary, which provide definitions and descriptions of data elements and terms. A DFD is not a prototype, which is a working model or simulation of a system or product.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Requirements Analysis, page 287-288.

Essential Guide to Business Process Mapping, Section: Data Flow Diagrams, paragraph 1-2.

Answer : D

A model is a representation of a system or a process that helps stakeholders and customers visualize the potential system. Models can use different forms, such as flowcharts, graphs, diagrams, or prototypes, to show the structure, behavior, or functionality of the system. Models are useful for communicating, analyzing, verifying, and validating the requirements.

Models are not slices of the project solution (A), although they may show some aspects of the solution. Models are not meant to simplify the requirements for common stakeholders (B), but rather to help all stakeholders understand the requirements better. Models are not statistics for the return on investment, time saved, and other mathematics , although some models may use quantitative data to support the requirements.

Answer : D

Lessons learned is a technique that involves identifying and documenting the knowledge gained from a project or an activity, and sharing it with relevant stakeholders. Lessons learned can include the successes, failures, best practices, and improvement opportunities that occurred during or after the project or activity. Lessons learned can help the BA to understand the stakeholders' level of satisfaction, to offer them an opportunity to help improve the working relationships, and to apply the learned knowledge to future projects or activities. The other options are not the best techniques for this purpose, as they are more focused on identifying and managing risks, generating and evaluating ideas, or engaging stakeholders in a fun and creative way.Reference:CBAP Handbook,CBAP Study Guide,BABOK Guide