Universal Containers is adopting Scrum as an agile methodology and wants to choose a software...

The correct selection is A, B, C. Scrum tooling must support the ordered product backlog, sprint backlog, and assignment or ownership of actionable work. Those capabilities map directly to Scrum planning and execution, whereas email alerts or a generic Kanban view are supporting conveniences rather than the core Scrum controls being asked for. From a system-design perspective, the decision should minimize unnecessary coupling while preserving clear ownership, scalability, governance, and extensibility. Salesforce architecture is strongest when boundaries reflect real business and technical responsibilities instead of using organizational convenience as the primary design driver. The other options introduce tighter coupling, duplicate governance, or solve a different architectural concern and therefore do not satisfy the stated boundary and ownership requirements. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. Product backlog prioritization; B. Sprint backlog management; C. Work (for example, user stories or tasks) assignment). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: System Design — org strategy; modular architecture; integration topology; data ownership; enterprise governance; scalability.