Option A is correct because Activity Plan Territory is the standard object that links an Activity Plan to territory details. Salesforce's Life Sciences Cloud Developer Guide describes ActivityPlanTerritory as representing the territory details associated with an activity plan. This exactly matches the requirement: the Immunexis Launch Activity Plan exists and contains the correct goals and measures, but it must be associated with the San Francisco North territory node so the relevant sales team can see and use it.
Salesforce's Activity Plans data model also lists Activity Plan Territory as one of the included entities, alongside Activity Plan, Territory, Provider Activity Goal, Provider Activity Goal Measure, Product, and Time Period. That confirms Activity Plan Territory is part of the standard Life Sciences Activity Plans architecture for defining, reviewing, and tracking employee activity plans, goals, and progress across territories.
Option B is not correct because "Territory Activity Plan" is not the standard object name used in the Life Sciences Cloud Activity Plans data model. Option C is also incorrect because Territory Plan Assignment relates more naturally to territory-planning assignment concepts, not linking an Activity Plan to a sales territory. Therefore, the consultant should populate Activity Plan Territory to associate the Activity Plan with the San Francisco North territory.

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

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 is correct. In Salesforce Life Sciences Cloud Remote Engagement, the standard object used for the executed video engagement details is the remote-call/video-call record. Salesforce's Life Sciences Developer Guide includes the VideoCall object for Remote Engagement and describes it as storing important information about the remote engagement, including its relationship to the associated provider visit. This aligns with the requirement to verify that the remote interaction occurred and review engagement metrics after the call concludes.
Provider Visit is related to the customer interaction and can represent the overall HCP visit context, but it is not the most precise object for the executed video-call details. The remote engagement session itself needs its own object because it can store video-specific information such as call status, timing, service details, and other remote-session metadata.
Option C, Video Log, is not the correct standard Life Sciences object name in the Salesforce documentation. "Video Log" sounds like a generic audit or logging object, but the documented Remote Engagement object is VideoCall. Since the answer options use "Remote Call" rather than "VideoCall," Remote Call is the closest and intended answer for the standard remote engagement execution record. Therefore, the consultant should use the Remote Call/VideoCall record to review the executed Remote Engagement details.
=========

Option A is correct because Salesforce Help for setting up the Inquiry record page for Medical Inquiries explicitly states that, to view timeline details for inquiries, the consultant should drag the Timeline component to the page. The requirement in the question is to expose a chronological list of key events and changes associated with the inquiry. That is exactly the purpose of the Timeline component on the Medical Inquiries record page.
Salesforce also documents Enhanced Timeline for Life Sciences Cloud, explaining that the Enhanced Timeline component shows key events relating to a person or a record. This supports the use case of giving users a consolidated, chronological view of relevant inquiry activity, rather than requiring them to inspect multiple related lists or audit records separately.
Option B is not the best answer because field history tracking and the standard History component are used for field-level audit history, not the Life Sciences Medical Inquiries timeline experience. Option C is also incorrect because adding an Inquiry History related list would expose related records, but it would not provide the configured timeline component experience described in Salesforce's Medical Inquiries setup documentation.
Therefore, the consultant must drag the Timeline component onto the Lightning record page and configure its component details for the Inquiry record page.