Als-Con-201 Exam Dumps - Salesforce Certified Agentforce Life Sciences Consultant

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.

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 B because the issue is the Activity Plan status transition. Salesforce describes Activity Plans as the mechanism to establish strategic plans and define activity goals for sales representatives over a specific period. The Life Sciences Activity Plans developer guidance also explains that activity plans define goals for employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

In this scenario, the plan exists and has a Start Date of today, but it is still in In Progress status. Reps cannot see the plan or their targets because the plan has not moved into the operational Active state. The specific job designed for this is Update Activity Plan Status , which evaluates the plan’s dates and moves eligible plans from In Progress to Active. Running that job makes the plan available for execution and dashboard reporting.

Option A is incorrect because Activity Plan Trigger Handler suggests trigger-based automation, not the named batch process that transitions plan status according to dates. Option C, Validate Activity Plans , is also incorrect because validation checks whether the plan setup is correct; it does not perform the status transition required by the question. The consultant should run Update Activity Plan Status in the Admin Console.

=========

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.

=========

The correct answer is C because reverse affiliation creation is handled by the AffiliationReciprocalHandler . Salesforce Help for Life Sciences trigger handlers identifies AffiliationReciprocalHandler as the handler that manages reciprocal affiliations. The same documentation notes behavior related to reciprocal affiliations and affiliation type handling, which directly matches the scenario where a newly created affiliation should automatically create the reverse relationship.

Affiliation Reverse Role Mapping defines how the relationship role should translate between the original and reciprocal records. For example, if an HCP is “Attending” at an HCO, the reverse relationship may show the HCO as “Employing” or otherwise related to the HCP, depending on the configured mapping. However, defining the mapping alone does not execute the automation. The trigger handler must be active so that when users create a new Affiliation record, Salesforce can generate the reciprocal Affiliation record using the configured reverse role mapping.

Option A, AffiliationUniquenessHandler , is incorrect because uniqueness logic prevents duplicate or invalid affiliation records; it does not create the reverse relationship. Option B, HardAffiliationHandler , is also incorrect because it is not the handler identified for reciprocal affiliation generation. Since the missing behavior is automatic creation of the reverse affiliation, the consultant must enable AffiliationReciprocalHandler .

Option B is correct because Life Sciences Cloud for Customer Engagement uses Life Sciences-specific Next Best components for the mobile and account-profile experience. Salesforce’s Life Sciences Next Best documentation explains that Next Best Action suggests timely actions such as visits and emails, and the Life Sciences Customer Engagement data model includes Life Sciences-specific recommendation objects such as Territory Account Recommended Action, Territory Account Product Message Score, and Territory Account Score. These are not the same as the generic Einstein Next Best Action component and strategy experience.

The question states that the recommendation data is already loaded and synced to mobile. That removes the most likely data-load or synchronization issue. If the data exists but the component is not visible on the account profile, the issue is most likely the wrong component placement. The page must use the Life Sciences Next Best Action component that is designed to render Life Sciences recommendations in the Life Sciences mobile app.

Option A is not the best answer because inactive strategy logic would generally prevent recommendations from being generated or returned, but the scenario confirms the recommendation data is present. Option C is also less likely because a permission problem would typically prevent access to the recommendation records or data, not specifically indicate that the component itself was configured incorrectly. Therefore, the consultant should replace the generic Einstein Next Best Action component with the Life Sciences Next Best Action component.

=========

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 Today’s Pace is tied to the Activity Plan’s calculation behavior, not the home page component itself. Salesforce describes Activity Plans as a way to establish a strategic activity plan and define activity goals for sales representatives over a specific period. Salesforce’s Life Sciences Activity Plans developer guidance also describes Activity Plans as allowing administrators to define goals for specific employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

When the business wants Today’s Pace calculated based on working days, that logic should be defined where the activity plan is created and governed. Selecting Working Days in the Today’s Pace Calculation Type field ensures the pacing metric uses working-day logic for the plan instead of simply counting all calendar days. This is the correct place to configure the calculation because Today’s Pace reflects plan progress against the plan timeline.

Option B is incorrect because editing the home page component only controls presentation. A component can display the metric, but it should not be the source of the calculation rules for the underlying Activity Plan. Option C is also not the best answer because the requirement is not a broad global enablement setting; it asks how to calculate Today’s Pace for the relevant Activity Plan. Therefore, the consultant should configure the calculation type directly on the Activity Plan by selecting Working Days .