BA-201 · Question #295
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 s
The correct answer is C. Enable history in the shared spreadsheet.. Enabling version history (available in tools like Google Sheets or Microsoft Excel Online) creates an auditable trail of every change - who made it, when, and what was changed. This secures the integrity of UAT results by preventing undetected alterations and allowing the team to
Question
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?
Options
- AGive all stakeholder the ability to edit the shared spreadsheet.
- BAsk each tester to admit share spreadsheet.
- CEnable history in the shared spreadsheet.
How the community answered
(26 responses)- A12% (3)
- B8% (2)
- C81% (21)
Explanation
Enabling version history (available in tools like Google Sheets or Microsoft Excel Online) creates an auditable trail of every change - who made it, when, and what was changed. This secures the integrity of UAT results by preventing undetected alterations and allowing the team to revert to previous states if needed. Option A (giving all stakeholders edit access) increases exposure to accidental or unauthorized changes, reducing security. Option B likely refers to having each tester submit data via a form, which is partially useful but does not address the auditability of results already in the spreadsheet. History tracking directly addresses the 'documented securely' requirement.
Topics
Community Discussion
No community discussion yet for this question.