Explanation
User acceptance testing is end-user testing performed in a sandbox or test environment to verify that a project or enhancement works as intended, and what was originally requested is actually being delivered. To ensure that the solution fulfills the needs of the sales team, the business analyst should choose subject matter experts as testers and prepare a sandbox with quality test data, test cases, and scripts that match real-world scenarios.
Subject matter experts are users who have extensive knowledge and experience with the business domain and processes. They can provide valuable feedback and insights on whether the solution meets their expectations and requirements. A sandbox is a copy of a production environment where users can test changes without affecting live data or users. Quality test data is data that is realistic, relevant, and representative of what users will encounter in production. Test cases are descriptions of specific scenarios or situations that users will perform with the solution. Test scripts are step-by-step instructions on how to execute each test case.
References: 1
https://trailhead.salesforce.com/en/content/learn/modules/user-acceptance-testing-video/learn-about-user-accept

Explanation
The best practice for conducting a live process mapping session is to have all stakeholders present and engaged. This ensures that the process is accurately captured and validated, and that any issues or gaps are identified and resolved. If some stakeholders are not available, the session may miss important information or perspectives, or create confusion or conflict later on. Therefore, the BA should cancel the workshop and reschedule it to a date when all stakeholders are available, or use other methods to elicit their input before or after the workshop. References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/plan-and-facilitate-

Explanation
A user story is a type of documentation that describes what functionality a system should provide from a user's perspective. It is written in simple language that anyone can understand and follows a standard format of "As a [user role], I want [functionality], so that [benefit]". A user story helps to capture the user's needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use user stories to document the functionality that a system should provide so it can be developed into a work item. References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories

Explanation
The area of user acceptance testing (UAT) that was overlooked was functionality on interconnected objects should be part of UAT. UAT is an end-user testing performed in a sandbox or test environment to verify that a project or enhancement works as intended, and what was originally requested is actually being delivered. UAT involves testing various scenarios on different users and levels of access to demonstrate that the solution works as expected in all situations. UAT should include functionality on interconnected objects because Salesforce objects are often related or linked to each other through lookup or master-detail relationships. For example, leads are converted into accounts, contacts, and opportunities; cases are associated with accounts or contacts; opportunities are closed as orders; etc. Functionality on interconnected objects should be part of UAT because it may affect how users perform their tasks or access their data across different objects. References:
https://trailhead.salesforce.com/content/learn/modules/user-acceptance-testing-video/create-test-scripts

Explanation
The action that the business analyst should take to quickly introduce new functionality to impress the customer is to demo standard features and elicit feedback from the customer. Demoing standard features means showing the customer how Sales Cloud can provide out-of-the-box functionality that meets their needs or expectations without requiring extensive customization or development. Eliciting feedback means asking the customer for their opinions or suggestions on how Sales Cloud can improve their sales process or performance. Demoing standard features and eliciting feedback helps to quickly introduce new functionality to impress the customer by demonstrating the value and benefits of Sales Cloud, as well as engaging and involving the customer in the solution design and delivery. References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/customer-di