Explanation
When a business analyst finds it difficult to get a response from a subject matter expert (SME), they should escalate the concern to the SMEs' manager. This is because the SMEs' manager can help to prioritize the project, provide feedback, and ensure accountability. The business analyst should also document the communication attempts and issues, and keep the project sponsor and other stakeholders informed of the status and risks.
References:https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/

Explanation
This answer states that using who, what, and why is what each user story should include for optimizing a very manual process in its Salesforce org. Who refers to the persona, which is a fictional representation of a typical user or stakeholder who will use or benefit from a feature or a functionality. What refers to the goal, which is what the user or stakeholder wants to accomplish with the feature or functionality. Why refers to the value, which is why the user or stakeholder wants to accomplish the goal, and how they will measure success. Using who, what, and why can help the BA to write effective user stories that capture and prioritize the requirements, and align them with the stakeholder value and expectations.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use

Explanation
One of the BA's strongest arguments for using configuration over code is that configuration provides faster speed to market. Speed to market is the time it takes to deliver a product or service from conception to launch.
Speed to market is important for gaining competitive advantage,meeting customer demand, and maximizing revenue potential. Configuration provides faster speed to market than code because it allows for creating and modifying functionality in Salesforce without writing code or deploying changes. Configuration can be done by using point-and-click tools such as App Builder, Process Builder, Flow Builder, Lightning Web Components Builder, etc., which are easy to use and require less technical skills than coding. Configuration also reduces the risk of errors or bugs that may occur with code and require more testing or debugging time.
References:https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional-requirements/

Explanation
The issue that should concern the business analyst most is that the system admins note a fair amount of technical debt without having the time or expertise to address it. Technical debt is the accumulated cost or consequence of suboptimal design, development, or maintenance decisions on a software system. Technical debt can negatively affect the performance, security, usability, and maintainability of a software system, as well as increase the complexity and risk of future changes or enhancements. Technical debt can also reduce user satisfaction and adoption, as well as business value and return on investment. Therefore, the business analyst should be concerned about the technical debt in the Sales Cloud implementation and work with the system admins and other stakeholders to identify, prioritize, and resolve it. References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/project-initi

Explanation
The tool that Universal Containers should use to prevent teams from overwriting each other's changes in the future is a version control system. A version control system is a tool that tracks and manages changes to code or configuration in a software project or enhancement. A version control system helps to prevent teams from overwriting each other's changes by allowing them to create and work on separate branches or copies of the code or configuration, merge their changes with the main branch or copy when they are ready, and resolve any conflicts or errors that may occur during the merge. A version control system also helps to maintain a history of changes, backup and restore previous versions, and collaborate and communicate with other team members.
References:https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/work-with-the-git-hub-