Option A is correct because Life Sciences Cloud Visit Management includes an Admin Console configuration called Map Visit Types to Accounts. This configuration is designed to associate the correct Visit record type with the relevant Account type. Salesforce Life Sciences setup resources reference Visit Management Admin Console tasks, including Configure Visit Settings, Activate Trigger Handlers, Schedule Visit Jobs, and Map Visit Types to Accounts. That mapping is the appropriate configuration when a company has separate visit processes for HCOs and HCPs.
In this scenario, Cumulus Pharma already has separate Account record types and separate Visit record types. The missing configuration is the relationship between those two sets of record types. Mapping Visit Types to Accounts ensures that, when a sales rep creates a visit from an HCO account, the HCO visit process is used, and when the rep creates a visit from an HCP account, the HCP visit process is used.
Option B is not the best answer because trigger handlers enable underlying Visit Management automation, but they do not define which Visit type is associated with each Account type. Option C is also incorrect because page layouts control what users see on record pages; they do not determine the visit process or Visit record type mapping. Therefore, the consultant should configure mappings in Map Visit Types to Accounts.
=========

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

The correct answer is B because the requirement is to enable the Life Sciences visit and calendar setting that surfaces best-time recommendations for planning. Salesforce Help for Life Sciences Calendar states that users can schedule visits and other events while using best time recommendations. Salesforce also provides guidance for configuring filters to find best visit times, explaining that users can filter accounts by a healthcare professional's preferred engagement time to plan and schedule visits more effectively.
The key phrase in the question is that the feature must be enabled in Visit/Calendar settings. "Best Time Settings" is the configuration area that supports the optimization. Once enabled, the system can use historical engagement patterns and preferred engagement timing to help reps plan visits when HCPs are more likely to be available or receptive.
Option A is close in meaning, but "Set up Provider Best Time" describes the capability more generally rather than the setting in Visit/Calendar settings. Option C is incorrect because operating hours represent general availability windows for an account or location. Operating hours can help prevent scheduling at inappropriate times, but they do not provide intelligent recommendations based on historical engagement data. Therefore, the consultant should enable Best Time Settings.
=========

The correct answer is A because provider summary generation depends on the prompt template and the data supplied to that prompt. In Life Sciences Cloud account summarization, Salesforce documentation references custom prompt templates for account summarization and the account summarization workflow, while the workflow uses the Generate Provider Account Territory Summary flow as part of the summary-generation process. Salesforce also documents that this flow calls actions such as Get Object Relationship Data and Get Life Sciences Configuration Field Names, meaning the flow participates in retrieving relationship-based data, but the generated business summary still needs the prompt template to know what information to use and how to summarize it.
Updating the ARC graph alone makes additional objects and fields available in the relationship structure, but it does not automatically change the prompt's summarization behavior. To ensure the new information is used correctly, the consultant should create a new prompt template version, update the input dataset so the new fields are included, revise the summarization instructions so the AI knows how to use them, and then activate that version. This aligns with Salesforce's guidance that prompt-based generation relies on the configured prompt and its grounding/input data. Option B is incomplete because changing only the flow does not update the prompt's instructions. Option C is also incorrect because batch-job configuration controls bulk execution, not the actual summarization logic.