Full Access Salesforce Als-Con-201 Tutorials

Option C is correct because the requirement is to display a conditional indicator on the Provider Card based on the Targeted Account field. Salesforce Help states that Provider Cards consolidate account information from scattered objects and fields into a single interface. Salesforce also documents that, in the Provider Card template, admins can use data from Provider Account Territory Information, including the Targeted Account field, to show whether an account is a target account.

The correct pattern is to add an item group element to a section, include the Targeted Account field from the Provider Account Territory Info source object, and configure visibility conditions so the card shows the appropriate label. When the field value indicates that the account is targeted, the card can show “Target.” When it is not targeted, a separate condition can show “Not Target.”

Option A is not correct because applying record-level filters to show only targeted accounts would hide non-targeted accounts rather than displaying both “Target” and “Not Target” states. Option B is not the best answer because a repeater element is used for repeating sets of records; this requirement is a single account-level indicator. Therefore, item group elements with visibility conditions are the right configuration for the Provider Card indicator.

=========

The correct answer is C because Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit. Salesforce Help for Add Internal Users as Visitors states that administrators can configure the visitors feature so field reps can record internal colleagues who participate in visits and automatically share visit data with them. This directly matches the requirement to include an MSL in the scheduled remote visit and track that person’s participation.

The MSL is not the primary HCP attendee and does not need a separate visit record. Instead, the MSL is an internal participant supporting the visit. Using the standard Add Visitors (Users) to a Visit action keeps the visit record intact while documenting the MSL as a participating internal user. It also supports better compliance, collaboration, and reporting because the MSL’s involvement is recorded against the actual visit.

Option A is incorrect because creating a separate Visit record would fragment the visit history and could cause duplicate or inconsistent reporting. Option B is incomplete because emailing the meeting link may help the MSL join the session, but it does not track the MSL’s participation in the Life Sciences Visit Management data model. The correct standard action is Add Visitors (Users) to a Visit .

=========

The correct answer is C because Life Sciences Calendar can display visits where the user is not the owner but is included as an attendee or visitor. Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit so that colleagues participating in the same HCP interaction can be recorded and the visit can be shared with them. Salesforce also describes Life Sciences Calendar as a place to visualize and prioritize key activities, including visits and other events, and Trailhead explains that reps can view colleagues’ visits in shared calendars to coordinate engagement.

In this scenario, the rep bulk deleted several planned visits from their calendar. The two remaining visits are likely not visits owned and managed by the rep. Instead, they are visits owned by another user where the rep is included as an attendee. Because the calendar is configured to show attendee visits, those records continue to appear even after the rep deletes their own planned visits.

Option A is incorrect because the issue is not tied to the selected account list. Option B is plausible for some filtered-calendar behavior, but the key clue is that only some visits remain visible after bulk deletion. The standard Life Sciences explanation is that attendee visits can remain visible because they belong to a colleague and are displayed for collaboration. Therefore, the visits remain because the rep is added as an attendee.

=========

Option C is correct because Territory Product Quantity Allocations are designed to manage sample product distribution at the territory level. Salesforce Help explains that territory product quantity allocations and sample limits both help manage sample distribution to HCPs, but territory product quantity allocation is used when the business needs to allocate a defined product quantity to a territory. Salesforce’s setup guidance for Territory Product Quantity Allocations also states that Max Disbursement Limit Quantity is the maximum amount a sales rep can disburse in a given visit.

This directly matches the requirement. Cumulus Pharma wants to cap the total quantity of Immunexis 50mg available for a high-growth territory in the next quarter and also prevent reps from handing off more than 50 units in a single visit. A Territory Product Quantity Allocation record can store the territory-level allocated quantity, while Max Disbursement Limit Quantity enforces the per-visit disbursement cap.

Option A is incorrect because an Advanced Sample Limit Template focuses on account or provider-level sample limits, not the total allocation available to a territory. Option B is also incorrect because changing the Life Sciences Marketable Product globally would affect the entire organization, not just the high-growth territory. Therefore, the correct recommendation is to create a Territory Product Quantity Allocation record and set the per-visit max disbursement limit to 50.

=========