The correct answer is A because Remote Engagement email notifications depend on email templates configured for the relevant automated email invitation context/action. Salesforce Help for uploading and creating email templates in Life Sciences Cloud includes configuration fields for automated email invitation context and action. For a rescheduled or updated virtual visit, the email template must be configured so the automated email invitation action corresponds to the update event.
The scenario asks specifically about email notifications when virtual visits are rescheduled. A reschedule is an update to an existing visit invitation, not a new invitation and not a cancellation. Therefore, the consultant must ensure there is an email template whose Automated Email Invitation Action is set to Update. That template is then used by the Remote Engagement process when the visit details change and the HCP needs to receive the revised meeting information.
Option B is incorrect because configuring a handler around a visit status value such as "Rescheduled" is not the core template configuration required for the notification content and action. Option C may sound plausible because trigger handlers often support automation, but the question asks which configuration is required to send email notifications for rescheduled virtual visits. The action-specific email template is the necessary configuration. Therefore, the consultant should use an Email Template with Automated Email Invitation Action set to Update.
=========

Option B is correct because Presentation Page Product is the standard Life Sciences Cloud object that links presentation content to products. Salesforce's Life Sciences Cloud Developer Guide states that PresentationPageProduct represents the link between a presentation page and a product, and may also include a connection to product guidance or product messages. This directly matches the requirement to link Immunexis to specific presentation pages or slide content so analytics can identify which products were detailed during visits.
Salesforce's Intelligent Content data model also includes Presentation, Presentation Linked Page, Presentation Page, Presentation Page Product, Product2, Life Science Marketable Product, Provider Visit, and visit-detailing objects. This confirms that Presentation Page Product is part of the standard content and detailing analytics architecture for Life Sciences Customer Engagement.
Option A, Presentation Linked Page, is not the best answer because it links pages within presentation structure, but it does not specifically represent the product association. Option C, Product Media Link, is not the documented standard object for connecting Life Sciences presentation pages to products. Salesforce also provides a Presentation Page Product API resource for creating or updating product and guidance associations for a presentation page, reinforcing that this is the intended object.
Therefore, the consultant should use Presentation Page Product.

The correct answer is B because Salesforce Life Sciences calendar configuration represents General Event calendar entries using the standard Event object. Salesforce Help for configuring calendar events in Life Sciences Cloud lists calendar event types and shows General Event with the object/API reference Event. This means that the standard object used to store general, non-customer calendar activities is Event, even though the user-facing event type is called General Event.
In the scenario, the activities are internal items such as sales training or team lunch. They are not visits, HCP interactions, HCO engagements, or account-specific activities. They still need to appear on the rep's calendar for capacity planning. Therefore, they should be logged as general calendar events on the standard Event object.
Option A, General Event, is tempting because it describes the business meaning of the schedule item. However, the question asks which object should be used. Salesforce's configuration identifies the object as Event. Option C, Time Off Territory, is incorrect because that object is used to log and manage time away from assigned territories, such as PTO or territory unavailability. A team lunch or sales training is not necessarily time away from territory and is better represented as a general calendar event. Therefore, the consultant should use the Event object.
=========

The correct answer is A because Remote Engagement video traffic requires Twilio endpoints to be trusted by the Salesforce org. Salesforce Help for setting up Twilio for Remote Engagement states that participants can connect to video calls by adding Twilio WSS endpoints as Trusted URLs in the Salesforce org. This is specifically required for secure video-call connectivity, which directly matches the symptom in the question: the Twilio credentials and Experience Cloud site are configured, but the video media fails to load.
Twilio External Credentials handle authentication and connection details for the integration, and the Experience Cloud site provides the HCP-facing remote engagement experience. However, browser and Salesforce security controls still need to allow the required Twilio WebSocket Secure traffic. If those URLs are not trusted, the page can load while the actual audio/video media connection fails.
Option B is incorrect because assigning a field-sales permission set to the Site Guest User would be inappropriate and overly permissive. The issue is media connectivity, not guest-user access to sales functions. Option C is also incorrect because a trigger handler for remote-session invitations would relate to record automation or invitation behavior, not secure loading of Twilio video traffic. Therefore, the consultant must add Twilio's required endpoints to Trusted URLs.
=========

The correct answer is C because Provider Cards are designed to consolidate key account information from multiple objects and fields into a single user-friendly account view. Salesforce Help describes Provider Cards in Life Sciences Cloud as consolidating an account's information that is scattered across objects and fields, such as provider locations and related account information. Salesforce also describes the Provider Account Territory Info object as representing engagement data between an account and a user within an assigned territory, including account-territory context such as visit and engagement details.
The requirement is to display an indicator, not to filter accounts out of the card. Field reps need to see whether each account is a target or not. Adding an item group element to the Provider Card section and including the Targeted Account field from Provider Account Territory Info allows the template to display territory-specific targeting information. Visibility conditions can then show "Target" when the field value indicates the account is targeted and "Not Target" when it is not.
Option A is incorrect because filtering to show only targeted accounts would hide non-targeted accounts, but the requirement is to display both states. Option B is not the best answer because a repeater is used for repeating multiple related records, not for showing a single indicator from the account-territory information context. Therefore, the consultant should use an item group element with the Targeted Account field and visibility conditions.
=========