Online Als-Con-201 Questions Video

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.

=========

Option B is correct because the two requirements depend on two different territory-related maintenance jobs, and the territory information should be refreshed before historical visit sharing is recalculated. Salesforce’s Life Sciences Cloud documentation describes Provider Account Territory Information as engagement data between an account and a user within an assigned territory, including visit-related information such as next provider visit date and preferred address. After a major territory realignment, this data must be updated first so that territory-based account and visit metrics reflect the new alignments.

After that, the Visit Share Management job should be run. Salesforce Help states that, to share historical account visit records after territory realignments, admins run the Visit Share Management job so field users continue to have access to relevant historical visit data. That exactly matches the second requirement in the question: newly assigned reps must gain access to historical visit data for accounts that now belong to their territories.

Option A is incorrect because the question asks for the correct sequence, and Salesforce documentation does not indicate that Visit Share Management should be relied on to automatically execute the territory information update job. Option C is incorrect because running visit sharing before updating provider-account-territory information can share records based on stale territory data. Therefore, the correct operational sequence is: update Provider Account Territory Information first, then run Visit Share Management.

=========

Option A is correct because Account Summarization uses cross-object graphs to determine which related objects and relationships are included in generated summaries. Salesforce Life Sciences Account Summarization setup resources reference creating a cross-object graph for Account Summarization and assigning cross-object graphs to an org or profile. This supports persona-specific summary behavior because a graph can be configured with the additional custom objects and then assigned specifically to the KAM profile.

The requirement says the new information must be used only for the new KAM persona. That means the consultant should avoid changing the default or shared provider summary mapping used by other personas. By creating a separate cross-object graph from the template, adding the two custom insight and market-intelligence objects, and assigning that graph only to the KAM profile, the consultant isolates the new summary structure to the intended users.

Option B is not the best answer because globally updating Provider Summary Objects mapping could affect more than the KAM persona if the mapping is shared. Option C is also not the best answer because the key Account Summarization configuration pattern documented by Salesforce is graph creation and graph assignment to an org or profile. Therefore, the correct configuration is to create a new cross-object graph and assign it to the KAM profile.

=========

Option A, HCP Remote Platform Conference, is correct. In Salesforce Life Sciences Cloud Remote Engagement, the consultant creates an Experience Cloud site so Healthcare Providers can join remote visits. Salesforce Help specifically states that the HCP Remote Platform Conference component is available under Custom Components and can also be found through the search bar when building the Experience Cloud page. This is the component that is placed on the page to support the remote engagement conference experience.

The question also mentions video playback and Terms & Conditions logic. Salesforce Life Sciences Cloud Remote Engagement setup includes configuration for video call settings and video call Terms and Conditions, and the Experience Cloud site component is the user-facing component that brings the HCP remote conference experience onto the page. Salesforce Help also references Remote Engagement setup tasks such as configuring video call settings with Twilio and configuring video call Terms and Conditions, showing that Twilio is part of the underlying video-call configuration rather than the Experience Cloud page component itself.

Option B, Twilio Connector, is incorrect because Twilio configuration supports the video service settings, but it is not the component dragged onto the Experience Cloud page canvas. Option C, Remote Video Player, is not the standard component name identified in the Salesforce setup documentation. Therefore, the out-of-the-box component the consultant should select is HCP Remote Platform Conference.