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

The correct answer is A from the available options, because the requirement is to control which user actions are exposed to different roles during the Medical Inquiry lifecycle. Salesforce Help for Medical Inquiries states that organizations can define relevant workflow actions for tasks users perform in the medical inquiry process, such as inquiry submission and assignment. Salesforce also describes a compliant role separation where field sales reps can submit medical inquiries, while Medical Science Liaisons can assign and respond to them.

The ideal Salesforce Life Sciences configuration pattern is to use Medical Inquiry workflow actions and workflow paths to control status transitions, actions, and permissions. However, among the provided answer choices, record types with role-specific page layouts is the only option that directly supports restricting the available buttons and actions by user role. This enables sales users to see only draft, sign, and submit actions, while MSL users see only assignment and response actions.

Option B is incorrect because a formula field can calculate or display logic, but it cannot enforce workflow actions or user interaction permissions by itself. Option C is also incorrect because a Flow action could add custom logic, but it is not the standard configuration approach for restricting Medical Inquiry lifecycle actions. Therefore, the best available answer is A .

=========

Option C is correct because the issue is isolated to the selected target account list, not to the overall availability of HCO accounts in the territory or application. Salesforce Life Sciences Cloud supports Lists and Filters so users can quickly identify a target group of accounts. These lists can be manually curated or filtered, meaning the accounts shown depend on the criteria or membership of the specific list being used. If only HCP accounts appear while HCO accounts are still aligned to the territory and visible elsewhere, the most likely cause is that the selected target account list itself includes only HCP accounts. Salesforce’s Life Sciences Cloud Developer Guide describes Lists and Filters as a way to quickly identify target account groups, and the LifeScienceAccountList object represents account list types such as filter, static list, and routine list.

Option A is not the best answer because Planner Administration record type settings would more broadly control planner behavior, not only one selected target account list. Option B is also not the best answer because Account Management record type configuration would affect how account types are configured or displayed more generally. The question states that HCO accounts are aligned and available elsewhere, which eliminates a broad record type or account management restriction. The problem occurs only when using the selected target account list during visit creation. Therefore, the consultant should review and correct the target account list criteria or membership so that both HCP and HCO accounts are included when needed.

=========

Option B is correct. In Salesforce Life Sciences Cloud Remote Engagement, the standard object used for the executed video engagement details is the remote-call/video-call record. Salesforce’s Life Sciences Developer Guide includes the VideoCall object for Remote Engagement and describes it as storing important information about the remote engagement, including its relationship to the associated provider visit. This aligns with the requirement to verify that the remote interaction occurred and review engagement metrics after the call concludes.

Provider Visit is related to the customer interaction and can represent the overall HCP visit context, but it is not the most precise object for the executed video-call details. The remote engagement session itself needs its own object because it can store video-specific information such as call status, timing, service details, and other remote-session metadata.

Option C, Video Log, is not the correct standard Life Sciences object name in the Salesforce documentation. “Video Log” sounds like a generic audit or logging object, but the documented Remote Engagement object is VideoCall. Since the answer options use “Remote Call” rather than “VideoCall,” Remote Call is the closest and intended answer for the standard remote engagement execution record. Therefore, the consultant should use the Remote Call/VideoCall record to review the executed Remote Engagement details.

=========

Option C is correct because the issue occurs when an HCP joins a Remote Engagement call through an Experience Cloud site link. In this flow, the external HCP typically accesses the site as the Site Guest User, so the guest user needs the correct permission set to use the remote engagement experience. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that admins must assign permission sets to the guest user of the site, including Access Remote Engagement for Digital Experience . This directly matches the error in the question: the HCP reaches the site, but receives an insufficient permissions error.

Option A is incorrect because the Life Sciences Commercial Admin permission set is intended for administrative users, not the Site Guest User serving an unauthenticated Remote Engagement portal. Assigning broad admin permissions to a guest user would also be inappropriate from a security and compliance perspective. Option B is also incorrect because the requirement is not to license the HCP as a Customer Community Plus user. The scenario describes an HCP joining from a link, and the Salesforce setup guidance specifically identifies a permission-set assignment for the Site Guest User.

Therefore, the consultant should assign the Access Remote Engagement for Digital Experience permission set to the Experience Cloud Site Guest User.

=========