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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PMI Exam PMI-PBA Topic 5 Question 74 Discussion

Actual exam question for PMI's PMI-PBA exam
Question #: 74
Topic #: 5
[All PMI-PBA 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

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
8 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
8 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
9 months ago
Sending an email requesting approval might not be as effective as actually discussing the requirements with the stakeholders.
upvoted 0 times
...
Hayley
9 months ago
I agree with User2, reviewing the requirements with stakeholders ensures that everyone is on the same page.
upvoted 0 times
...
Loreen
10 months ago
I think conducting a formal or informal review of the requirements would be the most appropriate way.
upvoted 0 times
...
Nikita
10 months ago
What do you think is the best way for the business analyst to obtain approval for the requirements?
upvoted 0 times
...
Kenneth
11 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
11 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
11 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
11 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
11 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
11 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
11 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
11 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
Brice
10 months ago
Getting approval through a review process ensures that the requirements are well understood by all parties involved.
upvoted 0 times
...
Jina
10 months ago
It's important to involve stakeholders in the process, so a review is definitely the way to go.
upvoted 0 times
...
Amie
10 months ago
I prefer option B too, a review helps catch any discrepancies early on.
upvoted 0 times
...
Hubert
10 months ago
True, maintaining an audit history log is crucial for tracking changes and decision-making.
upvoted 0 times
...
Janessa
10 months ago
I think option D is also important. Keeping a log of changes shows transparency and accountability.
upvoted 0 times
...
Magdalene
10 months ago
I agree, a review allows stakeholders to provide feedback and make sure everything is clear.
upvoted 0 times
...
Iluminada
10 months ago
Option B seems like a good choice. A review would ensure everyone is on the same page.
upvoted 0 times
...
...
Blossom
11 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
Luann
9 months ago
D) Create and maintain an audit history log of changes to requirements.
upvoted 0 times
...
Gracie
9 months ago
That sounds like the right approach.
upvoted 0 times
...
Shakira
9 months ago
B) Conduct a formal or informal review of the requirements.
upvoted 0 times
...
...
Lisandra
11 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