PMI Exam PMI-PBA Topic 5 Question 74 Discussion

Actual exam question for PMI's PMI-PBA exam

Question #: 74
Topic #: 5

A business analyst is working on a system enhancement project and has completed the requirements according to the requirements management plan. The business analyst is now ready to request approval from the stakeholders.

How should the business analyst obtain approval?

AProvide a defect tracking log for review.

BConduct a formal or informal review of the requirements.

CSend an email requesting approval of requirements.

DCreate and maintain an audit history log of changes to requirements.

Show Suggested Answer

Suggested Answer: B

by Whitley at Apr 10, 2024, 11:59 PM

Limited Time Offer

25%

Off

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Amina

5 months ago

It seems like most of us are in favor of conducting a formal or informal review to obtain approval. This way, stakeholders can provide feedback and clarify any misunderstandings.

upvoted 0 times

...

Yen

5 months ago

Creating and maintaining an audit history log of changes to requirements is also important to track any modifications made during the process.

upvoted 0 times

...

Alease

6 months ago

Sending an email requesting approval might not be as effective as actually discussing the requirements with the stakeholders.

upvoted 0 times

...

Hayley

6 months ago

I agree with User2, reviewing the requirements with stakeholders ensures that everyone is on the same page.

upvoted 0 times

...

Loreen

6 months ago

I think conducting a formal or informal review of the requirements would be the most appropriate way.

upvoted 0 times

...

Nikita

6 months ago

What do you think is the best way for the business analyst to obtain approval for the requirements?

upvoted 0 times

...

Kenneth

7 months ago

You know, I'm just gonna go with option A. Providing a defect tracking log for review might be the best way to demonstrate that the requirements are solid and ready for approval.

upvoted 0 times

...

Ronnie

7 months ago

Haha, true that! But hey, at least they're not asking us to create a 50-page requirements document. Small mercies, am I right?

upvoted 0 times

...

Louis

7 months ago

I'm with you both. Although, I have to say, I'm a bit surprised they didn't include 'hold a mandatory 3-hour PowerPoint presentation' as one of the options. That's the usual way to get approval, isn't it?

upvoted 0 times

...

Reed

7 months ago

I agree with you, B is the way to go. A defect tracking log might be useful later on, but it's not what's needed right now. And sending an email just doesn't seem like a robust enough approach for getting approval.

upvoted 0 times

...

Emerson

7 months ago

Hold up, what about option D? Creating and maintaining an audit history log of changes to requirements could be important for traceability and documentation.

upvoted 0 times

...

Ria

7 months ago

Hmm, this is an interesting one. I think the answer is B - conducting a formal or informal review of the requirements. Getting the stakeholders' buy-in is crucial at this stage, and a review session would be the best way to ensure they're on board with the changes.

upvoted 0 times

...

Joesph

7 months ago

Really? I was thinking option C - sending an email requesting approval. That seems like the easiest and most straightforward approach.

upvoted 0 times

...

Rene

7 months ago

Hmm, I'm leaning towards option B - conducting a formal or informal review of the requirements. That seems like the most thorough way to get buy-in from the stakeholders.

upvoted 0 times