Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-PBA Topic 5 Question 74 Discussion

Actual exam question for PMI's PMI Professional in Business Analysis exam
Question #: 74
Topic #: 5
[All PMI Professional in Business Analysis Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Loreen
1 days ago
User2: I think conducting a formal or informal review of the requirements would be the most appropriate way.
upvoted 0 times
...
Nikita
2 days ago
User1: What do you think is the best way for the business analyst to obtain approval for the requirements?
upvoted 0 times
...
Kenneth
24 days 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
24 days 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
25 days 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
26 days 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
26 days 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
27 days 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
27 days 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
28 days 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
Brice
6 days ago
Getting approval through a review process ensures that the requirements are well understood by all parties involved.
upvoted 0 times
...
Jina
7 days ago
It's important to involve stakeholders in the process, so a review is definitely the way to go.
upvoted 0 times
...
Amie
8 days ago
I prefer option B too, a review helps catch any discrepancies early on.
upvoted 0 times
...
Hubert
9 days ago
True, maintaining an audit history log is crucial for tracking changes and decision-making.
upvoted 0 times
...
Janessa
10 days ago
I think option D is also important. Keeping a log of changes shows transparency and accountability.
upvoted 0 times
...
Magdalene
11 days ago
I agree, a review allows stakeholders to provide feedback and make sure everything is clear.
upvoted 0 times
...
Iluminada
12 days ago
Option B seems like a good choice. A review would ensure everyone is on the same page.
upvoted 0 times
...
...
Blossom
1 months ago
I agree, this is a tough one. I think the key is to understand the requirements management plan and the stakeholder approval process.
upvoted 0 times
...
Lisandra
1 months ago
Oh man, this question is tricky. I've been studying for this exam, and I'm not sure which answer is the best approach.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77