IIBA CCBA Online Practice Questions and Exam Preparation

IIBA CCBA Online Questions & Answers

• Question 221:

  A government agency has initialed a project to implement a customer registry that will be shared across multiple agencies. Early estimates indicate there will be hundreds of requirements. While determining the requirements traceability approach, what factor takes precedence?

  A. Number of defects
  B. Cost of tracing
  C. Number of stakeholders
  D. Cost of testing
  C. Number of stakeholders

  ---

  The number of stakeholders is the most important factor to consider when determining the requirements traceability approach, because it affects the complexity and communication of the requirements. The more stakeholders involved, the more traceability is needed to ensure alignment and agreement among them. The number of defects, the cost of tracing, and the cost of testing are not as critical as the number of stakeholders. References: BABOK Guide v3, page 159; CCBA Mock Test,

• Question 222:

  Henry is meeting with Janet, the business analyst of the organization. They are discussing an opportunity to create a new service their company can provide, though the startup of the service would take time and an investment. Henry wants Janet to explore the possibility of this new venture. What activity is Henry asking Janet to complete?

  A. Brainstorm the business need.
  B. Create a data diagram for the service.
  C. Define the business need.
  D. Elicit the requirements of the proposal.
  C. Define the business need.

  ---

  This is the most common business analysis activity in enterprise analysis. Henry is asking Janet to define the business need. The purpose of defining business need is to identify and define why a change to organizational systems or capabilities is required. The business need is an important step in any business analysis effort. The business analyst tries to find a solution for the problem defined by the business need. A is incorrect. This isn't an example of a brainstorming session, as it's just Janet exploring the need for the new service. Brainstorming is a technique to gather general data. It can be used to identify risks, ideas, or solutions to issues by using a group of team members or subject-matter expert. Brainstorming is a group creativity technique that also provides other benefits, such as boosting morale, enhancing work enjoyment, and improving team work. It contains the following aims. Production of numerous new ideas Derivation of themes from those ideas for further analysis D is incorrect. This is not an example of requirements elicitation, though Janet's findings could lead to elicitation. B is incorrect. A data diagram shows the flow of data into and out of a system.

• Question 223:

  During planning, elicitation, and sign off of requirements, the stakeholders felt that their opinions were not heard and information was not frequently shared. What major competency was lacking in this process?

  A. Collaboration
  B. Trustworthiness
  C. Information
  D. Communication
  D. Communication

  ---

  The major competency that was lacking in this process was communication. Communication is the ability to exchange information and ideas effectively with a variety of audiences, using various modes and techniques. Communication is essential for planning, eliciting, and signing off requirements, as it ensures that the stakeholders are informed, engaged, and satisfied with the requirements process and deliverables. If the stakeholders felt that their opinions were not heard and information was not frequently shared, it indicates that the communication was poor or ineffective, and it could lead to misunderstandings, conflicts, or missed requirements.

• Question 224:

  When do change requests generally increase in a project?

  A. Towards the beginning of the project.
  B. During the project scope management processes.
  C. During the project's launch.
  D. Towards the end of the project.
  D. Towards the end of the project.

  ---

  Changes generally increase towards the end of the project. This can be due to a loosely defined scope, lack of requirements, and other reasons. Answer B is incorrect. The scope management process happens throughout the project until the scope is completed. Answer C is incorrect. Changes are easier to incorporate at the launch of the project but generally do not happen until later in the project. Answer A is incorrect. Scope changes generally happen towards the end of the project.

• Question 225:

  Which task in the requirements analysis knowledge area is best described as ensuring that the requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work?

  A. Defining assumptions and constraints
  B. Organizing requirements
  C. Specifying and modeling requirements
  D. Requirements verification
  D. Requirements verification

  ---

  Requirements verification is the correct answer. This task verifies that requirements specifications and models are accurate so that the endeavor may continue to achieve the best solution for the organization. Answer A is incorrect. The task of defining assumptions and constraints identifies factors other than requirements that may affect which solutions are viable. Answer C is incorrect. The task to specify and model requirements is used to analyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams, and formal models. Answer B is incorrect. The purpose of organizing requirements is to create a set of views of the requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.

• Question 226:

  Project work is taking place to evaluate whether a system's requirements can be met via creating internally, purchasing from others, or a combination of the two. What goal is addressed by this analysis?

  A. Developing the project plan
  B. Outlining the change control strategy
  C. Defining the solution approach
  D. Validating the requirements
  C. Defining the solution approach

  ---

  The solution approach is a description of how a need will be addressed by a solution. It includes an analysis of whether to build, buy, or reuse a solution component, or a combination of these options. Developing the project plan, outlining the change control strategy, and validating the requirements are not goals of this analysis. References: BABOK Guide v3, page 30; CCBA Mock Test,

• Question 227:

  When a business analyst completes the task of organizing requirements, he is completing two key objectives. What are the two objectives?

  A. The business analyst should categorize the requirements first by functional or non- functional decomposition and then structure the categories by identified prioritization elements.
  B. The business analyst should strive to find logic in the organizational structure and to establish a prioritization approach on key elements.
  C. The business analyst should aim to understand which models are appropriate for the business domain and solution scope and to identify model interrelationships and dependencies.
  D. The business analyst should work with stakeholders to organize defined categories and then to structure each category by a key performance indicator.
  C. The business analyst should aim to understand which models are appropriate for the business domain and solution scope and to identify model interrelationships and dependencies.

  ---

  The two key objectives when organizing requirements are to understand which models are appropriate for the business domain and solution scope and to identify model interrelationships and dependencies. Answer: B is incorrect. This is not a valid statement about the task of organizing requirements. Answer: D is incorrect. Each requirement will have a key performance indicator, but it's not an element for organizing requirements. Answer A is incorrect. There is not a structural or organizational reason to sort requirements by functional or non-functional decomposition.

• Question 228:

  Management comes to you and asks you to complete some specifications and models about the current state of the organization. Management wants you to complete this business analysis activity as soon as possible and report back to

  them with your findings.

  What is the primary purpose of the specify and model requirements process?

  A. To analyze the roles and responsibilities of users within the organization to determine how the processes may be improved.
  B. To analyze the utility function within the organization to determine how risk tolerance may allow for new opportunities.
  C. To analyze the functioning of an organization and to provide an insight into opportunities for improvement.
  D. To analyze the processes of an organization to determine what processes can be improved, removed, or added.
  C. To analyze the functioning of an organization and to provide an insight into opportunities for improvement.

  ---

  The specify and model requirements is a business analysis process to analyze the functioning of an organization and provide an insight into opportunities for improvement. Answer D, A, and B are incorrect. These are not valid definitions of the specify and model requirements process.

• Question 229:

  You are a business analyst for your organization and you're working with the stakeholders to identify the primary inputs to the business analysis approach. Which of the following will help determine whether a plan- driven or change-driven approach is appropriate?

  A. Organizational process assets
  B. Expert Judgement
  C. Business need
  D. Penalty of not seizing the opportunity
  A. Organizational process assets
  B. Expert Judgement
  C. Business need

  ---

  These are the primary inputs of planning the business analysis approach. The primary input of planning the business analysis approach is to consider the problem or opportunity faced by the organization. Time allowed for business analysis planning does have an effect on the thoroughness of the business analysis activities. The risk associated with the plan is also considered.

• Question 230:

  A business analyst (BA) is assigned a new project and is beginning to prepare for elicitation. Which task must the BA complete before preparation of the elicitation process can begin?

  A. Coordinate meeting logistics
  B. Approve anticipated expenses
  C. Gather contact information of stakeholder
  D. Collect information on the business need
  D. Collect information on the business need

  ---

  The task that the BA must complete before preparation of the elicitation process can begin is collecting information on the business need. This means that the BA should gather relevant data or facts that describe or justify why a change is required or desired by stakeholders or an organization. Collecting information on the business need can help the BA to understand and define the scope, objectives, and benefits of a project or an initiative. The other options are incorrect because: Option A is incorrect because coordinating meeting logistics is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs during preparation of the elicitation process. Coordinating meeting logistics means arranging and confirming the details of the meeting such as date, time, location, agenda, participants, etc. Option B is incorrect because approving anticipated expenses is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs after preparation of the elicitation process. Approving anticipated expenses means obtaining authorization or consent for the expected costs or resources required for the elicitation process. Option C is incorrect because gathering contact information of stakeholders is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs during preparation of the elicitation process. Gathering contact information of stakeholders means collecting and documenting the names, roles, communication channels, and availability of the stakeholders who will be involved in the elicitation process.