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 PL
Mob_nav_barsMENU

Salesforce Exam Business Analyst Topic 7 Question 25 Discussion

Actual exam question for Salesforce's Business Analyst exam
Question #: 25
Topic #: 7
[All Business Analyst Questions]

During a requirements gathering session, two stakeholders discuss the names of the fields they want to see when adding leads to the system. Each stakeholder has a different point of view on field names.

What should the business analyst do to help Influence the team and accurately capture the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: C

This answer states that enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely after receiving verbal acceptance of all user stories by the product owner for developing a new Commerce Cloud implementation at CK. History is a feature that allows users to view, restore, or compare previous versions of a document or a file. Enabling history in the shared spreadsheet means that the BA turns on this feature in the spreadsheet where user stories are stored, such as Google Sheets, Microsoft Excel, etc. Enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely because it helps the BA to track and record who made what changes to user stories and when, and to prevent or recover any accidental or unauthorized changes to user stories. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills


by Elke at Aug 29, 2023, 02:19 AM

Limited Time Offer

25%

Off

Get Premium Business Analyst Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Hershel
3 days ago
I heard the stakeholders were arguing over whether to call it 'Lead Name' or 'Customer Name'. Apparently, one of them wanted to future-proof it for when they start selling to superheroes.
upvoted 0 times
...
Horace
7 days ago
A business analyst who can't wrangle a couple of stakeholders and get them to agree on field names? That's like a traffic cop who can't direct a three-car pileup. Better brush up on those negotiation skills!
upvoted 0 times
...
Dorothea
15 days ago
Allowing the development team to make the final decision? That's like letting the fox guard the henhouse! They'll probably just name everything 'field1', 'field2', and call it a day.
upvoted 0 times
Glendora
2 days ago
Stakeholder 2: I agree, we want to avoid confusion for the users.
upvoted 0 times
...
Sol
3 days ago
Stakeholder 1: We need to make sure the field names are clear and descriptive.
upvoted 0 times
...
...
Mozelle
20 days ago
Letting the executive sponsor decide feels like an easy way out. The business analyst should be facilitating the discussion, not passing the buck.
upvoted 0 times
...
Adolph
25 days ago
Finding a middle ground seems like the best approach. Both stakeholders' perspectives need to be considered to reach a consensus.
upvoted 0 times
...
Rolande
26 days ago
I believe allowing the development team to make the final decision could lead to a more efficient process.
upvoted 0 times
...
Naomi
27 days ago
I agree with Azalee, it's important to make sure both stakeholders are satisfied.
upvoted 0 times
...
Azalee
29 days ago
I think the business analyst should find a middle ground.
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