Dominate the Salesforce Als-Con-201: Real Agentforce Logic & Prep (2026)

The correct answer is A because the symptom is specifically about Case ownership not changing after a Medical Inquiry is submitted. Salesforce Help for Medical Inquiries shows that the inquiry workflow uses Case status values such as Draft , Signed , Submitted , and Assigned , and Life Sciences Cloud also provides Trigger Handler Administration for configuring Life Sciences trigger handlers, including trigger handlers related to Case objects.

In the scenario, the status update is working correctly: the signed inquiry becomes Submitted . That means the submission process itself is functioning. The failure is isolated to ownership routing: the Case remains owned by the field sales rep instead of being routed to the Medical Science Liaison team or queue. Based on the available options, CaseChangeOwnershipHandler is the handler that directly corresponds to changing ownership on the Case record.

Option B, MSLInquirySubmissionHandler , sounds related to Medical Inquiry submission, but the submission status already updates correctly, so that is unlikely to be the inactive piece. Option C, CaseMSLQueueHandler , sounds like queue routing, but the Salesforce-style handler name that most directly describes the failed behavior is CaseChangeOwnershipHandler . Since the issue is ownership transfer after submission, the inactive trigger handler is CaseChangeOwnershipHandler .

=========

The correct answer is C because the requirement is to lock a submitted visit report so it can no longer be edited. Salesforce Life Sciences Visit Management supports compliant planning, execution, and reporting for provider visits, and Salesforce Help directs administrators to use the Visit Management Admin Console to configure what fields users can see and how users can interact with and manage visit records.

A submitted visit report often represents a compliance-sensitive record, especially in life sciences, where visit details, sampling activity, consent capture, and inquiry handling may need to remain auditable after submission. Enabling VisitLockHandler enforces the locking behavior, while leaving Unlock submitted visit unchecked prevents the record from being reopened or edited after final submission. This configuration best matches the requirement that the submitted visit report become immutable.

Option A is incorrect because VisitAutoSaveHandler relates to saving visit data, and checking “Allow edits after submission” would contradict the stated requirement. The business specifically wants no further edits after submission. Option B is also incorrect because disabling a permissions handler and setting the status to Closed does not directly enforce immutable submitted-visit behavior. Status alone is not the same as a record lock. Therefore, the consultant should enable VisitLockHandler and ensure submitted visits remain locked by unchecking Unlock submitted visit in the Admin Console.

=========

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.

=========

The correct answer is B because Life Sciences Cloud supports configuring quick actions for the mobile app through the Admin Console. Salesforce Help for Medical Insights states that Medical Insights can be made available to users in the Life Sciences mobile app so users can view their own insights and insights shared with them. Salesforce Help also describes Quick and Custom Action Management as the way to simplify user experiences in Salesforce and the Life Sciences for Customer Engagement mobile app by leveraging quick actions and custom actions.

The requirement is not merely to expose the Medical Insights tab. The rep must be able to quickly report a medical insight while managing a visit on an iPad. Configuring the Create Medical Insights quick action in the Admin Console makes the action available in the mobile workflow where reps need it. This supports fast, in-context capture of field observations during a visit.

Option A is incorrect because creating a custom action and custom flow adds unnecessary complexity when the standard quick action can be configured declaratively. Option C is also not the best answer because editing the Visit page layout and adding a generic standard action may not make the action available correctly in the Life Sciences mobile app experience. The Admin Console is the correct configuration point for mobile quick actions. Therefore, the consultant should configure the Create Medical Insights quick action using the Admin Console.

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

=========

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 C is correct because Salesforce Help identifies “Access Life Sciences Customer Engagement Agentforce” as the permission required for Life Sciences Customer Engagement Agentforce capabilities. In the Salesforce Help reference for the Life Sciences “Generate Healthcare Provider Summary” action, Salesforce lists the required access as Access Life Sciences Customer Engagement Agentforce. It also notes that, to run flows associated with agent actions, users need the Run Flows app permission or access to the individual flows.

This directly matches the scenario. The Life Sciences Field Sales agent template has already been configured and activated, but the field sales rep cannot use the agent-generated HCP summary capability. That means the issue is not the existence of the agent or the template; it is the user’s permission to access the Life Sciences Customer Engagement Agentforce features. Salesforce’s Account Summarization permissions documentation also references Access Life Sciences Customer Engagement Agentforce as part of the permission setup for account summarization, alongside standard Life Sciences user permission sets.

Option A, Life Sciences Commercial User, is not specific enough to grant access to these Agentforce capabilities. Option B, Agentforce Service Agent User, relates to Agentforce service use cases and is not the Life Sciences Customer Engagement permission named in the documentation. Therefore, the consultant should assign Access Life Sciences Customer Engagement Agentforce.

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 .

=========

The correct answer is C because field sales reps only need to view and consume Tableau Next metrics in the Life Sciences mobile app. Salesforce Help for Tableau Next in Life Sciences Cloud explains that Tableau Next integrates with Life Sciences Cloud to provide actionable insights and enhanced visualizations. Salesforce’s Tableau Next permission guidance also identifies Tableau Next Consumer as the permission set used for viewing Tableau Next content and interacting with metrics, while creator-level access is intended for users who create and manage Tableau Next assets.

In this scenario, the technical setup has already been completed: the metrics exist, the Tableau View component has been placed on the Mobile Home Page Lightning record page, and the mobile metadata cache has been refreshed. The remaining issue is an insufficient-privileges error, which indicates that the user lacks the Tableau Next permissions required to load and consume the metric. Assigning Tableau Next Consumer grants the field rep the appropriate access level without giving unnecessary authoring privileges.

Option A, Tableau Next Creator , is incorrect because field sales reps are not creating or administering metrics; they only need to consume them. Option B, CRM Analytics Plus User , is also incorrect because the requirement is specifically for Tableau Next metrics, not legacy CRM Analytics access. Therefore, the consultant should assign the Tableau Next Consumer permission set.

=========