Explanation
The best way for a business analyst to handle disruptions to the project from urgent requests by the marketing director is to interpret them as guidelines to be used when determining priorities for the upcoming release.
This will help them balance between meeting stakeholder expectations and following scrum methodology principles. Focusing on agreed upon deliverables instead of new requests may ignore changing business needs or miss opportunities for improvement. Asking for an additional resource to implement new requests may increase complexity or cost without adding value or quality.
References:https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/

Explanation
A challenge is an element of the storytelling process for UX that describes a hurdle that makes it difficult for your heroes to succeed on their journeys. A monster is an element of the storytelling process for UX that describes a person or thing that causes problems for your heroes. A victory is an element of the storytelling process for UX that describes a successful outcome for your heroes. A helper is an element of the storytelling process for UX that describes a person or thing that assists your heroes along their journeys. References:
https://trailhead.salesforce.com/content/learn/modules/ux-design-fundamentals/understand-the-storytelling-proce

Explanation
The business analyst should identify dependent components to help with prioritization of user stories to add to an sprint. Dependent components are components that rely on or affect other components in an application or system. Identifying dependent components can help determine which user stories are more critical, complex, risky, or interrelated than others and prioritize them accordingly. Identifying dependent components can also help avoid conflicts, errors, or delays caused by missing or incompatible components when developing or deploying user stories. Verifying acceptance criteria is not an action that the business analyst should take to help with prioritization of user stories to add to an sprint. Verifying acceptance criteria is a process that checks whether a user story meets its conditions or requirements for being done or acceptable. Verifying acceptance criteria can help validate and test user stories but does not help prioritize them based on their importance or urgency. Deleting the definition of done is not an action that the business analyst should take to help with prioritization of user stories to add to an sprint. Deleting the definition of done is a process that removes the criteria or standards that indicate when a user story is completed and ready for deployment. Deleting the definition of done can reduce quality and consistency of user stories but does not help prioritize them based on their importance or urgency.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-pr

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-

This answer states that building tooltips and discoverable content in the new console layouts is how the BA should help the EMEA sales team learn the new features after completing the user acceptance testing phase of a major update to Sales Cloud. Tooltips are small pop-up windows that provide brief explanations or instructions for a feature or a functionality when a user hovers over or clicks on an element. Discoverable content is content that is hidden until a user interacts with a trigger, such as a button, a link, or an icon.
Building tooltips and discoverable content in the new console layouts can help the BA to provide contextual and on-demand guidance and information to the EMEA sales team, and help them learn the new features at their own pace and convenience. References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder