IIBA CCBA Exam
Certification of Competency in Business Analysis (Page 6 )

Updated On: 30-Jan-2026

A business analyst has just completed an elicitation event.
What stakeholder(s) is/are involved in the documentation of the elicitation results?

  1. Business analyst and key stakeholders
  2. Business analyst
  3. Project manager, project team, and business analyst
  4. Project manager, business analyst, and project sponsor

Answer(s): B

Explanation:

Only the business analyst is involved in the documentation of the elicitation results. Answer D is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not the project manager and project sponsor.
Answer C is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not the project manager and project team.
Answer A is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not key stakeholders.



You are documenting the requirements attribute for your requirements management plan.
Which attribute would you use if you want to identify the person who created the requirements?

  1. Absolute reference
  2. Ownership
  3. Requirements sponsor
  4. Author of the requirements

Answer(s): D

Explanation:

The author of the requirements is a good attribute to include in the requirements attribute. This allows follow- up Questions or clarifications, if necessary, for the project. Answer A is incorrect. Absolute reference is needed to define specific requirements. A numeric coding is preferred over text and this code should not be reused. Answer B is incorrect. The ownership attribute describes who will be the owner of the requirement or deliverable. The owner isn't necessarily the same person who created the requirement. Answer C is incorrect. There is not an attribute called requirements sponsor, so this choice is not valid.



Which of the following is an output of the Identify Stakeholders process?

  1. Scope baseline
  2. Project charter
  3. Stakeholder register
  4. Project scope statement

Answer(s): C

Explanation:

The Identify Stakeholders process identifies all people or organizations that are impacted by the project. It also documents relevant information regarding their interests, involvement, and impact on project success.
Stakeholder register and stakeholder management strategy are outputs of this process. Answer B is incorrect. Project charter is one of the inputs of the Identify Stakeholders process. Answer A is incorrect. Scope baseline is one of the outputs of the Create Work Breakdown Structure (WBS) process.
Answer D is incorrect. Project scope statement is one of the outputs of the Define Scope process.



There are five tasks and six inputs to requirements management and communication. As a business analyst, you'll need to gather all of the following inputs for this knowledge area except for which one?

  1. Requirement Management Plan
  2. Work breakdown structure
  3. Business Analysis (BA) communication plan
  4. Solution scope

Answer(s): B

Explanation:

The work breakdown structure (WBS) is a tool used to define the scope of work and to develop estimates. This tool creates a hierarchy of work by decomposing the project scope into smaller and smaller pieces. WBS can perform the following tasks:
It may break the project into iterations, releases, or phases. It can break deliverables into work packages.
It may break activities into smaller tasks.
Answer C, A, and D are incorrect. The inputs to requirements management and communication are as follows:
Business Analysis (BA) communication plan Requirement Management Plan Solution Scope Requirements Structure
Organizational Process Assets
Stakeholder, List, Roles, and Responsibilities Requirements



You are the business analyst for your organization and you're working with your manager to discuss the constraints and assumptions that may affect the requirements. Your manager wants to know from where you've derived the list of constraints and assumptions.
What's the best answer as to where assumptions and constraints are identified?

  1. Assumptions and constraints are identified through a review of project requirements.
  2. Assumptions and constraints are identified through elicitation from stakeholders.
  3. Assumptions and constraints are identified through risk identification and analysis.
  4. Assumptions and constraints are identified through document analysis.

Answer(s): B

Explanation:

Assumptions and constraints are identified through elicitation from stakeholders. Answer D is incorrect. Assumptions and constraints are not identified through document analysis. Answer C is incorrect. Assumptions and constraints are not identified through risk identification, though false assumptions may be subject to risk analysis. Answer A is incorrect. Assumptions and constraints are not identified through a review of project requirements.



Viewing page 6 of 104
Viewing questions 26 - 30 out of 638 questions



Post your Comments and Discuss IIBA CCBA exam prep with other Community members:

Join the CCBA Discussion