nerdexam
Salesforce

BA-201 · Question #287

The Business analyst (BA) at Universal Container wants to improve the case process in Salesforce after feedback customer abut resolution time. The BA tacks the user story, request details, and…

The correct answer is A. Multiple project team members can make and view revisions. Storing user stories in a shared repository (e.g., a version-controlled tool like Jira, Git, or Confluence) enables collaborative, concurrent access so any team member can view the current state of requirements and contribute updates. This creates a single source of truth with…

Collaborate

Question

The Business analyst (BA) at Universal Container wants to improve the case process in Salesforce after feedback customer abut resolution time. The BA tacks the user story, request details, and configuration changes in a repository. What is a benefit of tracking user stories in this way?

Options

  • AMultiple project team members can make and view revisions.
  • BIt links all changes to Salesforce metadata.
  • CThe development team can work parallel on the same requirement.

How the community answered

(46 responses)
  • A
    93% (43)
  • B
    4% (2)
  • C
    2% (1)

Explanation

Storing user stories in a shared repository (e.g., a version-controlled tool like Jira, Git, or Confluence) enables collaborative, concurrent access so any team member can view the current state of requirements and contribute updates. This creates a single source of truth with a traceable history of changes. Option B is incorrect because a general repository does not inherently link changes to Salesforce metadata - that requires a deployment/version control tool like Salesforce DX. Option C is incorrect because parallel work on the same requirement can cause conflicts; repositories help manage versions but do not eliminate that risk.

Topics

#User Story Tracking#Version Control#Case Management#Team Collaboration

Community Discussion

No community discussion yet for this question.

Full BA-201 Practice