The Salesforce Certified Agentforce Life Sciences Consultant (Als-Con-201)

Option B is correct because Communication Subscription Channel Type is the junction record that links a Communication Subscription to an Engagement Channel Type. Salesforce’s Life Sciences Consent Management data model includes Communication Subscription, Communication Subscription Channel Type, Communication Subscription Consent, Data Use Purpose, Engagement Channel Type, and related consent objects. This confirms that subscription-channel availability is modeled through Communication Subscription Channel Type, not only through the subscription or channel records separately.

Salesforce’s Communication Subscription objects documentation states that Communication Subscription Channel Type specifies the engagement channel that can be used to contact the customer for a communication subscription. The Salesforce object reference also identifies fields on Communication Subscription Channel Type such as EngagementChannelTypeId, confirming that this object connects the subscription to the channel.

Option A is incorrect because there is no indication that a generic “Allow Email Channel” checkbox controls this relationship. Option C is also incorrect because Communication Subscription Consent stores an individual HCP’s consent preference after the channel-subscription combination exists. It does not make the Email channel selectable for the subscription. Therefore, the consultant must create a Communication Subscription Channel Type record linking “Immunexis KOL Webinar Series” to the Email Engagement Channel Type.

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.

=========

Option B is correct because Salesforce Life Sciences Cloud for Customer Engagement provides sample limit templates that help organizations enforce country-specific sampling rules. Salesforce Help states that Life Sciences Cloud includes a generic sample limit template and several country-specific templates by default. These templates are designed to support sample governance where regulations vary by country or region. In the scenario, Cumulus Pharma must comply with regional laws, such as Belgian requirements, while maintaining GxP standards for sample distribution. Using the default country-specific templates is the most appropriate standard configuration because it applies predefined sample-limit governance based on regional compliance expectations.

Option A is not the best answer because Territory Product Quantity Allocation is used to allocate product quantities by territory, but the requirement is about legal and GxP compliance by country. Allocation controls available quantities; it does not, by itself, represent the compliant sample-limit template framework. Option C is incorrect because manually adjusting Quantity On Hand on Product Item would change inventory balances directly and could create audit, traceability, and compliance risk. Product Item represents stock at a location, but manual quantity changes are not the correct way to enforce regional sampling laws.

Therefore, the consultant should use the default country-specific sample limit templates so sample distribution follows regional compliance rules while remaining aligned with Life Sciences Cloud’s controlled sample-management framework.

=========

The correct answer is B because Life Sciences Cloud supports configuring quick actions for the mobile app through the Admin Console. Salesforce Help for Medical Insights states that Medical Insights can be made available to users in the Life Sciences mobile app so users can view their own insights and insights shared with them. Salesforce Help also describes Quick and Custom Action Management as the way to simplify user experiences in Salesforce and the Life Sciences for Customer Engagement mobile app by leveraging quick actions and custom actions.

The requirement is not merely to expose the Medical Insights tab. The rep must be able to quickly report a medical insight while managing a visit on an iPad. Configuring the Create Medical Insights quick action in the Admin Console makes the action available in the mobile workflow where reps need it. This supports fast, in-context capture of field observations during a visit.

Option A is incorrect because creating a custom action and custom flow adds unnecessary complexity when the standard quick action can be configured declaratively. Option C is also not the best answer because editing the Visit page layout and adding a generic standard action may not make the action available correctly in the Life Sciences mobile app experience. The Admin Console is the correct configuration point for mobile quick actions. Therefore, the consultant should configure the Create Medical Insights quick action using the Admin Console.

The correct answer is B because the issue is the Activity Plan status transition. Salesforce describes Activity Plans as the mechanism to establish strategic plans and define activity goals for sales representatives over a specific period. The Life Sciences Activity Plans developer guidance also explains that activity plans define goals for employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

In this scenario, the plan exists and has a Start Date of today, but it is still in In Progress status. Reps cannot see the plan or their targets because the plan has not moved into the operational Active state. The specific job designed for this is Update Activity Plan Status , which evaluates the plan’s dates and moves eligible plans from In Progress to Active. Running that job makes the plan available for execution and dashboard reporting.

Option A is incorrect because Activity Plan Trigger Handler suggests trigger-based automation, not the named batch process that transitions plan status according to dates. Option C, Validate Activity Plans , is also incorrect because validation checks whether the plan setup is correct; it does not perform the status transition required by the question. The consultant should run Update Activity Plan Status in the Admin Console.

=========

The correct answer is C because Salesforce Life Sciences Sample Inventory Management is intended to provide a unified view of sample-related inventory activity. Salesforce documentation describes Sample Inventory Management as providing a unified view of transactions, shipments, inventory counts, and assigned batches, helping users stay on top of items requiring attention. This directly matches the requirement for reps to monitor batch assignments, received inventory, disbursements, transfers, and returns from one experience rather than navigating across multiple object tabs.

To make that experience available in the Agentforce Life Sciences mobile app, the consultant should expose the Sample Inventory Management dashboard through the user’s navigation configuration. Adding it to Navigation Items ensures the field sales rep profile can access the dashboard from the mobile app. This is better than building a custom report type because the standard dashboard is purpose-built for Life Sciences sample inventory workflows and already aligns with the sample inventory data model and operations.

Option A is not the best answer because a custom report chart would be less functional than the standard inventory dashboard and would not provide the operational interface reps need. Option B is also incomplete. The Inventory Operations Timeline is useful for viewing transaction history, and Salesforce describes it as an overview of transactions and product requests in chronological order, but it does not provide the full dashboard experience for assigned batches, inventory counts, shipments, and operational status.

The correct answer is B because the deadlines and review windows for activity-plan adjustments are configured on the Activity Plan record, specifically in the review-related configuration. Salesforce Help for creating Activity Plans references fields such as Reviewer Plan Adjustment Start Date and Reviewer Plan Adjustment End Date , which define the date range in which the manager can review adjustment requests.

The scenario describes a plan-level governance requirement: field sales reps must submit proposed visit targets by a specific deadline, and adjustments above allowed thresholds must be reviewed. This belongs to the Activity Plan configuration because the plan defines the cycle, timing, targets, review process, and adjustment behavior for the territory or provider planning period. Configuring the Review Details section ensures that the plan controls when reps can submit changes and when managers can review them.

Option A is incorrect because Global Calculation Settings for a Provider Activity Measure Type would relate to how measures or calculations are evaluated, not the submission and manager-review deadline for a specific Activity Plan. Option C is also incorrect because a Goal Definition represents a reusable planning objective, but it does not control the operational review dates and adjustment thresholds for a specific West Coast Activity Plan. Therefore, the consultant should configure the deadlines and adjustment limits on the Activity Plan record within the Review Details section .

=========

Option A is correct because Life Sciences Workflow Management is designed to control what users can do at different stages of a Life Sciences process, including Medical Inquiries. Salesforce Help for configuring Life Sciences workflow paths states that admins define stage operation conditions that must be met to grant users access to operations. Salesforce also provides specific setup guidance for workflow stages used to manage Medical Inquiries, including adding actions to stage operations and configuring stage operation conditions.

This fits the requirement exactly. The access rules change depending on the Medical Inquiry’s stage: Draft, Assigned, Responded, Signed, or Submitted. Salesforce’s Inquiry object documentation confirms these inquiry statuses are standard values used in the Medical Inquiries process.

Option B is incorrect because criteria-based sharing rules on Case would not dynamically manage stage-specific CRUD behavior for the Life Sciences Inquiry workflow. Also, the question is about Medical Inquiries, not generic Case sharing. Option C is also incorrect because validation rules and dynamic page layouts can restrict or hide fields and actions, but they do not provide the standard stage-based security model required here. Therefore, the consultant should configure Stage Operations and Stage Operation Conditions within Life Sciences Workflow Management.

=========

The correct answer is C because Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit. Salesforce Help for Add Internal Users as Visitors states that administrators can configure the visitors feature so field reps can record internal colleagues who participate in visits and automatically share visit data with them. This directly matches the requirement to include an MSL in the scheduled remote visit and track that person’s participation.

The MSL is not the primary HCP attendee and does not need a separate visit record. Instead, the MSL is an internal participant supporting the visit. Using the standard Add Visitors (Users) to a Visit action keeps the visit record intact while documenting the MSL as a participating internal user. It also supports better compliance, collaboration, and reporting because the MSL’s involvement is recorded against the actual visit.

Option A is incorrect because creating a separate Visit record would fragment the visit history and could cause duplicate or inconsistent reporting. Option B is incomplete because emailing the meeting link may help the MSL join the session, but it does not track the MSL’s participation in the Life Sciences Visit Management data model. The correct standard action is Add Visitors (Users) to a Visit .

=========