Als-Con-201 Salesforce Certified Agentforce Life Sciences Consultant Free Practice Exam Questions (2026 Updated)

Option A is correct because Life Sciences Workflow Management is designed to control what users can do at different stages of a Life Sciences process, including Medical Inquiries. Salesforce Help for configuring Life Sciences workflow paths states that admins define stage operation conditions that must be met to grant users access to operations. Salesforce also provides specific setup guidance for workflow stages used to manage Medical Inquiries, including adding actions to stage operations and configuring stage operation conditions.

This fits the requirement exactly. The access rules change depending on the Medical Inquiry’s stage: Draft, Assigned, Responded, Signed, or Submitted. Salesforce’s Inquiry object documentation confirms these inquiry statuses are standard values used in the Medical Inquiries process.

Option B is incorrect because criteria-based sharing rules on Case would not dynamically manage stage-specific CRUD behavior for the Life Sciences Inquiry workflow. Also, the question is about Medical Inquiries, not generic Case sharing. Option C is also incorrect because validation rules and dynamic page layouts can restrict or hide fields and actions, but they do not provide the standard stage-based security model required here. Therefore, the consultant should configure Stage Operations and Stage Operation Conditions within Life Sciences Workflow Management.

=========

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 .

=========

The correct answer is A because provider summary generation depends on the prompt template and the data supplied to that prompt. In Life Sciences Cloud account summarization, Salesforce documentation references custom prompt templates for account summarization and the account summarization workflow, while the workflow uses the Generate Provider Account Territory Summary flow as part of the summary-generation process. Salesforce also documents that this flow calls actions such as Get Object Relationship Data and Get Life Sciences Configuration Field Names , meaning the flow participates in retrieving relationship-based data, but the generated business summary still needs the prompt template to know what information to use and how to summarize it.

Updating the ARC graph alone makes additional objects and fields available in the relationship structure, but it does not automatically change the prompt’s summarization behavior. To ensure the new information is used correctly, the consultant should create a new prompt template version, update the input dataset so the new fields are included, revise the summarization instructions so the AI knows how to use them, and then activate that version. This aligns with Salesforce’s guidance that prompt-based generation relies on the configured prompt and its grounding/input data. Option B is incomplete because changing only the flow does not update the prompt’s instructions. Option C is also incorrect because batch-job configuration controls bulk execution, not the actual summarization logic.

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 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.

=========

The correct answer is B because the requirement is to enable the Life Sciences visit and calendar setting that surfaces best-time recommendations for planning. Salesforce Help for Life Sciences Calendar states that users can schedule visits and other events while using best time recommendations . Salesforce also provides guidance for configuring filters to find best visit times, explaining that users can filter accounts by a healthcare professional’s preferred engagement time to plan and schedule visits more effectively.

The key phrase in the question is that the feature must be enabled in Visit/Calendar settings . “Best Time Settings” is the configuration area that supports the optimization. Once enabled, the system can use historical engagement patterns and preferred engagement timing to help reps plan visits when HCPs are more likely to be available or receptive.

Option A is close in meaning, but “Set up Provider Best Time” describes the capability more generally rather than the setting in Visit/Calendar settings. Option C is incorrect because operating hours represent general availability windows for an account or location. Operating hours can help prevent scheduling at inappropriate times, but they do not provide intelligent recommendations based on historical engagement data. Therefore, the consultant should enable Best Time Settings .

=========

The correct answer is A because Account Summarization can use different Cross-Object Field History Graph assignments by org or profile. Salesforce Help for Life Sciences Account Summarization states that administrators can create a Cross-Object Graph for Account Summarization and assign cross-object graphs to an org or profile. Salesforce also describes the Account Summarization workflow as using configured cross-object field history so summaries can include recent and relevant account changes from related objects.

In this case, KAMs see summaries that include Provider Visit and Medical Inquiry records, while field sales reps do not. Both groups have Read access to the objects, so object permission is not the root cause. The difference is most likely profile-based summarization configuration: the graph containing Provider Visit and Medical Inquiry data has been assigned to the KAM profile but not to the field sales rep profile.

Option B is incorrect because Account Summary generation in this scenario is driven by Cross-Object Field History Graph configuration, not membership in a Data 360 segment. Option C is also incorrect because the question explicitly says both user groups have Read access. View All is not the stated requirement for using a graph in summarization. Therefore, the issue is that the Cross-Object Field History Graph is not assigned to the field sales rep profile.

=========

Option C is correct because the issue is isolated to the selected target account list, not to the overall availability of HCO accounts in the territory or application. Salesforce Life Sciences Cloud supports Lists and Filters so users can quickly identify a target group of accounts. These lists can be manually curated or filtered, meaning the accounts shown depend on the criteria or membership of the specific list being used. If only HCP accounts appear while HCO accounts are still aligned to the territory and visible elsewhere, the most likely cause is that the selected target account list itself includes only HCP accounts. Salesforce’s Life Sciences Cloud Developer Guide describes Lists and Filters as a way to quickly identify target account groups, and the LifeScienceAccountList object represents account list types such as filter, static list, and routine list.

Option A is not the best answer because Planner Administration record type settings would more broadly control planner behavior, not only one selected target account list. Option B is also not the best answer because Account Management record type configuration would affect how account types are configured or displayed more generally. The question states that HCO accounts are aligned and available elsewhere, which eliminates a broad record type or account management restriction. The problem occurs only when using the selected target account list during visit creation. Therefore, the consultant should review and correct the target account list criteria or membership so that both HCP and HCO accounts are included when needed.

=========

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 C because Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit. Salesforce Help for Add Internal Users as Visitors states that administrators can configure the visitors feature so field reps can record internal colleagues who participate in visits and automatically share visit data with them. This directly matches the requirement to include an MSL in the scheduled remote visit and track that person’s participation.

The MSL is not the primary HCP attendee and does not need a separate visit record. Instead, the MSL is an internal participant supporting the visit. Using the standard Add Visitors (Users) to a Visit action keeps the visit record intact while documenting the MSL as a participating internal user. It also supports better compliance, collaboration, and reporting because the MSL’s involvement is recorded against the actual visit.

Option A is incorrect because creating a separate Visit record would fragment the visit history and could cause duplicate or inconsistent reporting. Option B is incomplete because emailing the meeting link may help the MSL join the session, but it does not track the MSL’s participation in the Life Sciences Visit Management data model. The correct standard action is Add Visitors (Users) to a Visit .

=========

Option A is correct because Salesforce Help for setting up the Inquiry record page for Medical Inquiries explicitly states that, to view timeline details for inquiries, the consultant should drag the Timeline component to the page. The requirement in the question is to expose a chronological list of key events and changes associated with the inquiry. That is exactly the purpose of the Timeline component on the Medical Inquiries record page.

Salesforce also documents Enhanced Timeline for Life Sciences Cloud, explaining that the Enhanced Timeline component shows key events relating to a person or a record. This supports the use case of giving users a consolidated, chronological view of relevant inquiry activity, rather than requiring them to inspect multiple related lists or audit records separately.

Option B is not the best answer because field history tracking and the standard History component are used for field-level audit history, not the Life Sciences Medical Inquiries timeline experience. Option C is also incorrect because adding an Inquiry History related list would expose related records, but it would not provide the configured timeline component experience described in Salesforce’s Medical Inquiries setup documentation.

Therefore, the consultant must drag the Timeline component onto the Lightning record page and configure its component details for the Inquiry record page.

The correct answer is A because Remote Engagement video traffic requires Twilio endpoints to be trusted by the Salesforce org. Salesforce Help for setting up Twilio for Remote Engagement states that participants can connect to video calls by adding Twilio WSS endpoints as Trusted URLs in the Salesforce org. This is specifically required for secure video-call connectivity, which directly matches the symptom in the question: the Twilio credentials and Experience Cloud site are configured, but the video media fails to load.

Twilio External Credentials handle authentication and connection details for the integration, and the Experience Cloud site provides the HCP-facing remote engagement experience. However, browser and Salesforce security controls still need to allow the required Twilio WebSocket Secure traffic. If those URLs are not trusted, the page can load while the actual audio/video media connection fails.

Option B is incorrect because assigning a field-sales permission set to the Site Guest User would be inappropriate and overly permissive. The issue is media connectivity, not guest-user access to sales functions. Option C is also incorrect because a trigger handler for remote-session invitations would relate to record automation or invitation behavior, not secure loading of Twilio video traffic. Therefore, the consultant must add Twilio’s required endpoints to Trusted URLs .

=========

Option B is correct because MIRF Share Management is the Life Sciences Cloud batch job used to manage sharing for Medical Inquiry records. Salesforce Help describes Medical Inquiries as supporting batch jobs that share and manage multiple medical inquiry records consistently and efficiently, and specifically identifies the MIRF Share Management job as the job used to maintain inquiry-data sharing. This directly matches the scenario: after a territory reorganization, field sales reps need access recalculated for historical Medical Inquiry records associated with HCPs in their newly assigned territories.

Option A is not the best answer because Account Object Share Rule Calculation is a generic description of account sharing recalculation. The issue is not general Account visibility; it is Medical Inquiry record visibility after territory changes. Option C is also incorrect because aligning accounts to territories handles territory assignment, but the accounts have already been reorganized. The remaining problem is recalculating access to Medical Inquiry records that should now be shared according to the new territory model.

Therefore, the consultant should run MIRF Share Management. This batch job is the standard Life Sciences mechanism for recalculating Medical Inquiry record sharing and ensuring field users regain access to inquiry records that correspond to their current territory-aligned HCPs.

=========

The correct answer is B because the deadlines and review windows for activity-plan adjustments are configured on the Activity Plan record, specifically in the review-related configuration. Salesforce Help for creating Activity Plans references fields such as Reviewer Plan Adjustment Start Date and Reviewer Plan Adjustment End Date , which define the date range in which the manager can review adjustment requests.

The scenario describes a plan-level governance requirement: field sales reps must submit proposed visit targets by a specific deadline, and adjustments above allowed thresholds must be reviewed. This belongs to the Activity Plan configuration because the plan defines the cycle, timing, targets, review process, and adjustment behavior for the territory or provider planning period. Configuring the Review Details section ensures that the plan controls when reps can submit changes and when managers can review them.

Option A is incorrect because Global Calculation Settings for a Provider Activity Measure Type would relate to how measures or calculations are evaluated, not the submission and manager-review deadline for a specific Activity Plan. Option C is also incorrect because a Goal Definition represents a reusable planning objective, but it does not control the operational review dates and adjustment thresholds for a specific West Coast Activity Plan. Therefore, the consultant should configure the deadlines and adjustment limits on the Activity Plan record within the Review Details section .

=========

The correct answer is A because distance-based sorting in the Next Best Customer mobile component requires geolocation data on the account’s relevant address. Salesforce Help for configuring Next Best Customer settings for the mobile app states that, to ensure accounts are accurately sorted by distance, geolocation data must be captured for the primary address or preferred address. Salesforce Help also explains that if no preferred address is available, distance is calculated using the account’s primary Contact Point Address.

The reps already confirmed that location services are enabled on the iPad, so the issue is not the mobile device’s ability to determine the user’s current location. The missing piece is the account-side location data. If the primary or preferred address does not contain valid latitude and longitude values, the component cannot accurately calculate the distance between the rep and the account. As a result, accounts may appear with a distance of 0 or behave incorrectly when sorted by distance.

Option B is incorrect because a manual refresh does not solve missing geolocation data. Refreshing the component may reload records, but it cannot calculate distance without valid address coordinates. Option C is also incorrect because territory alignment is important for determining which accounts are relevant to the rep, but the distance calculation itself depends on geolocation data. Therefore, the root cause is missing geolocation data on the account’s primary or preferred address.

=========