Als-Con-201 Salesforce Certified Agentforce Life Sciences Consultant Questions and Answers

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 the requirement is persona-specific. Cumulus Pharma does not want the two additional custom objects to influence provider summaries for all users; the new insights and market intelligence must be used only when the provider summary is generated for the Key Account Manager profile. Salesforce Life Sciences Account Summarization is designed to generate contextual provider summaries from the latest changes, interactions, and insights related to a healthcare provider, and its configuration includes profile-specific setup so different personas can receive summaries grounded in the information relevant to their role.

Creating mapping records in the Provider Summary Profile Mappings tab associates the relevant summary data with the KAM profile. This is the most precise configuration because it controls which profile receives access to the additional summary context. Option A is not the best answer because creating a cross-object graph and assigning it directly to a profile is not the described administrative mechanism for persona-based provider summary control. Option C is also too broad: updating the Provider Summary Objects mapping may make the custom objects available to the summarization framework, but the key requirement is limiting usage to the new KAM persona. Profile mapping is what ensures the new objects are applied only for that persona’s provider summary generation.

=========

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.”

The correct answer is B because Salesforce Life Sciences calendar configuration represents General Event calendar entries using the standard Event object. Salesforce Help for configuring calendar events in Life Sciences Cloud lists calendar event types and shows General Event with the object/API reference Event . This means that the standard object used to store general, non-customer calendar activities is Event , even though the user-facing event type is called General Event.

In the scenario, the activities are internal items such as sales training or team lunch. They are not visits, HCP interactions, HCO engagements, or account-specific activities. They still need to appear on the rep’s calendar for capacity planning. Therefore, they should be logged as general calendar events on the standard Event object.

Option A, General Event , is tempting because it describes the business meaning of the schedule item. However, the question asks which object should be used. Salesforce’s configuration identifies the object as Event . Option C, Time Off Territory , is incorrect because that object is used to log and manage time away from assigned territories, such as PTO or territory unavailability. A team lunch or sales training is not necessarily time away from territory and is better represented as a general calendar event. Therefore, the consultant should use the Event object.

=========

Option A is correct because routines are the Life Sciences Cloud capability intended for reusable visit schedules and recurring route patterns. Salesforce Help describes Customer Engagement features as including the ability to optimize daily schedules by showing key events and applying predefined routines on the calendar. This directly matches the requirement: field sales reps repeatedly visit the same groups of accounts across weekly routes or multi-day coverage patterns and want to reuse those planned schedules instead of rebuilding visits every time.

Routines support practical field planning because a rep can save a predefined pattern of planned visits and apply it later when the same route or schedule is needed. This is different from simply grouping accounts.

Option B is not the best answer because account lists help reps organize, filter, and target groups of accounts, but they do not by themselves preserve a reusable multi-day visit schedule. Account lists can help with planning, but they are not the direct solution for saving and reapplying a planned route. Option C is also incorrect because Activity Plans define strategic goals, targets, and activity expectations across a period. They align engagement activity to business objectives, but they are not designed to save and reapply recurring visit schedules. Therefore, the consultant should recommend creating a routine that saves the predefined set of visits and applying that routine as needed.

The correct answer is A because the subscription and channel must be connected before reps can capture consent for that channel. Salesforce’s Life Sciences Consent Management model includes Communication Subscription , Engagement Channel Type , and Communication Subscription Channel Type as standard entities for capturing and managing HCP consent and communication preferences. The Communication Subscription Channel Type object acts as the junction between a subscription topic, such as “Immunexis KOL Webinar Series,” and a channel, such as Email.

In the scenario, the subscription is visible, which confirms that the Communication Subscription record exists and is available in the mobile consent experience. However, Email is not selectable because the subscription has not been associated with the Email engagement channel. Creating the Communication Subscription Channel Type record resolves this gap by telling the system that this subscription can be consented to through the Email channel.

Option B is incorrect because Communication Subscription Consent records represent an individual HCP’s consent decision, such as opt-in or opt-out. They do not control whether a channel is available for a subscription. The channel must first be configured as valid for the subscription. After that, reps can capture the HCP’s opt-in preference during the visit. Therefore, the consultant should create the Communication Subscription Channel Type junction record.

=========

The correct answer is A because Salesforce Life Sciences Sample Inventory Management includes a process for fixing unresolved product disbursements. Salesforce Help for managing samples references Fix Unresolved Product Disbursements , and the same Sample Inventory Management area describes inventory operations such as transfers, returns, shipments, assigned batches, and product disbursements as part of the sample lifecycle.

The issue occurs because the rep physically received samples and handed them to an HCP before formally acknowledging the inventory in the system. To preserve inventory integrity, Salesforce cannot simply reduce inventory counts as if the stock were already confirmed in the rep’s available inventory. Instead, the system flags the Product Disbursement as unresolved. The rep must first acknowledge the inventory so the system recognizes the received stock, and then use the Resolve Disbursement quick action to complete the reconciliation and finalize the inventory count updates.

Option B is incorrect because the process does not require an admin to manually override an unresolved status in org-wide settings. This is an operational correction handled by the rep through the sample inventory workflow. Option C is also incorrect because forcing a Manual Adjustment would bypass the intended reconciliation process and could weaken auditability. The proper Life Sciences process is to acknowledge the inventory and then resolve the disbursement using the quick action.

=========

Option B is correct because Salesforce Life Sciences Cloud requires a specific API-name prefix for custom Lightning web components that should render as inline components in the Life Sciences mobile app. Salesforce Help for creating and adding an LWC as an inline component on a record page states that admins must create a custom mobile-ready LWC and add lscMobileInline_ as the prefix for the component’s API name. This exact prefix identifies the component as compatible with the Life Sciences mobile inline rendering framework.

This directly matches the issue in the scenario. The component exists and was added to the Account record page, but it does not render correctly as an inline component in the mobile app. The missing configuration is not the page placement itself, but the required naming convention that allows the Life Sciences mobile app to recognize and render the LWC inline.

Option A, lsc_mobile_, is incorrect because it is not the documented prefix for inline mobile LWCs. Option C, mobileInline_, is also incorrect because it omits the Life Sciences-specific lsc prefix and does not match the Salesforce Help requirement. Therefore, the consultant should rename or recreate the LWC API name using the lscMobileInline_ prefix so it functions correctly as an inline component in the Agentforce Life Sciences mobile app.

=========

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.

=========

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 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 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 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.

=========

The correct answer is A because Remote Engagement email notifications depend on email templates configured for the relevant automated email invitation context/action. Salesforce Help for uploading and creating email templates in Life Sciences Cloud includes configuration fields for automated email invitation context and action. For a rescheduled or updated virtual visit, the email template must be configured so the automated email invitation action corresponds to the update event.

The scenario asks specifically about email notifications when virtual visits are rescheduled. A reschedule is an update to an existing visit invitation, not a new invitation and not a cancellation. Therefore, the consultant must ensure there is an email template whose Automated Email Invitation Action is set to Update . That template is then used by the Remote Engagement process when the visit details change and the HCP needs to receive the revised meeting information.

Option B is incorrect because configuring a handler around a visit status value such as “Rescheduled” is not the core template configuration required for the notification content and action. Option C may sound plausible because trigger handlers often support automation, but the question asks which configuration is required to send email notifications for rescheduled virtual visits. The action-specific email template is the necessary configuration. Therefore, the consultant should use an Email Template with Automated Email Invitation Action set to Update .

=========

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 .

Option C is correct because Life Sciences Cloud separates the overall visit activity from provider-specific visit details. In the Life Sciences Cloud data model, the Visit object tracks information related to a field representative’s visit to a healthcare provider and is used for Customer Engagement. Salesforce’s ProviderVisit object represents the details of a field user’s visit to a healthcare provider. The Customer Engagement data model also explains that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples.

For a group visit such as a “Lunch and Learn” with three HCPs, the overall event is represented by the parent Visit record. Each attendee requires their own provider-specific visit detail record because each HCP may have different product discussions, messages, samples, signatures, or follow-up activities. Therefore, the system creates one parent Visit and separate child Provider Visit records for each HCP attendee.

Option A is incorrect because a multi-select lookup field is not the correct Life Sciences Cloud visit data model pattern. Option B is also not correct because it implies individual parent-level Visit records for every attendee, which would duplicate the overall group interaction. The correct structure is one parent Visit for the group interaction and three child Provider Visit records, one for each Healthcare Provider attendee.

Option C is correct because Life Sciences mobile offline behavior depends on metadata cache for page layouts, metadata definitions, and offline user interface configuration. Salesforce Help for customizing the Life Sciences Cloud mobile app states that the generated metadata cache includes object schemas and metadata definitions that the mobile app stores locally to support both online and offline modes. Salesforce Help for setting up the Life Sciences Cloud mobile app also identifies object metadata cache settings, application settings, profile-based configurations, and UI customizations as part of the mobile setup process.

This directly matches the issue. The reps completed a data sync, but data sync alone does not necessarily refresh page layout metadata or translation changes used by the offline mobile app. Since the consultant changed Account page layout configuration and translation files, the correct action is to regenerate the metadata cache for the relevant profiles so offline users receive the updated metadata package.

Option A is incorrect because resetting the Sync Processor job status addresses synchronization processing, not metadata or translation availability. Option B is also incorrect because Mobile Offline Briefcase filters control which records or data are available offline; they do not publish updated page layouts or translated labels. Therefore, the consultant should generate a new metadata cache for the affected profiles.

The correct answer is A because the described requirement matches a Provider Plan Cycle . In Salesforce Life Sciences Cloud, Activity Plans are used to organize and guide planned field activity. Salesforce Help specifically states that when creating Activity Plans, the consultant selects Provider Plan Cycle for the Usage Type. This usage type supports a planned engagement cycle where field sales reps work against defined goals for providers during a specific period.

The wording in the scenario is important: the goals are defined by the home office and executed by field sales reps during a strategic cycle. That is not the same as a broader account planning process or a standalone territory objective. A Provider Plan Cycle is designed for provider-focused execution, where commercial strategy is translated into actionable field goals for HCP engagement.

Option B, Account Plan , is incorrect because account plans are generally used for broader key account management and strategic relationship planning, especially for major accounts or account hierarchies. It does not specifically represent the activity-plan usage type for home-office-defined provider engagement cycles. Option C, Territory Objective , is also incorrect because a territory objective represents a goal or target at the territory level, but it is not the Usage Type required when creating the Activity Plan record for provider cycle execution. Therefore, the consultant should select Provider Plan Cycle .

=========

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.

=========

The correct answer is A because Next Best Message uses product-message scoring data at the territory-account-product-message level. Salesforce’s Life Sciences Cloud Developer Guide states that Next Best Message provides tailored and relevant messages for each product associated with an account. Salesforce also documents the related scoring object and describes the calculation agent used to calculate the territory account product message score based on various metrics.

The scenario says Cumulus Pharma already has a custom predictive model outside Salesforce. The goal is not to build the model inside Salesforce, but to surface the model’s results to reps through the standard Next Best Message capability. Therefore, the external scores and rankings should be loaded into the object that stores ranked product-message recommendations for accounts in territories: Territory Account Product Message Score .

Option B, Visit Recommendation , is not the best answer because the requirement is specifically about product messages for HCPs, not general recommendations tied to a visit. Option C, Score Explainability Info , may support interpretation or explanation of scoring, but it is not the primary object used to load the external product-message score and ranking. To use Next Best Message with external model outputs, the consultant should load the results into Territory Account Product Message Score .

=========

Option B, Action Plan Template Assignment, is correct. In Salesforce Life Sciences Cloud Key Account Management, strategic planning uses goal definitions and action plan templates to standardize account-planning execution. A Goal Definition represents the reusable strategic goal blueprint, such as “Secure Formulary Access.” An Action Plan Template defines the repeatable tactical tasks that should be generated when that goal is added to an account plan. The object that connects these two pieces is ActionPlanTemplateAssignment. Salesforce’s Life Sciences Cloud Developer Guide describes ActionPlanTemplateAssignment as the object to which the action plan template is associated, including examples such as a problem definition, goal definition, or care plan template. This directly matches the scenario: the action plan template must be associated with the goal definition so that importing the predefined strategic goal can generate the related tactical action plan.

Option A is not correct because “Action Plan Template Goal” is not the standard object identified in the Salesforce Life Sciences Cloud data model for this association. Option C is also incorrect because an Action Plan Template Participant would relate to participants, not the relationship between a goal definition and an action plan template. Salesforce’s Key Account Management Account Plan data model also includes Action Plan Template Assignment, Action Plan Template, Action Plan Template Item, and Goal Definition as part of the standard account-planning architecture.

Therefore, the correct object for linking the tactical action plan template to the reusable strategic goal definition is Action Plan Template Assignment.

=========

Option C is the best answer because the requirement is specifically to activate Activity Plans based on the time period. In Life Sciences Cloud, Activity Plans define activity goals for sales representatives over a specific period, including goals, measures, territories, accounts, and activity targets. Salesforce Help describes Activity Plans as a way to transform provider interaction strategies into actionable tasks with defined goals and targets for field representatives.

When the key requirement is status activation based on the plan’s effective time period, the relevant job is the Update Activity Plan Status batch job. The wording of this option directly aligns with the requested outcome: activate the plans according to time period. Validate Activity Plans is related to validation and activation readiness. Salesforce Help notes that the Validate Activity Plans batch job is used in the activity-plan approval and activation process, but the question does not ask merely to validate plans or activate approved provider activity goals.

Process Provider Activity Plans is also not the best answer because it is more closely associated with processing provider-level plan records and goal calculations after plans are configured. The question asks which step completes configuration and activates plans based on time period, making the status update job the precise fit. Therefore, the consultant should schedule or immediately trigger the Update Activity Plan Status batch job.

=========

Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.

The key word in the question is “collaborate.” Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because “availability” typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user’s territories, and the named handler that most directly supports that requirement is the sharing handler.

Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.

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.

=========

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.

Option C is correct because Salesforce Help identifies “Access Life Sciences Customer Engagement Agentforce” as the permission required for Life Sciences Customer Engagement Agentforce capabilities. In the Salesforce Help reference for the Life Sciences “Generate Healthcare Provider Summary” action, Salesforce lists the required access as Access Life Sciences Customer Engagement Agentforce. It also notes that, to run flows associated with agent actions, users need the Run Flows app permission or access to the individual flows.

This directly matches the scenario. The Life Sciences Field Sales agent template has already been configured and activated, but the field sales rep cannot use the agent-generated HCP summary capability. That means the issue is not the existence of the agent or the template; it is the user’s permission to access the Life Sciences Customer Engagement Agentforce features. Salesforce’s Account Summarization permissions documentation also references Access Life Sciences Customer Engagement Agentforce as part of the permission setup for account summarization, alongside standard Life Sciences user permission sets.

Option A, Life Sciences Commercial User, is not specific enough to grant access to these Agentforce capabilities. Option B, Agentforce Service Agent User, relates to Agentforce service use cases and is not the Life Sciences Customer Engagement permission named in the documentation. Therefore, the consultant should assign Access Life Sciences Customer Engagement Agentforce.

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.

=========

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 .

=========

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.

=========

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 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 A because Remote Engagement video traffic requires Twilio endpoints to be trusted by the Salesforce org. Salesforce Help for setting up Twilio for Remote Engagement states that participants can connect to video calls by adding Twilio WSS endpoints as Trusted URLs in the Salesforce org. This is specifically required for secure video-call connectivity, which directly matches the symptom in the question: the Twilio credentials and Experience Cloud site are configured, but the video media fails to load.

Twilio External Credentials handle authentication and connection details for the integration, and the Experience Cloud site provides the HCP-facing remote engagement experience. However, browser and Salesforce security controls still need to allow the required Twilio WebSocket Secure traffic. If those URLs are not trusted, the page can load while the actual audio/video media connection fails.

Option B is incorrect because assigning a field-sales permission set to the Site Guest User would be inappropriate and overly permissive. The issue is media connectivity, not guest-user access to sales functions. Option C is also incorrect because a trigger handler for remote-session invitations would relate to record automation or invitation behavior, not secure loading of Twilio video traffic. Therefore, the consultant must add Twilio’s required endpoints to Trusted URLs .

=========

Option B is correct because the Healthcare Provider object contains provider-specific Life Sciences attributes, including whether the provider is designated as a speaker for engagement. Salesforce’s Life Sciences Cloud Developer Guide for the HealthcareProvider object states that the object and its fields are used by Account Management and Segmentation, and the search result for the same Salesforce object documentation identifies a field that indicates whether the provider is designated as a speaker for engagement, with a default value of false. This directly matches the question’s requirement to identify whether a physician is flagged as a speaker.

Option A, Board Certification, is incorrect because board certification stores credential or certification information about a provider. It may help qualify the provider professionally, but it does not represent the commercial engagement flag that identifies whether the provider is a speaker. Option C, Person Account, is also not the best answer. In Life Sciences Cloud, physicians are commonly represented through Person Accounts, but the speaker designation is stored in the Healthcare Provider data model, not as a generic Person Account-only attribute.

Therefore, when the consultant needs to identify whether a physician is flagged as a speaker in Agentforce Life Sciences for Customer Engagement, the correct object to reference is Healthcare Provider .

=========