exam questions

Exam CBAP All Questions

View all questions & answers for the CBAP exam

Exam CBAP topic 1 question 78 discussion

Actual exam question from IIBA's CBAP
Question #: 78
Topic #: 1
[All CBAP Questions]

Henry is the business analyst for the UUH Organization. Currently Henry is working on several work products as part of the requirements development process.
He may need to share these work products with the stakeholders.
Which of the following is not an example of a work product?

  • A. Requirements documentation
  • B. Interview questions and notes
  • C. Meeting agendas and minutes
  • D. Presentation slides
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
NgocThanh
5 days, 7 hours ago
Selected Answer: C
The correct answer is: C. Meeting agendas and minutes Explanation: Work products are outputs created as part of the business analysis process to document or support the development, communication, and management of requirements. Examples of work products include: • A. Requirements documentation: Core deliverable in requirements development. • B. Interview questions and notes: Documentation used to elicit and record requirements. • D. Presentation slides: Used to communicate requirements or findings to stakeholders. C. Meeting agendas and minutes, while helpful for organizing and documenting discussions, are not directly part of the requirements development process. They are considered administrative tools rather than work products specifically tied to the requirements development process.
upvoted 1 times
...
CBAPCohort6
2 months, 1 week ago
Selected Answer: C
Meeting agendas and minutes are typically not categorized as work products because they are more focused on the logistics of meetings rather than the analysis itself
upvoted 1 times
...
Farooq_95
8 months ago
Selected Answer: C
Meeting agenda and minutes are administrative document that document the discussions during the meetings. While they may be shared with stakeholders to provide transparency and updates on project activities, they are not direct outputs of the requirements development process and do not specifically relate to documenting or analyzing requirements. BABOK v3 defines work product as a document or collection of notes or diagrams used by the business analyst during the requirements development process. So, all of the other options can be used directly by BA to develop requirements. Although requirements documentation is an output of the requirements development process, it is still a work product as it encompasses the collection of documents, specifications, user stories, use cases, and other artifacts that the business analyst uses and develops throughout the requirements development process.
upvoted 2 times
Farooq_95
8 months ago
all options could be considered work products in a broad sense, "C. Meeting agendas and minutes" is the least directly related to the core activities of requirements development and analysis compared to the other options provided.
upvoted 1 times
...
...
Rabbitsfoot
9 months ago
Selected Answer: C
as below
upvoted 1 times
...
Rabbitsfoot
9 months ago
C. Meeting agendas and minutes. Meeting agendas and minutes are artifacts related to the management of meetings and the documentation of discussions, decisions, and action items. While they may involve inputs from the business analyst and could contain information related to requirements discussions, they are not direct outputs of the requirements development process. Instead, they facilitate communication and coordination among stakeholders during meetings. Therefore, meeting agendas and minutes are not considered typical work products of the requirements development process. v3 - pg 445: deliverable: Any unique and verifiable work product or service that a party has agreed to deliver. pg 455: work product (business analysis): A document or collection of notes or diagrams used by the business analyst during the requirements development process.
upvoted 2 times
...
Rfcuenca
11 months, 2 weeks ago
Option 1 Babok v2 page 74 Requirements documentation would be a deliverable and not work product
upvoted 1 times
...
Atzewine
1 year, 9 months ago
Work product (business analysis): A document or collection of notes or diagrams used by the business analyst during the requirements development process.(page 456 babok3). Requirements documentation is not a document use during requirements development process. It's an output, It can't be an input. Answer is A
upvoted 2 times
Farooq_95
8 months ago
Its correct that requirements documentation is an output and not an input for requirements development process. But, it is still a work product as it encompasses the collection of documents, specifications, user stories, use cases, and other artifacts that the business analyst uses and develops throughout the requirements development process.
upvoted 1 times
...
...
Sisichels
2 years, 9 months ago
the answer is correct, when you look at the definition of what a work product is as defined by BABOK
upvoted 1 times
...
MFZZ
2 years, 10 months ago
Sorry meant to say A
upvoted 1 times
...
MFZZ
2 years, 10 months ago
Interviews are a part of elicitation which is a work product. Incorrect answer is B
upvoted 1 times
...
MFZZ
2 years, 10 months ago
Ans: A B refers to Surveys
upvoted 2 times
...
AnyU
2 years, 11 months ago
Selected Answer: B
B seems to be the only option that is NOT relevant
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago