Salesforce Als-Con-201 Practice Exam Questions & Answers

Option A is correct because the requirement is specifically to allow field sales reps to add colleagues as CC recipients when sending emails from the Life Sciences Cloud mobile app. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails from the Life Sciences Cloud mobile app from areas such as the home page, visit and account records, the content library, and the presentation player. The same Salesforce Help result also states that users can add colleagues as CC recipients, depending on the Salesforce admin's configuration.

That wording directly matches the option ''Add Colleagues as CC.'' The purpose of the setting is not simply to expose a generic CC field, but to enable the Life Sciences mobile email experience where reps can copy internal colleagues on compliant business communications.

Option B, ''Add CC Recipients,'' is too generic and does not match the Life Sciences-specific setting name in the question. It describes the general email behavior but not the precise admin setting. Option C, ''Enable CC Field Representative,'' is also not correct because it implies a setting focused on copying the field representative, rather than allowing the field representative to add colleagues as CC recipients.

Therefore, to let field sales reps CC colleagues from the Agentforce Life Sciences mobile app, the consultant should enable Add Colleagues as CC.

Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.

The key word in the question is ''collaborate.'' Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because ''availability'' typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user's territories, and the named handler that most directly supports that requirement is the sharing handler.

Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.

Option A is correct because Activity Plan Territory is the standard object that links an Activity Plan to territory details. Salesforce's Life Sciences Cloud Developer Guide describes ActivityPlanTerritory as representing the territory details associated with an activity plan. This exactly matches the requirement: the Immunexis Launch Activity Plan exists and contains the correct goals and measures, but it must be associated with the San Francisco North territory node so the relevant sales team can see and use it.

Salesforce's Activity Plans data model also lists Activity Plan Territory as one of the included entities, alongside Activity Plan, Territory, Provider Activity Goal, Provider Activity Goal Measure, Product, and Time Period. That confirms Activity Plan Territory is part of the standard Life Sciences Activity Plans architecture for defining, reviewing, and tracking employee activity plans, goals, and progress across territories.

Option B is not correct because ''Territory Activity Plan'' is not the standard object name used in the Life Sciences Cloud Activity Plans data model. Option C is also incorrect because Territory Plan Assignment relates more naturally to territory-planning assignment concepts, not linking an Activity Plan to a sales territory. Therefore, the consultant should populate Activity Plan Territory to associate the Activity Plan with the San Francisco North territory.

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 C is correct because the requirement is to display a conditional indicator on the Provider Card based on the Targeted Account field. Salesforce Help states that Provider Cards consolidate account information from scattered objects and fields into a single interface. Salesforce also documents that, in the Provider Card template, admins can use data from Provider Account Territory Information, including the Targeted Account field, to show whether an account is a target account.

The correct pattern is to add an item group element to a section, include the Targeted Account field from the Provider Account Territory Info source object, and configure visibility conditions so the card shows the appropriate label. When the field value indicates that the account is targeted, the card can show ''Target.'' When it is not targeted, a separate condition can show ''Not Target.''

Option A is not correct because applying record-level filters to show only targeted accounts would hide non-targeted accounts rather than displaying both ''Target'' and ''Not Target'' states. Option B is not the best answer because a repeater element is used for repeating sets of records; this requirement is a single account-level indicator. Therefore, item group elements with visibility conditions are the right configuration for the Provider Card indicator.