New Year Sale ! 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 10 Question 33 Discussion

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

The product owner at Cloud Kicks wants to know which user stories fail user acceptance testing (UAT) and the potential impact on other successful use stories. Currently, user stories are stored in a shared spreadsheet.

What should a business analyst recommend to ensure UAT result are document security.

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 Lettie at Mar 04, 2024, 12:17 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Truman
6 months ago
Forget the spreadsheet, let's just store the user stories on the back of a napkin. That way, no one can access them, and we'll always know where they are... in the trash can.
upvoted 0 times
Tijuana
5 months ago
C) Enable history in the shared spreadsheet.
upvoted 0 times
...
Wendell
5 months ago
A) Give all stakeholder the ability to edit the shared spreadsheet.
upvoted 0 times
...
...
Julieta
6 months ago
Hmm, I don't know about you, but I'd rather not have to worry about accidentally deleting the entire spreadsheet during my lunch break. Let's go with the history option!
upvoted 0 times
Darrin
5 months ago
I think enabling history in the shared spreadsheet is the best option to ensure document security during UAT.
upvoted 0 times
...
Tamekia
5 months ago
Yeah, it would definitely make it easier to track who made what changes.
upvoted 0 times
...
Jutta
5 months ago
C) Enable history in the shared spreadsheet.
upvoted 0 times
...
Xochitl
6 months ago
I agree, having a history of changes in the spreadsheet would be really helpful.
upvoted 0 times
...
Ramonita
6 months ago
B) Ask each tester to admit share spreadsheet.
upvoted 0 times
...
Shayne
6 months ago
A) Give all stakeholder the ability to edit the shared spreadsheet.
upvoted 0 times
...
...
Benton
6 months ago
Enabling history in the spreadsheet? Now we're talking! That's a great way to keep track of changes and ensure traceability.
upvoted 0 times
Carmelina
5 months ago
I agree, it's important for documenting UAT results securely.
upvoted 0 times
...
Tomas
6 months ago
Yes, it will help us track changes and ensure traceability.
upvoted 0 times
...
Odelia
6 months ago
Enabling history in the spreadsheet is a good idea.
upvoted 0 times
...
Willard
6 months ago
Yes, it will help track changes and ensure accountability.
upvoted 0 times
...
Callie
6 months ago
Enabling history in the spreadsheet is a good idea.
upvoted 0 times
...
...
Kathrine
6 months ago
I think asking each tester to admit and share their testing results individually would be more organized.
upvoted 0 times
...
Ora
7 months ago
Ask each tester to add the spreadsheet? That's way too much manual work. We need a more efficient solution.
upvoted 0 times
Vannessa
6 months ago
A) Give all stakeholders the ability to edit the shared spreadsheet.
upvoted 0 times
...
Vannessa
6 months ago
C) Enable history in the shared spreadsheet.
upvoted 0 times
...
...
Lilli
7 months ago
That's true, it could lead to conflicts and confusion.
upvoted 0 times
...
Barney
7 months ago
But wouldn't giving all stakeholders the ability to edit the spreadsheet create chaos?
upvoted 0 times
...
Dortha
7 months ago
Giving all stakeholders edit access? That's like handing over the keys to the kingdom. Not a good idea at all.
upvoted 0 times
Miriam
6 months ago
B) Ask each tester to admit share spreadsheet.
upvoted 0 times
...
Ryan
7 months ago
C) Enable history in the shared spreadsheet.
upvoted 0 times
...
Cheryl
7 months ago
A) Give all stakeholders the ability to edit the shared spreadsheet.
upvoted 0 times
...
...
Stephen
7 months ago
I agree with Lilli, it would allow us to track changes and who made them.
upvoted 0 times
...
Lilli
7 months ago
I think enabling history in the shared spreadsheet would be a good idea.
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