Cyber Monday 2024! 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 6 Question 86 Discussion

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

Contribute your Thoughts:

Luisa
2 months ago
I'm going with B. A good old-fashioned requirements review is the way to go. Let's hope the stakeholders don't fall asleep during the presentation!
upvoted 0 times
...
Marge
2 months ago
A) A defect tracking log? Really? That's not going to help with getting approval. The business analyst should focus on the actual requirements, not past issues.
upvoted 0 times
Yasuko
1 months ago
C) Provide a defect tracking log for review.
upvoted 0 times
...
Lavera
1 months ago
A) I agree, focusing on the actual requirements is key to getting approval.
upvoted 0 times
...
Chau
1 months ago
B) Create and maintain an audit history log of changes to requirements.
upvoted 0 times
...
Christiane
2 months ago
A) Conduct a formal or informal review of the requirements.
upvoted 0 times
...
...
Maybelle
2 months ago
D) An audit history log is great, but it's not enough on its own. The stakeholders need to be involved in the process and have a chance to provide input.
upvoted 0 times
...
Brittney
2 months ago
C) Sending an email is just too informal. The business analyst needs to have a proper meeting or review session to discuss the requirements and get the stakeholders' feedback.
upvoted 0 times
Chaya
1 months ago
A) Conduct a formal or informal review of the requirements.
upvoted 0 times
...
Reita
1 months ago
C) Sending an email is just too informal. The business analyst needs to have a proper meeting or review session to discuss the requirements and get the stakeholders' feedback.
upvoted 0 times
...
Beata
2 months ago
B) Create and maintain an audit history log of changes to requirements.
upvoted 0 times
...
Thea
2 months ago
A) Conduct a formal or informal review of the requirements.
upvoted 0 times
...
...
Monte
3 months ago
B) Conducting a formal or informal review of the requirements is the way to go. That's the best way to get stakeholder approval and make sure everyone is on the same page.
upvoted 0 times
Stanton
2 months ago
It's important to get stakeholder approval through a thorough review process.
upvoted 0 times
...
Julie
2 months ago
Once the review is done, we can move forward with requesting approval.
upvoted 0 times
...
Claribel
2 months ago
Agreed, that way we can ensure everyone is aligned before moving forward.
upvoted 0 times
...
Ressie
2 months ago
We should make sure all stakeholders are involved in the review process.
upvoted 0 times
...
Marguerita
2 months ago
We should definitely conduct a formal review of the requirements.
upvoted 0 times
...
Kenneth
2 months ago
Agreed, a formal review will ensure everything is in order.
upvoted 0 times
...
Lemuel
2 months ago
Let's review the requirements before requesting approval.
upvoted 0 times
...
...
Helga
3 months ago
Sending an email requesting approval of requirements might not be sufficient. It's better to have a face-to-face discussion.
upvoted 0 times
...
Martina
3 months ago
I believe creating and maintaining an audit history log of changes to requirements is also crucial for transparency.
upvoted 0 times
...
Wei
3 months ago
I agree with Rozella. It's important to get feedback from stakeholders before final approval.
upvoted 0 times
...
Rozella
3 months ago
I think the business analyst should conduct a formal or informal review of the requirements.
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