Als-Con-201 Dumps with Practice Exam Questions Answers

Option A is correct because Remote Engagement with Twilio uses Salesforce named and external credentials, and users need access to the external credential principal to use those credentials. Salesforce Help for configuring Twilio credentials in Life Sciences Remote Engagement states that the Life Sciences Customer Engagement managed package includes the named and external credentials for Twilio. The same Salesforce Help result specifically references selecting External Credential Principal Access as part of the setup. This aligns directly with the error: the field sales rep cannot access the video service credentials, even though the Life Sciences Field Sales Representative permission set has been verified.

Option B is incorrect because the solution is not to manually provide the rep with a Twilio authentication token. That approach would be insecure and inconsistent with Salesforce’s named/external credential model. Credentials should be managed centrally through Salesforce configuration, not distributed directly to end users. Option C is also incorrect because “Twilio Users Public Group” is not the documented permission mechanism for accessing the video service credentials in Life Sciences Cloud Remote Engagement.

Salesforce’s broader named credential security documentation also explains that external credential principals can be mapped to permission sets and profiles so users can make callouts to external systems with the right access. That supports the need to grant External Credential Principal Access rather than changing the rep’s profile or sharing tokens manually.

=========

The correct answer is A because the subscription and channel must be connected before reps can capture consent for that channel. Salesforce’s Life Sciences Consent Management model includes Communication Subscription , Engagement Channel Type , and Communication Subscription Channel Type as standard entities for capturing and managing HCP consent and communication preferences. The Communication Subscription Channel Type object acts as the junction between a subscription topic, such as “Immunexis KOL Webinar Series,” and a channel, such as Email.

In the scenario, the subscription is visible, which confirms that the Communication Subscription record exists and is available in the mobile consent experience. However, Email is not selectable because the subscription has not been associated with the Email engagement channel. Creating the Communication Subscription Channel Type record resolves this gap by telling the system that this subscription can be consented to through the Email channel.

Option B is incorrect because Communication Subscription Consent records represent an individual HCP’s consent decision, such as opt-in or opt-out. They do not control whether a channel is available for a subscription. The channel must first be configured as valid for the subscription. After that, reps can capture the HCP’s opt-in preference during the visit. Therefore, the consultant should create the Communication Subscription Channel Type junction record.

=========

The correct answer is C because Provider Account Territory Information is the standard object used to store provider-level territory information, including calculated territory-specific visit metrics. Salesforce Help states that the Account Address batch job creates Provider Account Territory Information records and calculates values such as year-to-date visits , next visit, and last visit. This directly matches the requirement to track the HCP’s Year-to-Date Visit Count separately by territory assignment.

The key detail is that the HCP is assigned to multiple territories. A single account-level field would not be sufficient because the visit count must be different depending on the territory relationship. Provider Account Territory Information supports this by storing data at the intersection of provider account and territory, allowing the same HCP to have separate calculated values for each assigned territory.

Option A, Provider Account Territory Summary , sounds plausible because it includes “summary,” but the Salesforce-documented batch process specifically creates Provider Account Territory Information records for territory-specific metrics. Option B, User Territory Affiliation Information , is not correct because the requirement is about an HCP’s territory-specific visit count, not user-territory affiliation data. Therefore, the consultant should use Provider Account Territory Information .

=========

Digital Verification is the correct answer because Salesforce Life Sciences resources describe it as the native capability used to manage electronic signatures in Salesforce and support an organization’s 21 CFR Part 11 compliance requirements. Salesforce Help states that Electronic Signatures can be set up using the Digital Verifications feature, allowing signatures to be managed in Salesforce instead of relying on a third-party application. It also references creating a “signature trail,” which is the key concept in this question: the signature is not just a stored image, but part of a controlled verification process tied to the signed record and signer context.

Field Audit Trail is not the best answer because it tracks field history and retention for data changes; it does not provide the electronic-signature process required for HCP sample acknowledgments. Adobe Sign is also not the best answer because the question asks for the Salesforce Life Sciences feature that generates the audit trail inside the Life Sciences process. The Salesforce Developer Guide also identifies Digital Verification standard objects as part of the electronic-signature data model, reinforcing that Digital Verification is the Life Sciences capability designed for this use case.

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.

=========