CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. IIBA
  5. CCBA

Free CCBA Exam Braindumps (page: 23)

Page 23 of 129
PDF with 513 Questions

When do change requests generally increase in a project?

  1. Towards the beginning of the project.
  2. During the project scope management processes.
  3. During the project's launch.
  4. Towards the end of the project.

Answer(s): D

Explanation:

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.



You are the business analyst for your organization and you're working with the key stakeholders to validate the requirements. In your review, you have determined the business value of each requirement and you've discovered three requirements that do not deliver direct or indirect value to the stakeholders.
What should you do with these requirements?

  1. Determine their purpose in the requirements set.
  2. Justify their existence.
  3. See if the requirements are integrated with other requirements.
  4. Remove them from the requirements set.

Answer(s): D

Explanation:

Requirements that do not add direct or indirect value need to be removed from the requirements set.
Answer B is incorrect. It's not best to justify the existence of requirements; requirements must contribute to the business need or solution.
Answer A is incorrect. If the requirements do not add some type of value, then you don't need to determine the purpose of the requirements. This answer isn't valid.

Answer C is incorrect. If the requirements were integrated or linked to other requirements, then it would already be evident that the requirements offer an indirect value to the requirements, solution, or stakeholders.



According to 'A Guide to the Business Analysis Body of Knowledge', when should the business analyst and an organization actually start requirements allocation?

  1. As soon as a budget has been created
  2. After approval of the requirements
  3. After the project charter
  4. As soon as the solution approach is determined

Answer(s): D

Explanation:

Requirements allocation typically begins early in the project lifecycle (as soon as the solution approach is determined) and will continue to be performed until all valid requirements are allocated. Allocation typically continues through design and construction of a solution. Answer C is incorrect. Requirements allocation doesn't have to wait until the project has been chartered. Answer B is incorrect. Approval of the requirements is good, but the solution scope for the requirements needs to be created to begin allocating the requirements. Answer A is incorrect. The budget creation isn't linked to the requirements allocation process.



You are working with the project stakeholders to analyze and prioritize their requirements for the project. One of the project requirements is to achieve a high-level of customer satisfaction for the project deliverable.
What is the danger in this project requirement?

  1. Achieving customer satisfaction is a risk, as the project manager cannot control how satisfied the customer will be with the project deliverables.
  2. Achieving customer satisfaction is an assumption and should be documented in the project scope.
  3. Achieving customer satisfaction should always map to the quality requirements for the project.
  4. Achieving customer satisfaction is a subjective requirement and entails a high level of risk of being successfully accomplished.

Answer(s): D

Explanation:

While every project manager wants to achieve customer satisfaction, this subjective term is too vague to be measured or accounted for.
What one person deems customer satisfaction may be low compared to another. Requirements need metrics to determine the level of success.
Answer C is incorrect. The subjective requirements cannot be measured or mapped to quality requirements. Answer B is incorrect. This is not an assumption, but a subjective requirement. Answer A is incorrect. This is not a risk, but a requirement that needs metric for measurement attached to it.



Page 23 of 129



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

Mohammed Basheer commented on August 23, 2017
Wrote the exam today and I passed it easily. Valid dump!
UNITED STATES
upvote