Salesforce Certified Agentforce Life Sciences Consultant Als-Con-201 Exam Questions

Answer : C

Option C is correct because Life Sciences Cloud separates the overall visit activity from provider-specific visit details. In the Life Sciences Cloud data model, the Visit object tracks information related to a field representative's visit to a healthcare provider and is used for Customer Engagement. Salesforce's ProviderVisit object represents the details of a field user's visit to a healthcare provider. The Customer Engagement data model also explains that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples.

For a group visit such as a ''Lunch and Learn'' with three HCPs, the overall event is represented by the parent Visit record. Each attendee requires their own provider-specific visit detail record because each HCP may have different product discussions, messages, samples, signatures, or follow-up activities. Therefore, the system creates one parent Visit and separate child Provider Visit records for each HCP attendee.

Option A is incorrect because a multi-select lookup field is not the correct Life Sciences Cloud visit data model pattern. Option B is also not correct because it implies individual parent-level Visit records for every attendee, which would duplicate the overall group interaction. The correct structure is one parent Visit for the group interaction and three child Provider Visit records, one for each Healthcare Provider attendee.

Answer : A

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.

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

Option C is correct because Subject Management is the standard approach for organizing Medical Insights by topic. Salesforce Life Sciences Medical Insights allows users to capture, view, and work with insights from HCP engagements. Salesforce Help describes Medical Insights as a feature that can be made available in the Life Sciences mobile app so users can view their own insights and insights captured by users in their territories. Salesforce also documents Medical Insight object setup through page layouts and field sets, which supports structured capture and display of insight details.

The question asks for a way to organize insights for easy searching and filtering by topics. Subject Management fits that need because subjects provide a controlled way to classify insights into topics or categories. This helps reps and analytics teams search, filter, and review insights consistently rather than relying only on free-text notes.

Option A, Life Science Insight List Filter, is not the best answer because filtering is a user experience mechanism, not the underlying topic-management configuration. Option B, Actionable List Filter Criteria, is also not correct because actionable lists and filter criteria are broader account or list-management concepts; they do not define Medical Insight topics. Therefore, to organize Medical Insights by topic for better searching and filtering, the consultant should recommend Subject Management.

=========

Answer : B

Option B is correct because the requirement is specifically about making Consent Management data available in the Life Sciences mobile app. Salesforce Help for Consent Management states that admins must create object metadata cache configuration for supported Consent Management objects and generate a metadata cache so sales reps can view and update consent data. Salesforce also has a dedicated setup topic for creating Object Metadata Cache Configuration, which is accessed from the Life Sciences Commercial app Admin Console under Mobile.

This is important because the Life Sciences mobile app depends on generated metadata cache so that configured objects, fields, and layouts are available to field users on iPad and mobile workflows. Without the metadata cache for the Consent Management objects, reps may not be able to access or update consent preferences during visits, even if the consent model itself is configured correctly.

Option A is not the best answer because Subscription Filtering Fields help control filtering behavior for consent subscriptions, but they do not make the consent objects available in the mobile app. Option C is also incorrect because configuring a desktop Lightning record page does not satisfy the Life Sciences mobile app metadata requirement. Therefore, the consultant should create the object metadata cache configuration for Consent Management objects and generate the metadata cache.

=========

Answer : C

The correct answer is C because aligned account lists in Agentforce Life Sciences for Customer Engagement are configured through account list settings, where the consultant defines how the list appears to users in the mobile experience. Salesforce describes account management features in Life Sciences Cloud as enabling users to organize, prioritize, and focus on accounts through lists and filters in the Customer Engagement app. The account list configuration controls which fields appear to reps so they can quickly understand account context without opening every account record.

In this scenario, the business wants field sales reps to see the most relevant account information directly in the aligned account list. After creating the account list, the consultant should configure it as the Default list type and select up to four visible fields as columns. This gives reps a concise, mobile-friendly view of the most important account details.

Option A is incorrect because configuring the Search list affects search-result display behavior, not the aligned account list columns. It also refers to up to five account fields, which does not match the aligned account list column configuration described in the question. Option B is incorrect because assigning ownership to field sales reps does not define the visible columns in the list. Column configuration is an admin setup activity, not something resolved by record ownership. Therefore, the consultant should set the list type to Default and configure up to four visible fields.

=========

Answer : C

Option C is correct because the business requirement is based on the HCP's relationship with a hospital, not the HCP's primary address. Salesforce Life Sciences Cloud Affiliations help organizations understand and map relationships between Healthcare Providers and Healthcare Organizations. Salesforce Help also describes Territory Alignment for Affiliated Accounts, where affiliated accounts can be aligned to territories based on affiliation relationships. This fits the scenario: the HCP's primary address points to San Francisco South, but their practice relationship with a hospital points to San Francisco North.

Option A is not the best answer because manually assigning the HCP to San Francisco North and excluding the record from future assignment rules creates a one-off exception. That may work temporarily, but it does not meet the requirement for automatic mapping based on practice location and affiliation. Option B is incorrect because it would use the HCP's primary address zip code, which the scenario says is aligned to San Francisco South. That would produce the wrong territory.

An affiliation assignment rule aligns the HCP based on their relationship with the hospital, so the HCP can be mapped to San Francisco North when the hospital affiliation drives the business alignment. Therefore, the correct configuration is to set up an affiliation assignment rule based on the HCP-HCO relationship.

=========