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

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.

=========

Option C is correct because an Ad Hoc inventory count assessment is used for an unscheduled inventory check, and Salesforce Life Sciences Sample Inventory Management supports discrepancy adjustments when the counted quantity differs from the system quantity. Salesforce Help states that when a discrepancy is recorded in an inventory count, Sample Inventory Management adjusts the system count positively or negatively to match the actual count. In this scenario, the rep physically counts 95 units while the system shows 100, so the compliant process is to submit the count and let the system create the adjustment transaction for the five-unit negative discrepancy.

Salesforce Help also describes Inventory Count Assessment as the object that captures the overview of the count, including where the assessment occurs and the assessment type. This supports using an inventory count assessment rather than manually changing inventory balances.

Option A is not correct because the missing units were not returned to the distribution center; creating a return would misrepresent the physical inventory event. Option B is also incorrect because an Initial inventory count is used for establishing an initial count, not for reconciling an unscheduled discrepancy after inventory already exists. Therefore, the correct compliant action is to submit an Ad Hoc inventory count assessment and let the system generate the adjustment transaction.

=========

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.

=========

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.

The correct answer is C because aligned account lists in Agentforce Life Sciences for Customer Engagement are configured through account list settings, where the consultant defines how the list appears to users in the mobile experience. Salesforce describes account management features in Life Sciences Cloud as enabling users to organize, prioritize, and focus on accounts through lists and filters in the Customer Engagement app. The account list configuration controls which fields appear to reps so they can quickly understand account context without opening every account record.

In this scenario, the business wants field sales reps to see the most relevant account information directly in the aligned account list. After creating the account list, the consultant should configure it as the Default list type and select up to four visible fields as columns. This gives reps a concise, mobile-friendly view of the most important account details.

Option A is incorrect because configuring the Search list affects search-result display behavior, not the aligned account list columns. It also refers to up to five account fields, which does not match the aligned account list column configuration described in the question. Option B is incorrect because assigning ownership to field sales reps does not define the visible columns in the list. Column configuration is an admin setup activity, not something resolved by record ownership. Therefore, the consultant should set the list type to Default and configure up to four visible fields.

=========

Option A is correct because Salesforce Life Sciences Account Summarization uses field history tracking to include the latest changes for configured fields. Salesforce Help states that, to get summaries of the latest changes in a record, history tracking must be enabled for the fields configured in the Account Summarization template. This directly matches the issue: the summaries include related data, but recent updates to specific HCP Account fields are missing. The consultant must enable history tracking for the relevant fields so Agentforce can use those tracked changes when generating the account summary.

Feed tracking is not the best answer because Chatter feed tracking is primarily used to publish field changes to the record feed for collaboration and visibility. It does not satisfy the specific Account Summarization requirement documented by Salesforce. Field Audit Trail is also not correct for this scenario. Field Audit Trail is a Salesforce Shield capability used for long-term retention and audit-policy management of field history data, but the Account Summarization setup requirement is specifically field history tracking for the fields included in the template. Salesforce’s Account Summarization Data Setup documentation also confirms that the Provider Summary Lightning App Builder component can be configured to enable history tracking for fields included in the information summary.

Therefore, the consultant should enable history tracking for the Account fields configured in the Account Summarization template.

=========