The correct answer is C because Salesforce Life Sciences Cloud provides the Lsc4ce.EmailQueueProcessor interface for using a third-party email service. Salesforce Help for using a third-party email service states that administrators should create a global Apex class that implements the Lsc4ce.EmailQueueProcessor interface. This interface is the supported extension point for handing off Life Sciences email operations to an external email provider instead of relying only on Salesforce's standard email sending behavior and limits.
This scenario is specifically about emails sent from the Agentforce Life Sciences mobile app. Salesforce's Field Email capability is designed to streamline compliant email creation, sending, and tracking for Life Sciences users, and the developer documentation describes LifeScienceEmail as representing a collection of sendable messages that manages creation, sending, and tracking of email communications. When an organization needs an external provider to send those emails, the custom Apex implementation must process the queued email operation and pass it to the third-party service.
Option A is incorrect because Lsc4ce.ExternalEmailHandler is not the interface identified by Salesforce for third-party email service handoff. Option B is also incorrect because Lsc4ce.MessagingService is not the documented Life Sciences email queue processing interface. Therefore, the consultant should implement Lsc4ce.EmailQueueProcessor.
=========

Option C is correct because the requirement is strict enforcement. Salesforce Help for Sample Limit Template types states that when the enforcement type is Error, distributions are blocked after limits are met. This directly matches the legal requirement in the question: the field sales rep must be prevented from submitting the visit when the disbursement quantity exceeds the allowed limit.
A controlled substance requires a hard compliance stop rather than a soft business warning. Setting the Limit Enforcement Type to Error ensures that the rep receives an error message and must correct the sample quantity before continuing. This protects the company from noncompliant disbursements and supports controlled sampling governance.
Option A is incorrect because Warning is a soft-limit behavior. A warning may alert the rep that the limit has been exceeded, but it allows the rep to proceed. That does not meet the requirement to strictly prevent the transaction. Option B is also not the best answer because "Block" is not the documented Limit Enforcement Type in the sample-limit template options shown in Salesforce's Life Sciences sample limit resources. The documented strict enforcement behavior is Error. Therefore, for controlled substances or any legally required hard stop, the consultant should configure the Sample Limit Template with Limit Enforcement Type set to Error.

Option B is correct because Salesforce Life Sciences Medical Inquiries uses workflow actions and persona/profile-based configuration to control who can perform specific inquiry actions, such as assigning and responding. Salesforce Help states that, before setting up Medical Inquiry, admins must make sure the required user profiles, licenses, and permission sets are in place. It also describes that medical science liaisons can assign and respond to inquiries, which confirms that these actions are intended to be controlled by role or persona.
Salesforce's Life Sciences workflow documentation also identifies workflow actions and workflow stages as part of the Medical Inquiry management setup. The Medical Inquiries workflow setup includes action buttons, workflow stages, stage operations, and conditions, allowing admins to expose or restrict actions based on configured roles and workflow state.
Option A is not the best answer because the requirement is not simply to grant a broad app permission; it is to ensure that only a designated persona can perform the assign and respond actions in the controlled Medical Inquiry process. Option C is incorrect because a custom formula field only affects display logic and does not enforce the standard workflow-action permission model. Formula-based visibility also creates compliance risk because it can hide buttons without truly governing the underlying operation. Therefore, the consultant should create workflow actions and associate those actions with the appropriate profiles in the Life Sciences Admin Console.
=========

Option C is correct because the issue occurs when an HCP joins a Remote Engagement call through an Experience Cloud site link. In this flow, the external HCP typically accesses the site as the Site Guest User, so the guest user needs the correct permission set to use the remote engagement experience. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that admins must assign permission sets to the guest user of the site, including Access Remote Engagement for Digital Experience. This directly matches the error in the question: the HCP reaches the site, but receives an insufficient permissions error.
Option A is incorrect because the Life Sciences Commercial Admin permission set is intended for administrative users, not the Site Guest User serving an unauthenticated Remote Engagement portal. Assigning broad admin permissions to a guest user would also be inappropriate from a security and compliance perspective. Option B is also incorrect because the requirement is not to license the HCP as a Customer Community Plus user. The scenario describes an HCP joining from a link, and the Salesforce setup guidance specifically identifies a permission-set assignment for the Site Guest User.
Therefore, the consultant should assign the Access Remote Engagement for Digital Experience permission set to the Experience Cloud Site Guest User.
=========

Option C is correct because Product Batch Item is the Salesforce Life Sciences Cloud record that connects a production batch to a specific product inventory location or user inventory context. Salesforce Help describes creating Product Batch Items for sample inventory and states that a product batch item establishes the relationship between the Product, Life Science Marketable Product, Production Batch, Product Batch Item, Location, and User. This directly matches the scenario: Cumulus Pharma needs to allocate samples from a specific production batch to a field sales rep's inventory and track remaining quantity at the batch level.
The ProductBatchItem object also includes the RemainingQuantity field, which supports the requirement to track remaining quantity by batch. Salesforce's Life Sciences Cloud Developer Guide documents ProductBatchItem and identifies RemainingQuantity as a field on the object.
Option A is incorrect because simply assigning a Production Batch to the Life Sciences Marketable Product does not allocate batch-specific stock to a rep's inventory. Visit submissions can update inventory, but the batch allocation must already be represented correctly. Option B is also incorrect because updating Quantity on Hand on Product Item only changes general product inventory at a location. It does not establish the production-batch relationship needed for batch-level tracking. Therefore, the consultant should create a Product Batch Item, associate it to the rep's Product Item, mark it Active, and enter the Remaining Quantity.
=========