Als-Con-201 Exam Dumps : Salesforce Certified Agentforce Life Sciences Consultant

The correct answer is A because distance-based sorting in the Next Best Customer mobile component requires geolocation data on the account’s relevant address. Salesforce Help for configuring Next Best Customer settings for the mobile app states that, to ensure accounts are accurately sorted by distance, geolocation data must be captured for the primary address or preferred address. Salesforce Help also explains that if no preferred address is available, distance is calculated using the account’s primary Contact Point Address.

The reps already confirmed that location services are enabled on the iPad, so the issue is not the mobile device’s ability to determine the user’s current location. The missing piece is the account-side location data. If the primary or preferred address does not contain valid latitude and longitude values, the component cannot accurately calculate the distance between the rep and the account. As a result, accounts may appear with a distance of 0 or behave incorrectly when sorted by distance.

Option B is incorrect because a manual refresh does not solve missing geolocation data. Refreshing the component may reload records, but it cannot calculate distance without valid address coordinates. Option C is also incorrect because territory alignment is important for determining which accounts are relevant to the rep, but the distance calculation itself depends on geolocation data. Therefore, the root cause is missing geolocation data on the account’s primary or preferred address.

=========

The correct answer is C because Life Sciences Calendar can display visits where the user is not the owner but is included as an attendee or visitor. Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit so that colleagues participating in the same HCP interaction can be recorded and the visit can be shared with them. Salesforce also describes Life Sciences Calendar as a place to visualize and prioritize key activities, including visits and other events, and Trailhead explains that reps can view colleagues’ visits in shared calendars to coordinate engagement.

In this scenario, the rep bulk deleted several planned visits from their calendar. The two remaining visits are likely not visits owned and managed by the rep. Instead, they are visits owned by another user where the rep is included as an attendee. Because the calendar is configured to show attendee visits, those records continue to appear even after the rep deletes their own planned visits.

Option A is incorrect because the issue is not tied to the selected account list. Option B is plausible for some filtered-calendar behavior, but the key clue is that only some visits remain visible after bulk deletion. The standard Life Sciences explanation is that attendee visits can remain visible because they belong to a colleague and are displayed for collaboration. Therefore, the visits remain because the rep is added as an attendee.

=========

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 .

=========