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

Salesforce Exam Business Analyst Topic 3 Question 53 Discussion

Actual exam question for Salesforce's Business Analyst exam
Question #: 53
Topic #: 3
[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 Deonna at Oct 18, 2024, 06:26 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Vilma
2 months ago
Ah, the joys of shared spreadsheets. Option C is the only way to keep things organized and secure. Wouldn't want the product owner to accidentally delete the whole thing, am I right?
upvoted 0 times
Kasandra
23 days ago
Definitely, it's crucial for accountability and security. Option C is the best choice for documenting UAT results.
upvoted 0 times
...
Loreta
27 days ago
Agreed, enabling history in the shared spreadsheet will help track any changes made during UAT.
upvoted 0 times
...
Micaela
1 months ago
Option C is definitely the way to go. It's important to have a history of changes for security purposes.
upvoted 0 times
...
...
Lorriane
2 months ago
Giving everyone edit access? That's a recipe for disaster! Option B is just plain wrong too. C is the clear winner here.
upvoted 0 times
...
Slyvia
2 months ago
I agree with Emily. It would help track changes and ensure document security.
upvoted 0 times
...
Elliott
2 months ago
Option C is the way to go! History tracking is crucial for documenting UAT results securely.
upvoted 0 times
Estrella
1 months ago
Having a clear record of UAT results will help identify any issues and improve the overall quality of the product.
upvoted 0 times
...
Glenna
1 months ago
It's important to track changes made during UAT to ensure the integrity of the testing process.
upvoted 0 times
...
Elliot
1 months ago
I agree, enabling history in the shared spreadsheet will provide transparency and accountability.
upvoted 0 times
...
Lizette
2 months ago
Option C is the way to go! History tracking is crucial for documenting UAT results securely.
upvoted 0 times
...
...
Emily
2 months ago
I think enabling history in the shared spreadsheet would be a good idea.
upvoted 0 times
...

Save Cancel