Get Salesforce Als-Con-201 Exam Practice Questions - Real and Updated

Answer : B

Option B is correct because Salesforce Life Sciences Cloud requires a specific API-name prefix for custom Lightning web components that should render as inline components in the Life Sciences mobile app. Salesforce Help for creating and adding an LWC as an inline component on a record page states that admins must create a custom mobile-ready LWC and add lscMobileInline_ as the prefix for the component's API name. This exact prefix identifies the component as compatible with the Life Sciences mobile inline rendering framework.

This directly matches the issue in the scenario. The component exists and was added to the Account record page, but it does not render correctly as an inline component in the mobile app. The missing configuration is not the page placement itself, but the required naming convention that allows the Life Sciences mobile app to recognize and render the LWC inline.

Option A, lsc_mobile_, is incorrect because it is not the documented prefix for inline mobile LWCs. Option C, mobileInline_, is also incorrect because it omits the Life Sciences-specific lsc prefix and does not match the Salesforce Help requirement. Therefore, the consultant should rename or recreate the LWC API name using the lscMobileInline_ prefix so it functions correctly as an inline component in the Agentforce Life Sciences mobile app.

=========

Answer : A

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.

=========

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 : A

Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep's targets.

Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.

Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.

=========

Answer : C

The correct answer is C because Life Sciences Calendar can display visits where the user is not the owner but is included as an attendee or visitor. Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit so that colleagues participating in the same HCP interaction can be recorded and the visit can be shared with them. Salesforce also describes Life Sciences Calendar as a place to visualize and prioritize key activities, including visits and other events, and Trailhead explains that reps can view colleagues' visits in shared calendars to coordinate engagement.

In this scenario, the rep bulk deleted several planned visits from their calendar. The two remaining visits are likely not visits owned and managed by the rep. Instead, they are visits owned by another user where the rep is included as an attendee. Because the calendar is configured to show attendee visits, those records continue to appear even after the rep deletes their own planned visits.

Option A is incorrect because the issue is not tied to the selected account list. Option B is plausible for some filtered-calendar behavior, but the key clue is that only some visits remain visible after bulk deletion. The standard Life Sciences explanation is that attendee visits can remain visible because they belong to a colleague and are displayed for collaboration. Therefore, the visits remain because the rep is added as an attendee.

=========