BA-201 · Question #230
Universal Containers is developing a new recurring app utilizing Lightning screen flows. The business analyst (BA) has started writing user stores in a repository. The project lead has edited user…
The correct answer is C. Review the version control history. Version control history is the definitive record of what changed, who changed it, and when. In a DevOps tool or source control system, every edit to a file or artifact is tracked as a commit or revision, giving the BA a full audit trail of modifications to user stories…
Question
Universal Containers is developing a new recurring app utilizing Lightning screen flows. The business analyst (BA) has started writing user stores in a repository. The project lead has edited user stories in the DevOps tool to make them more complete. What should the BA do to understand which user stories were modified?
Options
- AReview the approval history.
- BReview the change sets history
- CReview the version control history.
How the community answered
(36 responses)- A8% (3)
- B19% (7)
- C72% (26)
Explanation
Version control history is the definitive record of what changed, who changed it, and when. In a DevOps tool or source control system, every edit to a file or artifact is tracked as a commit or revision, giving the BA a full audit trail of modifications to user stories. Approval history (A) tracks workflow approvals, not content edits. Change set history (B) is a Salesforce deployment concept relating to metadata, not user story documentation. Version control is the correct tool for understanding edits to collaborative documents in a development workflow.
Topics
Community Discussion
No community discussion yet for this question.