Als-Con-201 VCE Exam Download

Option B is correct because the Healthcare Provider object contains provider-specific Life Sciences attributes, including whether the provider is designated as a speaker for engagement. Salesforce’s Life Sciences Cloud Developer Guide for the HealthcareProvider object states that the object and its fields are used by Account Management and Segmentation, and the search result for the same Salesforce object documentation identifies a field that indicates whether the provider is designated as a speaker for engagement, with a default value of false. This directly matches the question’s requirement to identify whether a physician is flagged as a speaker.

Option A, Board Certification, is incorrect because board certification stores credential or certification information about a provider. It may help qualify the provider professionally, but it does not represent the commercial engagement flag that identifies whether the provider is a speaker. Option C, Person Account, is also not the best answer. In Life Sciences Cloud, physicians are commonly represented through Person Accounts, but the speaker designation is stored in the Healthcare Provider data model, not as a generic Person Account-only attribute.

Therefore, when the consultant needs to identify whether a physician is flagged as a speaker in Agentforce Life Sciences for Customer Engagement, the correct object to reference is Healthcare Provider .

=========

Option A is correct because Account Summarization uses a cross-object graph to define which objects and relationships are included in the generated summary. Salesforce Help states that administrators can create cross-object graphs from a predefined Account Summarization template to provide a complete view of an account and its related objects. This directly matches the requirement to include Account data and related Healthcare Provider and Contact Point Address information in the summary.

The phrase “historical data” is also important. Salesforce Account Summarization setup includes configuring history tracking for the fields included in the template, so Agentforce can summarize recent changes from the selected objects and fields. The cross-object graph defines the relationship structure, while field history tracking provides the change history used in the summary.

Option B, Actionable Relationship Center, is not the best answer. Actionable Relationship Center is used to visualize related records and relationships, but the Account Summary configuration specifically relies on cross-object graphs. Option C, Affiliation Alignment Rules, is unrelated because those rules support territory alignment for affiliated accounts, not Account Summary object relationships. Therefore, the consultant should use a Cross-Object Field History Graph to define the Account, Healthcare Provider, Contact Point Address, and related-object structure used by Agentforce Account Summary.

=========

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 B because off-label control in the visit experience is tied to product detailing behavior. In life sciences commercial engagement, product detailing governs what products, messages, indications, and approved content can be discussed or shown during a visit. Salesforce Trailhead describes Life Sciences Cloud content visibility as being filtered by territory, product assignment, and account restrictions to prevent off-label or noncompliant sharing. This aligns most closely with Visit Settings > Product Detailing Settings , because that is the visit configuration area where product discussion and detailing behavior is controlled.

The question asks where the consultant should configure whether reps are allowed to discuss products for unapproved indications. That is not a generic compliance switch; it is a visit-detailing control connected to product and indication behavior in the field engagement workflow. Product Detailing Settings are therefore the correct place to enforce whether off-label discussion is permitted, warned, or restricted according to company policy.

Option A is incorrect because “Compliance Settings > Off-Label Validation” is not the standard configuration path presented in the available options for the Life Sciences visit experience. Option C is also incorrect because Restricted Products would control whether products are available or restricted, but the scenario is specifically about discussion of unapproved indications during product detailing. Therefore, the consultant should use Visit Settings > Product Detailing Settings .

=========