Als-Con-201 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
Option A is the best answer because the requirement is specifically tied to the Next Best Customer user experience. Salesforce Life Sciences Cloud uses Next Best Customer to help sales reps understand and work with the top accounts in their territory by configuring the Next Best Customer component, quick actions, scores, and rationales. Salesforce Help also references Account Scores and Rationales for Next Best Customer as part of the setup path, which confirms that scores and supporting rationale are standard parts of the Next Best Customer capability.
The reps are not asking for a separate generic charting capability or a custom extension. They want to see the data that explains why a customer is recommended and how the score was derived. Embedded charts on the Next Best Customer component meet this requirement because they keep the rationale visualization directly in the same workflow where reps prioritize accounts and plan visits.
Option B is not the best answer because extending the Next Best Customer FlexCard would imply custom development or UI customization when the requirement can be met through the standard component experience.
Option C is also not the best answer because the Chart Lightning Web Component Accelerator is a generic charting component, not the Life Sciences-specific Next Best Customer configuration for showing recommendation rationale. Therefore, embedded charts on the Next Best Customer component are the correct recommendation.

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

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

Explanation:
The correct answer is A because Salesforce Life Sciences Territory Management batch jobs can be scheduled with an hourly frequency. Salesforce Help for running Territory Management jobs states that, from the Life Sciences Commercial Admin Console, the job can be scheduled hourly, every selected hours, by selecting the hour from the dropdown. This confirms that hourly scheduling is a supported automatic execution option for Territory Management batch jobs.
Territory Management batch jobs are important because Life Sciences territory configuration affects field execution, account alignment, provider access, and downstream engagement processes. Scheduling these jobs automatically helps ensure that territory-related processing runs on a predictable cadence without requiring administrators to manually start each batch job. When the question asks how often the jobs can be scheduled to execute automatically, the available option that matches Salesforce’s documented scheduling capability is Hourly.
Option B, Every 12 hours, may sound plausible because some enterprise batch processes use longer intervals, but it is not the best answer because Salesforce’s documented configuration describes hourly scheduling and selecting the hour interval.
Option C, Monthly, is also incorrect because monthly execution would be too infrequent for many territory-management operational updates and is not the option reflected in the documented batch-job scheduling guidance. Therefore, the consultant should identify Hourly as the correct scheduling frequency.

Explanation:
The correct answer is B because the product must be enabled for discussion in the visit-detailing experience. Salesforce’s Life Sciences Visit Management developer documentation states that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples. Salesforce Trailhead also explains that Life Sciences Cloud uses product administration and product-message configuration to ensure reps only promote and discuss therapies within approved guardrails.
The scenario says the product exists in Salesforce, but it does not appear when the rep tries to add it to the Product Detailing section during a visit. That means the issue is not product creation; it is visit-discussion eligibility. The consultant should configure Product Discussion Settings in the Visit Administration area so Immunexis is available for product detailing and visit discussions.
Option A is incorrect because Territory Product Alignment Rules determine which products are aligned to territories, but the question specifically says the product must be explicitly enabled for use in visit discussions. Territory alignment alone does not guarantee the product appears in the Product Detailing search.
Option C is also incorrect because Visit Record Type Mappings control record-type behavior, not whether a product can be discussed. Therefore, the correct configuration is Product Discussion Settings.