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

Salesforce Exam Certified-Business-Analyst Topic 5 Question 31 Discussion

Actual exam question for Salesforce's Salesforce Certified Business Analyst exam
Question #: 31
Topic #: 5
[All Salesforce Certified Business Analyst Questions]

After stakeholders formally signed off on requirements, the business analyst (BA) received numerous emails requesting changes to Salesforce during uses acceptance testing (UAT). The BA quickly became overwhelmed by the requests and needs a way to organize and peritonitis them.

What should the BA use to help them organize these requests?

Show Suggested Answer Hide Answer
Suggested Answer: A

This answer states that change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT after receiving numerous emails from stakeholders who formally signed off on requirements. Change request log is a document or a file that records and tracks requests for changes to a project or a product, such as adding, modifying, or removing a feature or a functionality. Change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT because it helps the BA to manage and monitor the requests for changes, and to evaluate and approve or reject them based on their impact, urgency, or feasibility. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills


Contribute your Thoughts:

Huey
3 months ago
Haha, 'peritonitis them'? I think the BA needs to get that checked out. But seriously, the change request log is the way to go here.
upvoted 0 times
Yong
2 months ago
C) Gap analysis document
upvoted 0 times
...
Carin
2 months ago
B) Scope statement specification
upvoted 0 times
...
Marilynn
3 months ago
A) Change request log
upvoted 0 times
...
...
King
3 months ago
I'm not sure about the other options, but the change request log definitely sounds like the most appropriate tool for organizing all these requests from the stakeholders.
upvoted 0 times
Tess
2 months ago
B) Scope statement specification
upvoted 0 times
...
Emily
3 months ago
C) Gap analysis document
upvoted 0 times
...
Tess
3 months ago
A) Change request log
upvoted 0 times
...
Shawnta
3 months ago
B) Scope statement specification
upvoted 0 times
...
Adolph
3 months ago
A) Change request log
upvoted 0 times
...
...
Sang
3 months ago
The change request log seems like the obvious choice here. It's designed to keep track of all the changes requested during the project lifecycle.
upvoted 0 times
Cristina
3 months ago
B) Scope statement specification
upvoted 0 times
...
Ezekiel
3 months ago
A) Change request log
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