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

Answer : B

Option B is correct because Salesforce Life Sciences Activity Plans use weighted goals to measure activities differently based on business importance. Salesforce Help for creating Activity Plans states that, to track weighted goals, administrators create Provider Activity Goal Measure records to define weights, select Weighted Goal in the Type field, and assign a value in Activity Weight Value. This directly supports the requirement to measure high-impact activities differently from standard activities.

Activity Plans are designed to transform provider interaction strategies into actionable goals and targets for field representatives. When certain activities with specific HCPs are more strategically important, weighted goals allow those activities to contribute differently to plan performance. This is more precise than simply counting every activity equally.

Option A is incorrect because ''High Impact Goal'' is not the documented Type value for this configuration. The Salesforce Help wording identifies ''Weighted Goal'' as the Type value used for weighted measurement. Option C is also not correct because the documented field is Activity Weight Value, not Activity Impact. Even if a percentage-based concept sounds plausible, the standard configuration step is to set the Provider Activity Goal Measure Type to Weighted Goal and enter the weight value. Therefore, the consultant should select Weighted Goal for the Type field.

=========

Answer : C

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.

=========

Answer : A

The correct answer is A because Salesforce Life Sciences Field Email allows field users to add colleagues as CC recipients. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails to healthcare professionals and healthcare organizations from their workflow, select an email template, and add colleagues as CC recipients.

This distinction matters for compliance. In Life Sciences engagement, HCPs and HCOs are the intended external recipients of approved email communications. The CC field is not intended as a free-form way to add additional HCPs. Instead, CC is used for internal collaboration or visibility, such as copying a colleague involved in the account, territory, or follow-up process. This helps keep HCP communications controlled, trackable, and aligned with approved email workflows.

Option B is incorrect because it suggests both HCPs and colleagues can be CC'd. Although emails are sent to HCPs or HCOs, Salesforce's documented CC behavior specifically references colleagues as CC recipients. Option C is also incorrect because HCPs are the primary external recipients, not the users who should be copied in the CC field. Therefore, when sending email from the Agentforce Life Sciences mobile app, field sales reps can CC colleagues.

=========

Answer : B

The correct answer is B because the business requirement says the system must block additional distributions once the sample limit is met. In Salesforce Life Sciences sample management, sample limits are used to control how many samples can be distributed to HCPs based on rules such as product, time period, and visit limits. Salesforce Help describes sample management features as supporting efficient and compliant handling and distribution of drug samples, while sample limits are part of the setup used to govern sample distribution.

The distinction between enforcement types is important. A Warning allows the rep to continue after being alerted. A Threshold is typically used to identify when a limit is nearing or reaching a defined point, but it does not satisfy the requirement to prevent excess sample distribution. An Error is the strictest enforcement behavior because it stops the transaction when the configured limit would be exceeded.

Here, Cumulus Pharma needs hard compliance enforcement: maximum 5 units per HCP per calendar year and maximum 2 units per visit. Since the system must prevent field sales reps from exceeding those values, the consultant should set the sample limit enforcement type to Error. This ensures the disbursement cannot proceed when the annual or per-visit limit has already been reached.

=========

Answer : B

Option B is correct because the Healthcare Provider object contains provider-specific Life Sciences attributes, including whether the provider is designated as a speaker for engagement. Salesforce's Life Sciences Cloud Developer Guide for the HealthcareProvider object states that the object and its fields are used by Account Management and Segmentation, and the search result for the same Salesforce object documentation identifies a field that indicates whether the provider is designated as a speaker for engagement, with a default value of false. This directly matches the question's requirement to identify whether a physician is flagged as a speaker.

Option A, Board Certification, is incorrect because board certification stores credential or certification information about a provider. It may help qualify the provider professionally, but it does not represent the commercial engagement flag that identifies whether the provider is a speaker. Option C, Person Account, is also not the best answer. In Life Sciences Cloud, physicians are commonly represented through Person Accounts, but the speaker designation is stored in the Healthcare Provider data model, not as a generic Person Account-only attribute.

Therefore, when the consultant needs to identify whether a physician is flagged as a speaker in Agentforce Life Sciences for Customer Engagement, the correct object to reference is Healthcare Provider.

=========

Answer : B

Option B is correct. In Agentforce Life Sciences for Customer Engagement, the visit engagement screen in the mobile app can be customized so field users have quick access to key visit information and related records while preparing for or conducting a visit. Salesforce Help identifies the Life Sciences Cloud mobile app setup area as the place where admins configure the visit engagement page, sidebar menu, visit information fields, visit record types, quick actions, and other customer engagement mobile settings. The sidebar menu is intended to provide focused, in-context access to the most relevant information, not to replicate every possible related list from the desktop experience.

The maximum number of custom object-related lists that can be added to the sidebar is five. This limit helps preserve mobile usability and keeps the visit engagement experience streamlined for field sales reps using an iPad or mobile device during HCP or HCO interactions.

Option A is incorrect because 10 related lists would create a heavier mobile interface than the supported sidebar configuration allows. Option C is also incorrect because the product allows more than two custom object-related lists. Therefore, when configuring the visit engagement sidebar, the consultant should plan for a maximum of five custom object-related lists and prioritize the most important related records for the field workflow.

=========

Answer : B

The correct answer is B because the requirement is about making a Samples option appear in the Life Sciences mobile app sidebar, not about adding a related list to a Salesforce desktop page. Salesforce Help for setting up the Life Sciences Cloud mobile app specifically includes tasks for configuring the Visit Engagement Page and the Sidebar Menu. Salesforce also states that mobile app configuration changes are handled through the Life Sciences Commercial app's Admin Console and mobile configuration areas, with metadata cache used to sync configuration to the mobile device.

The Samples tab is part of the mobile visit engagement experience. Enabling the relevant Samples sidebar setting in Mobile App Settings makes the Samples entry available in the sidebar so reps can record sample disbursements during a visit. This is the correct configuration approach because it controls the mobile navigation and visit sidebar behavior.

Option A is incorrect because adding the Product Disbursements related list affects a record page layout, but it does not create the mobile sidebar tab required by the field sales team. Option C is also incorrect because simply placing a Lightning web component on the Visit Lightning record page does not necessarily add a Samples entry to the Life Sciences mobile sidebar menu. The consultant should enable the Samples sidebar setting in Mobile App Settings.

=========