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

Option C is correct because Sample Inventory Management includes standard lock behavior for inventory operations based on status. The requirement is to prevent edits after a field sales rep submits inventory records such as transfers and adjustments. Salesforce Help references trigger handlers for Product Batch Item and Product Transfer objects, including ProductTransferLockHandler, which prevents modifications to Product Transfer records when the associated inventory operation is locked. This supports the standard Life Sciences pattern: the Inventory Operation reaches a locked status, and related inventory transaction records can no longer be modified.

Adding finalized status values to the Inventory Operation Locked Status list in Sample Inventory Settings is the appropriate administrative configuration because it tells the system which statuses should make the inventory operation locked. Once the record enters one of those statuses, the standard inventory lock handlers can enforce the restriction.

Option A is not the best answer because a restriction rule controls record visibility, not the complete GxP-style lock behavior for submitted inventory operations and related records. Option B is also not the best answer because a generic flow lock template is not the documented Sample Inventory Settings mechanism for locking inventory operations. Therefore, the consultant should configure the Inventory Operation Locked Status list with the finalized statuses that must prevent further edits.

=========

The correct answer is C because Salesforce Life Sciences Sample Inventory Management is intended to provide a unified view of sample-related inventory activity. Salesforce documentation describes Sample Inventory Management as providing a unified view of transactions, shipments, inventory counts, and assigned batches, helping users stay on top of items requiring attention. This directly matches the requirement for reps to monitor batch assignments, received inventory, disbursements, transfers, and returns from one experience rather than navigating across multiple object tabs.

To make that experience available in the Agentforce Life Sciences mobile app, the consultant should expose the Sample Inventory Management dashboard through the user’s navigation configuration. Adding it to Navigation Items ensures the field sales rep profile can access the dashboard from the mobile app. This is better than building a custom report type because the standard dashboard is purpose-built for Life Sciences sample inventory workflows and already aligns with the sample inventory data model and operations.

Option A is not the best answer because a custom report chart would be less functional than the standard inventory dashboard and would not provide the operational interface reps need. Option B is also incomplete. The Inventory Operations Timeline is useful for viewing transaction history, and Salesforce describes it as an overview of transactions and product requests in chronological order, but it does not provide the full dashboard experience for assigned batches, inventory counts, shipments, and operational status.

The correct answer is B because the business requirement says the system must block additional distributions once the sample limit is met. In Salesforce Life Sciences sample management, sample limits are used to control how many samples can be distributed to HCPs based on rules such as product, time period, and visit limits. Salesforce Help describes sample management features as supporting efficient and compliant handling and distribution of drug samples, while sample limits are part of the setup used to govern sample distribution.

The distinction between enforcement types is important. A Warning allows the rep to continue after being alerted. A Threshold is typically used to identify when a limit is nearing or reaching a defined point, but it does not satisfy the requirement to prevent excess sample distribution. An Error is the strictest enforcement behavior because it stops the transaction when the configured limit would be exceeded.

Here, Cumulus Pharma needs hard compliance enforcement: maximum 5 units per HCP per calendar year and maximum 2 units per visit. Since the system must prevent field sales reps from exceeding those values, the consultant should set the sample limit enforcement type to Error . This ensures the disbursement cannot proceed when the annual or per-visit limit has already been reached.

=========

Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep’s targets.

Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.

Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.

=========

The correct answer is B because the standard field that represents whether a received document is incoming or outgoing is Direction . Salesforce’s Life Sciences Cloud Developer Guide for the ReceivedDocument object lists direction values such as INCOMING — Incoming and OUTGOING — Outgoing , which directly matches the reporting requirement in the scenario.

The operations manager wants to analyze document volume based on whether consent forms are flowing into the organization from HCPs or being sent out to HCPs. That is a directional reporting requirement, not a document lifecycle or status requirement. Grouping the report by the Direction field allows the team to separate inbound consent forms from outbound documents using standard Salesforce data rather than creating a custom field or relying on interpretation.

Option A, Flow Type , is incorrect because the question is not asking about a business process type, document-processing flow, or automation path. It specifically asks for whether the document was incoming or outgoing. Option C, Document Status , is also incorrect because status would indicate where the document is in its lifecycle, such as received, processed, pending, or completed depending on configuration. Status does not define the direction of the document exchange. Therefore, the consultant should recommend grouping and filtering the report by the standard Direction field on Received Document.

=========

Option B is correct because the requirement is specifically to prevent visit creation when a Visit overlaps with a Time Off Territory record. Salesforce Life Sciences documentation references Time Off Territory overlapping rules as the standard mechanism that prevents creating visits during TOT events. Salesforce’s Winter ’26 Customer Engagement package patch notes also mention an issue where a visit could be created during a Time Off Territory event, bypassing the overlapping rule that should have prevented creation. That confirms TOT overlapping rules are the expected standard control for this scenario.

Because the business wants a hard stop, the overlapping rule behavior must be set to “Error.” This means the rep receives an error and cannot proceed with scheduling the visit while it conflicts with the TOT time block.

Option A is incorrect because a custom validation rule on Visit would duplicate a standard Life Sciences calendar/TOT capability and may not handle the full mobile scheduling experience correctly. Option C is also not the best answer because “Block Activity on Conflict” on the TOT record type is not the documented standard configuration in the Life Sciences Visit/Calendar settings. The correct standard configuration is to use TOT Overlapping Rules and set the overlap behavior to Error. This prevents scheduling visits during the rep’s logged time off.

=========

The correct answer is B because sprint completion values are configured in the Life Sciences Admin Console under Key Account Management sprint settings. Salesforce Help for Configure Sprint Completion Statuses states that administrators should go to the App Launcher, open Admin Console , select Key Account Management , and then select Sprints Settings in the left navigation pane. From there, admins add the sprint values that indicate completion.

The scenario says KAMs are selecting a picklist value called “Finished,” but the system does not recognize the sprint as closed for reporting. That means the label exists as a picklist option, but it has not been mapped as a completion status in the Life Sciences Key Account Management sprint configuration. The consultant must configure the completion-status mapping in Sprint Settings so the platform treats “Finished” as a closed/completed sprint value.

Option A is too broad and does not point to the specific sprint completion configuration. Option C is also incorrect because editing the Status picklist in Object Manager only changes or adds picklist values. It does not tell the Life Sciences Key Account Management logic which values count as completed for reporting and process behavior. Therefore, the mapping should be configured in Admin Console > Key Account Management > Sprint Settings .

=========

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.

=========

Option A is correct because this is a mobile rendering limitation, not a data or filter issue. Salesforce documentation for reports and dashboards on mobile describes differences and limitations between desktop and the Salesforce mobile app. When a dashboard component appears on desktop but not in the mobile app, the consultant should first check mobile dashboard support and component compatibility rather than assuming that the report data is missing.

The question states that the funnel charts appear on desktop, which strongly indicates that the underlying reports and reporting periods are valid. If the data were missing for the selected reporting period, the chart would fail or show no data consistently, not only on mobile. Option C is therefore not a good fit. Option B is also incorrect because dashboard filters can affect what data is shown, but they do not make an unsupported chart type render in the mobile app.

Salesforce Help also discusses making dashboards available in mobile workflows and notes that mobile dashboard behavior depends on how dashboards are embedded and rendered in the Salesforce mobile app. For this scenario, the consultant should recommend replacing the funnel chart with a mobile-supported visualization or providing an alternate dashboard component for mobile users. Therefore, the correct answer is that funnel charts are not supported in the mobile app.

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.

=========