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

The correct answer is B because the requirement is specifically compliance-driven verification of sample holdings against an audit trail. Salesforce Help for Sample Inventory Management identifies inventory assessment types, including Ad hoc , Periodic , and Audited . It describes Ad hoc as an unplanned inventory count, Periodic as an inventory count used to comply with organizational guidelines, and Audited as a self-audit, declaration of inventory count, or peer audit.

The scenario mentions preparation for an FDA inspection, which is more rigorous than a routine count or unplanned check. The purpose is to verify current holdings against the digital audit trail and support compliance evidence. An Audited assessment is designed for this type of controlled verification because it supports audit-oriented sample inventory confirmation.

Option A, Ad Hoc , is incorrect because an ad hoc count is generally unplanned and operational, such as preparing for a visit or checking inventory outside a regular schedule. While useful, it does not best represent formal inspection readiness. Option C, Periodic , is also not the best answer because periodic counts are recurring counts based on company policy or schedule. The question focuses on audit preparation and verification against the digital audit trail, making Audited the most appropriate assessment type. Therefore, the consultant should recommend an Audited assessment.

=========

The correct answer is C because Provider Cards are designed to consolidate key account information from multiple objects and fields into a single user-friendly account view. Salesforce Help describes Provider Cards in Life Sciences Cloud as consolidating an account’s information that is scattered across objects and fields, such as provider locations and related account information. Salesforce also describes the Provider Account Territory Info object as representing engagement data between an account and a user within an assigned territory, including account-territory context such as visit and engagement details.

The requirement is to display an indicator, not to filter accounts out of the card. Field reps need to see whether each account is a target or not. Adding an item group element to the Provider Card section and including the Targeted Account field from Provider Account Territory Info allows the template to display territory-specific targeting information. Visibility conditions can then show “Target” when the field value indicates the account is targeted and “Not Target” when it is not.

Option A is incorrect because filtering to show only targeted accounts would hide non-targeted accounts, but the requirement is to display both states. Option B is not the best answer because a repeater is used for repeating multiple related records, not for showing a single indicator from the account-territory information context. Therefore, the consultant should use an item group element with the Targeted Account field and visibility conditions.

=========

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.

=========

The correct answer is C because an Action Plan Template Assignment connects predefined action-plan tasks to reusable planning objectives so Key Account Managers can import standardized objectives into account plans with tactical steps already attached. Salesforce Help for Life Sciences Key Account Management explains that a Goal Definition represents a broad business objective that can be reused across global, national, and territory levels. It also states that when creating account plan objectives, users can import templates and choose goal definitions with action plans and assessment tasks to add to account plans.

The key phrase in the scenario is “with predefined tactical steps.” A high-level corporate objective alone would not be enough. The organization also wants repeatable execution tasks that KAMs can bring into individual account plans. Creating an Action Plan Template Assignment supports this by associating the action plan template with the goal definition, so the imported objective includes the structured actions needed for execution.

Option A, Account Plan Objective Link , is incorrect because it suggests linking an objective after the fact rather than defining a reusable objective with tactical steps. Option B, Goal Definition Product , is also not the best answer. A product association may be useful for a product launch, but it does not provide the predefined action-plan tasks required by the business process. Therefore, the consultant should create an Action Plan Template Assignment .

Option B, Dynamic Segmentation, is correct because the sample limit assignment must change automatically when the HCP’s Engagement Tier changes. Salesforce’s Life Sciences Cloud segmentation data model supports entities and relationships for creating and managing static and dynamic account segmentations. It also shows the connection between account segmentation, Healthcare Provider records, Product2, Provider Sample Limit, Provider Sample Limit Template, and Life Science Account Group Assignment. This confirms that segmentation is reusable in sample limit scenarios and can drive which sample limit template applies to a provider.

The important phrase in the question is “automatically update.” Because Engagement Tier is a calculated Account field that changes monthly, the consultant needs a rule-based segmentation approach. Dynamic Segmentation evaluates account criteria and can move accounts between groups as their data changes. When the HCP qualifies for the Tier 1 segment, the higher sample limit template can apply without an administrator manually reassigning the provider.

Option A, Account Segmentation, is too broad and does not specifically indicate the automatic, rule-driven behavior needed here. Option C, Sample Segmentation, sounds related to samples, but the key requirement is not merely grouping sample policies; it is dynamic reassignment based on changing account criteria. Therefore, Dynamic Segmentation is the correct configuration to support automatic sample limit changes as HCP engagement tiers change.

=========

Option B is correct because the requirement is based on an HCP’s affiliation with an HCO and a specialty filter. Salesforce Life Sciences Cloud supports Territory Alignment for Affiliated Accounts, which lets organizations align affiliated accounts to specific territories. Salesforce Help also states that admins can define affiliation alignment rules to automatically align affiliated accounts to territories. This is the correct configuration when territory assignment must depend on the relationship between an HCP and an HCO, rather than only the HCP’s standalone demographic or geographic attributes.

The question specifically says that only oncology-specialty HCPs affiliated with a specific HCO should be automatically aligned. An affiliation alignment rule can use Care Specialty as a criterion, so selecting “Oncology” ensures that only matching affiliated HCPs are included. Other specialties at the same HCO are excluded because they do not meet the specialty condition.

Option A is not the best answer because a territory geo assignment rule evaluates territory assignment using geographic or account-level criteria. It does not specifically model the affiliated-account relationship with the HCO. Option C is incorrect because sharing rules only control record visibility; they do not perform territory alignment. Therefore, the consultant should configure an affiliation alignment rule for the territory and select Care Specialty as “Oncology.”

=========

The correct answer is B because physical sample disbursement to an HCP requires compliant signature capture to confirm the handoff and support the audit trail. Salesforce’s Life Sciences Customer Engagement data model states that Provider Visit Management supports compliance requirements for sample eligibility, sample limits, allocations, and e-signature capture . Salesforce also describes Electronic Signatures through Digital Verifications as the way to set up signature trails for records or workflows that require users to verify key updates.

In this scenario, the field sales rep is physically transferring custody of a restricted product to the HCP. To finalize that disbursement and generate the required electronic receipt, the rep must capture the HCP’s digital signature directly on the mobile device. This ties the transaction to the HCP, the product, the quantity, the timestamp, and the specific disbursement event.

Option A is incorrect because an Inventory Adjustment is used to reconcile inventory discrepancies or administrative stock changes, not to document a compliant HCP sample handoff. Option C is also incorrect because a confirmation email is not the standard Life Sciences sample-disbursement action for chain-of-custody compliance. The required mobile action is direct digital signature capture from the HCP.

=========

Option B is correct because Salesforce Life Sciences Activity Plans use weighted goals to measure activities differently based on business importance. Salesforce Help for creating Activity Plans states that, to track weighted goals, administrators create Provider Activity Goal Measure records to define weights, select Weighted Goal in the Type field, and assign a value in Activity Weight Value. This directly supports the requirement to measure high-impact activities differently from standard activities.

Activity Plans are designed to transform provider interaction strategies into actionable goals and targets for field representatives. When certain activities with specific HCPs are more strategically important, weighted goals allow those activities to contribute differently to plan performance. This is more precise than simply counting every activity equally.

Option A is incorrect because “High Impact Goal” is not the documented Type value for this configuration. The Salesforce Help wording identifies “Weighted Goal” as the Type value used for weighted measurement. Option C is also not correct because the documented field is Activity Weight Value, not Activity Impact. Even if a percentage-based concept sounds plausible, the standard configuration step is to set the Provider Activity Goal Measure Type to Weighted Goal and enter the weight value. Therefore, the consultant should select Weighted Goal for the Type field.

=========

The correct answer is C: Perform audits of Inventory Count Assessment records user permission. In Life Sciences Cloud sample inventory management, Inventory Count Assessment records are used to support inventory count and audit processes. Salesforce documentation distinguishes between conducting or performing an audit and requesting an audit. The wording in the question asks which permission is needed for a user to conduct a self-audit of their inventory count. Because the action is to perform the audit, the required permission is the user permission that allows users to perform audits of Inventory Count Assessment records.

Option A is incorrect because the Life Sciences Field Sales Representative permission set alone should not be assumed to include every inventory audit capability by default. Salesforce Life Sciences sample inventory features use specific user permissions for different inventory audit actions, so the named permission is the safer and more precise answer. Option B is incorrect because “Request audits of multiple Inventory Count Assessment records” is related to submitting or requesting audits, especially peer-audit-style workflows, not personally conducting the self-audit. Salesforce Help notes that requesting a peer audit requires the Request Multiple Inventory Count Assessment Audits user permission, which confirms that request permission is separate from the permission to perform audits.

Therefore, for a self-audit where the user is actually conducting the audit activity, the correct permission is “Perform audits of Inventory Count Assessment records.”

Option B is correct because Salesforce Life Sciences Cloud provides a standard Data Change Requests framework for governed master-data updates. The requirement is not simply to block a change or create a manual task; it is to route critical HCP data changes to a Data Steward for review before the change is applied. Salesforce’s Life Sciences Cloud Account Management documentation describes Data Change Requests as a capability used to validate data changes by objects and fields and configure data changes by profile and record type. That aligns directly with controlled governance over fields such as Medical License Number.

The specific configuration object in the question, LifeSciDataChgPersonaDef, represents the persona-based data-change configuration. Salesforce’s Developer Guide identifies LifeSciDataChgPersonaDef as part of Data Change Requests and includes the ChangeUpdateType picklist field. Setting ChangeUpdateType to DoNotApplyChangesImmediately means changes are not applied directly by the sales rep persona and can instead be managed through the data-change governance process.

Option A is not the best answer because a custom record-triggered flow would duplicate standard Life Sciences Cloud data-change governance and could create maintenance or compliance risk. Option C is also not ideal because a validation rule only blocks the update; it does not create the governed change-request process needed for Data Steward review. Salesforce’s Data Change Requests data model includes Life Science Data Change Definition, managed fields, record types, persona definitions, and Life Science Data Change Request, confirming this is the intended standard architecture.

=========

The correct answer is A because the requirement is for a single embedded, interactive graph that visualizes multiple relationship types around an HCP. Salesforce describes Actionable Relationship Center (ARC) as a capability for viewing relationships among people and businesses in an interactive graph. Salesforce also describes ARC as supporting entity hierarchy and entity relationship visualization, and Life Sciences provider-card guidance references account-related object relationships in an ARC graph.

This scenario includes more than a simple parent-child hierarchy. The HCP has an employment relationship with one hospital, affiliation relationships with two additional hospitals, and a Key Opinion Leader role for a research study. ARC is designed for this type of multi-object, multi-relationship visualization. It allows users to see related entities in context and navigate through connected records from a graph-based interface rather than moving through several related lists.

Option B, Einstein Relationship Insights , is incorrect because it is not the Life Sciences page component used to display a configured relationship graph for HCP-related records. Option C, Account Hierarchy Visualization , is also too limited because account hierarchy is generally used for hierarchical account structures, not a broader relationship network involving employment, affiliations, KOL status, and research-study connections. Since the requirement calls for an interactive relationship graph embedded on the record page, the consultant should implement Actionable Relationship Center .

=========

The correct answer is A because Salesforce’s Remote Engagement setup guidance for Life Sciences Cloud specifically identifies the Experience Cloud site as the place where language support is configured for remote engagement experiences. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that, for language support, the administrator should select Components and drag the Language Selector component to the page. This directly supports the requirement for HCPs to review and accept terms and conditions in multiple languages when joining remote visits.

Remote Engagement involves an HCP-facing experience, not only a sales-rep mobile action. The terms and conditions are presented through the Experience Cloud site used for the remote session, so the language-selection capability must be available there. Adding the Language Selector lets the HCP choose the appropriate language in the site experience before reviewing the terms.

Option B is incorrect because configuring the Start Remote Session quick action may help reps launch or manage remote sessions, but it does not provide the HCP-facing multilingual site control required for terms and conditions. Option C is also incorrect because a survey can collect feedback or preferences, but it is not the Salesforce-recommended way to localize the terms-and-conditions experience. The correct configuration is to add the Language Selector component to the Experience Cloud site.

=========

Option C is correct because Advanced Sample Limit Templates are designed for custom, complex sample-limit rules. Salesforce Help explains that advanced sample limit templates are used to define custom sample limit rules for more complex needs and stricter requirements. This scenario requires two non-basic behaviors: a dynamic period start based on the product launch date and soft-limit enforcement that warns the rep but still allows the disbursement to proceed. Those requirements go beyond a generic calendar-year rule.

A Generic Sample Limit Template is not the best answer because generic templates are better suited for standard sample-limit logic. The requirement explicitly says the limit period must begin on the Product Launch Date rather than the standard Calendar Year, which makes the rule more specialized. A Country Sample Limit Template is also not correct because country templates are used for country-specific legal or regulatory sampling limits. In this question, the control is strategic and inventory-driven, not a legal requirement tied to a specific country.

Advanced templates are the correct fit because they allow more flexible configuration for business-specific sample controls, including nonstandard periods and warning-based enforcement. Therefore, the consultant should use an Advanced Sample Limit Template for the Immunexis launch sampling rule.

=========

The correct answer is B because the requirement combines two controls: a territory-level cap for a product during a defined period and a per-visit disbursement limit for sales reps. Salesforce Life Sciences documentation for Territory Product Quantity Allocations states that these allocations are used to manage sample product distribution to healthcare professionals, and the setup guidance specifically references the Max Disbursement Limit Quantity as the maximum amount a sales rep can disburse in a given visit.

A Territory Product Quantity Allocation record is designed for the exact scenario described: controlling how much of a specific product is allocated to a territory and limiting how much can be disbursed during a visit. The consultant would define the allocated quantity for Immunexis 50mg for the high-growth territory for the next quarter and set the Max Disbursement Limit Quantity to 50 so that an individual field sales rep cannot hand off more than 50 units in one visit.

Option A is incorrect because setting a product-level maximum sample order quantity would apply too broadly across the organization and would not satisfy the territory-specific allocation requirement. Option C is not the best answer because an Advanced Sample Limit Template at the Healthcare Provider account level controls limits by HCP/account, not the total quantity available to a territory. Therefore, Territory Product Quantity Allocation is the correct administrative configuration.

Option B is correct because Presentation Page Product is the standard Life Sciences Cloud object that links presentation content to products. Salesforce’s Life Sciences Cloud Developer Guide states that PresentationPageProduct represents the link between a presentation page and a product, and may also include a connection to product guidance or product messages. This directly matches the requirement to link Immunexis to specific presentation pages or slide content so analytics can identify which products were detailed during visits.

Salesforce’s Intelligent Content data model also includes Presentation, Presentation Linked Page, Presentation Page, Presentation Page Product, Product2, Life Science Marketable Product, Provider Visit, and visit-detailing objects. This confirms that Presentation Page Product is part of the standard content and detailing analytics architecture for Life Sciences Customer Engagement.

Option A, Presentation Linked Page, is not the best answer because it links pages within presentation structure, but it does not specifically represent the product association. Option C, Product Media Link, is not the documented standard object for connecting Life Sciences presentation pages to products. Salesforce also provides a Presentation Page Product API resource for creating or updating product and guidance associations for a presentation page, reinforcing that this is the intended object.

Therefore, the consultant should use Presentation Page Product.

Option B is correct. In Agentforce Life Sciences for Customer Engagement, the visit engagement screen in the mobile app can be customized so field users have quick access to key visit information and related records while preparing for or conducting a visit. Salesforce Help identifies the Life Sciences Cloud mobile app setup area as the place where admins configure the visit engagement page, sidebar menu, visit information fields, visit record types, quick actions, and other customer engagement mobile settings. The sidebar menu is intended to provide focused, in-context access to the most relevant information, not to replicate every possible related list from the desktop experience.

The maximum number of custom object-related lists that can be added to the sidebar is five. This limit helps preserve mobile usability and keeps the visit engagement experience streamlined for field sales reps using an iPad or mobile device during HCP or HCO interactions.

Option A is incorrect because 10 related lists would create a heavier mobile interface than the supported sidebar configuration allows. Option C is also incorrect because the product allows more than two custom object-related lists. Therefore, when configuring the visit engagement sidebar, the consultant should plan for a maximum of five custom object-related lists and prioritize the most important related records for the field workflow.

=========

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.

=========

Option B, Product Item, is correct because Salesforce defines ProductItem as the object that represents the stock of a particular product at a particular location. Salesforce Field Service developer documentation states that ProductItem represents stock of a product at a location, such as items stored in a warehouse. The Field Service Inventory Management data model also states that inventory management starts with product items, which represent stock of a particular product at a particular location.

This exactly matches the reporting requirement. The analyst needs to calculate how much “Immunexis 50mg” exists in each sales rep’s trunk. In Salesforce inventory architecture, each rep’s trunk is modeled as a Location, and the stock quantity of a given Product2 at that Location is represented by Product Item records. Reporting on Product Item allows the analyst to group by Location, filter or group by Product, and calculate quantity or value.

Option A, Location Group, is incorrect because a location group organizes or groups locations; it does not represent the actual stock quantity of a specific product at an individual location. Option C, Product Request, is also incorrect because a product request is used for requesting or moving inventory, not for representing the on-hand inventory balance. Therefore, Product Item is the primary data source for this report.

The correct answer is A because Salesforce Life Sciences Cloud provides the MIRF Share Management job specifically to manage sharing for medical inquiry records. Salesforce Help states that teams can save time, reduce manual errors, and maintain the integrity and reliability of inquiry data by using the MIRF Share Management job. Salesforce also has dedicated guidance for defining sharing settings for Medical Inquiries.

The requirement is territory-based sharing: all medical inquiries in a territory must be shared with all field sales reps in that same territory. A scheduled MIRF Share Management job is the Life Sciences-specific mechanism designed to maintain this sharing behavior for medical inquiry records. This is preferable because medical inquiry workflows often have regulated data-handling and access-control requirements, so using the purpose-built sharing-management capability is safer and more maintainable than creating generic sharing automation.

Option B is not the best answer because the described configuration is not simply a generic Territory Management setting in the Life Sciences Admin Console. The question asks specifically how to share medical inquiry records, and Salesforce points to MIRF Share Management for that purpose. Option C is also incorrect because an owner-based sharing rule on the Inquiry object would be a generic Salesforce sharing approach. It may not correctly reflect Life Sciences medical inquiry sharing logic or maintain the intended record integrity. Therefore, the consultant should schedule the MIRF Share Management job .