New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Business Analyst (BA-201) Exam - Topic 5 Question 31 Discussion

Actual exam question for Salesforce's Salesforce Certified Business Analyst (BA-201) exam
Question #: 31
Topic #: 5
[All Salesforce Certified Business Analyst (BA-201) 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:

0/2000 characters
Edwin
3 months ago
Change request log makes the most sense for tracking.
upvoted 0 times
...
Lonny
3 months ago
Surprised no one mentioned prioritizing the requests!
upvoted 0 times
...
Veronica
4 months ago
Gap analysis? Really? That seems off.
upvoted 0 times
...
Sabine
4 months ago
I think a scope statement would be more useful here.
upvoted 0 times
...
Alva
4 months ago
A change request log is definitely the way to go!
upvoted 0 times
...
Carmen
4 months ago
Gap analysis document? I don't think that fits here. It’s more about identifying differences, not organizing requests.
upvoted 0 times
...
Grover
4 months ago
I practiced a similar question where we had to prioritize requests. A change request log definitely sounds like the right tool for that.
upvoted 0 times
...
Maybelle
4 months ago
I'm not entirely sure, but I think a scope statement specification might help too? It could clarify what changes are actually needed.
upvoted 0 times
...
Bettye
5 months ago
I remember we discussed the importance of a change request log in class. It seems like the best way to track all those requests.
upvoted 0 times
...
Myra
5 months ago
This is a tricky one. The BA is dealing with a lot of requests, so they need something that can help them track and prioritize everything. I'm not sure if the scope statement or gap analysis would be the best fit here. I'd probably go with the change request log as the most appropriate tool.
upvoted 0 times
...
Roxane
5 months ago
I think the key here is that the BA needs to organize the requests. A gap analysis document (option C) could work, but that's more for identifying gaps between requirements, not managing change requests. I'm leaning towards the change request log.
upvoted 0 times
...
Janey
5 months ago
Hmm, I'm a bit unsure here. The question mentions the BA is overwhelmed, so maybe a more comprehensive tool like a scope statement specification (option B) would be better to capture all the details.
upvoted 0 times
...
Pa
5 months ago
This seems like a straightforward question. The BA needs a way to organize all the change requests, so I'd go with option A - a change request log.
upvoted 0 times
...
Hana
5 months ago
Hmm, this looks like a tricky one. I'll need to think carefully about the potential issues with manually creating a static VXLAN tunnel.
upvoted 0 times
...
Cherry
5 months ago
Hmm, I'm a little unsure about this one. The question is asking what the Scrum Master should do, but the options don't seem to directly address that. I'll need to think through the Scrum roles and responsibilities to figure out the best approach.
upvoted 0 times
...
Glenna
5 months ago
I think this might relate to Service Autonomy since I remember reading about how services should operate independently.
upvoted 0 times
...
Huey
2 years 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 years ago
C) Gap analysis document
upvoted 0 times
...
Carin
2 years ago
B) Scope statement specification
upvoted 0 times
...
Marilynn
2 years ago
A) Change request log
upvoted 0 times
...
...
King
2 years 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 years ago
B) Scope statement specification
upvoted 0 times
...
Emily
2 years ago
C) Gap analysis document
upvoted 0 times
...
Tess
2 years ago
A) Change request log
upvoted 0 times
...
Shawnta
2 years ago
B) Scope statement specification
upvoted 0 times
...
Adolph
2 years ago
A) Change request log
upvoted 0 times
...
...
Sang
2 years 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
2 years ago
B) Scope statement specification
upvoted 0 times
...
Ezekiel
2 years ago
A) Change request log
upvoted 0 times
...
...

Save Cancel