BA-201 · Question #179
The business analyst (BA) at Northern Trail Outfitters is writing user stories about a Case creation feature within Service Cloud for an upcoming sprint. This feature overlaps with another feature…
The correct answer is C. Version control. Version control (Choice C) is the appropriate tool for managing metadata dependencies across parallel feature development teams. Systems like Git allow teams to track changes to Salesforce metadata (e.g., page layouts, flows, custom fields), merge branches carefully, and…
Question
The business analyst (BA) at Northern Trail Outfitters is writing user stories about a Case creation feature within Service Cloud for an upcoming sprint. This feature overlaps with another feature that is being developed in the current sprint. The BA is working with the technical team to identify metadata dependencies across features to prevent overwriting before the release. What should the BA use?
Options
- ASetup Audit Trail
- BChange Sets
- CVersion control
How the community answered
(39 responses)- A21% (8)
- B10% (4)
- C69% (27)
Explanation
Version control (Choice C) is the appropriate tool for managing metadata dependencies across parallel feature development teams. Systems like Git allow teams to track changes to Salesforce metadata (e.g., page layouts, flows, custom fields), merge branches carefully, and resolve conflicts before release - preventing one team's changes from overwriting another's. Choice A (Setup Audit Trail) tracks historical changes already made in an org - it is a diagnostic tool, not a preventive one for parallel development. Choice B (Change Sets) is a deployment mechanism for moving metadata between orgs, but it does not provide conflict management or collaborative dependency tracking across parallel sprints. Version control is the industry-standard solution for this scenario.
Topics
Community Discussion
No community discussion yet for this question.