Salesforce Als-Con-201 Exam Questions

The correct answer is C because Provider Cards are designed to consolidate key account information from multiple objects and fields into a single user-friendly account view. Salesforce Help describes Provider Cards in Life Sciences Cloud as consolidating an account's information that is scattered across objects and fields, such as provider locations and related account information. Salesforce also describes the Provider Account Territory Info object as representing engagement data between an account and a user within an assigned territory, including account-territory context such as visit and engagement details.

The requirement is to display an indicator, not to filter accounts out of the card. Field reps need to see whether each account is a target or not. Adding an item group element to the Provider Card section and including the Targeted Account field from Provider Account Territory Info allows the template to display territory-specific targeting information. Visibility conditions can then show ''Target'' when the field value indicates the account is targeted and ''Not Target'' when it is not.

Option A is incorrect because filtering to show only targeted accounts would hide non-targeted accounts, but the requirement is to display both states. Option B is not the best answer because a repeater is used for repeating multiple related records, not for showing a single indicator from the account-territory information context. Therefore, the consultant should use an item group element with the Targeted Account field and visibility conditions.

=========

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.

=========

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.

The correct answer is A because Salesforce's Remote Engagement setup guidance for Life Sciences Cloud specifically identifies the Experience Cloud site as the place where language support is configured for remote engagement experiences. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that, for language support, the administrator should select Components and drag the Language Selector component to the page. This directly supports the requirement for HCPs to review and accept terms and conditions in multiple languages when joining remote visits.

Remote Engagement involves an HCP-facing experience, not only a sales-rep mobile action. The terms and conditions are presented through the Experience Cloud site used for the remote session, so the language-selection capability must be available there. Adding the Language Selector lets the HCP choose the appropriate language in the site experience before reviewing the terms.

Option B is incorrect because configuring the Start Remote Session quick action may help reps launch or manage remote sessions, but it does not provide the HCP-facing multilingual site control required for terms and conditions. Option C is also incorrect because a survey can collect feedback or preferences, but it is not the Salesforce-recommended way to localize the terms-and-conditions experience. The correct configuration is to add the Language Selector component to the Experience Cloud site.

=========

Option C is correct because Salesforce Life Sciences Cloud supports manual territory alignment for affiliated accounts. Salesforce Help for Territory Alignment for Affiliated Accounts states that a user's territory determines which accounts they can view and manage, and that users can manually align an affiliated account to their territory. The broader Affiliations documentation also explains that affiliation alignment rules can automatically align affiliated accounts, but the scenario specifically asks for manual alignment by field users when needed.

The correct Admin Console setting is therefore the one that enables users to align affiliated accounts to the user's territory. This setting allows reps working with complex HCO/HCP affiliation networks to bring relevant affiliated accounts into their current territory alignment when the relationship is valid for their business process.

Option A is not the best answer because the requirement is not to align accounts outside the user's territory. It is to let users align affiliated accounts to their own current territory. Option B is also incorrect because searching for accounts outside the user's territory only affects discoverability. It does not grant the ability to perform the actual affiliated-account alignment. Therefore, the consultant should enable ''Enable users to align affiliated accounts to the user's territory'' in Account Management > Affiliation.