Data Use Purpose is the correct answer. In Salesforce Life Sciences Cloud Consent Management, a Communication Subscription represents a specific subscription, such as a newsletter, and the consent model must also connect that subscription to the business purpose and relevant Life Sciences product. Salesforce’s Life Sciences Help documentation specifically describes creating a Data Use Purpose record to associate a Life Sciences Marketable Product with a Communication Subscription. That directly matches the scenario: “Immunology Monthly” is the Communication Subscription, and “Immunexis” is the product record that must be linked for consent capture.

Engagement Channel Type is not correct because it represents the channel through which the HCP can be contacted, such as email, SMS, or other communication methods. It defines the communication channel, not the relationship between a subscription and a marketable product. Communication Subscription Consent is also not correct because it represents an individual customer’s or HCP’s consent preference for a subscription. In other words, that record is created or updated when the HCP opts in or opts out; it is not the setup record used to link the newsletter subscription to the product. Salesforce’s Life Sciences standard object documentation also describes Communication Subscription Consent as representing a customer’s consent to a communication subscription, reinforcing that it stores the HCP’s consent outcome rather than the product-subscription configuration.

=========

The correct answer is C because reverse affiliation creation is handled by the AffiliationReciprocalHandler . Salesforce Help for Life Sciences trigger handlers identifies AffiliationReciprocalHandler as the handler that manages reciprocal affiliations. The same documentation notes behavior related to reciprocal affiliations and affiliation type handling, which directly matches the scenario where a newly created affiliation should automatically create the reverse relationship.

Affiliation Reverse Role Mapping defines how the relationship role should translate between the original and reciprocal records. For example, if an HCP is “Attending” at an HCO, the reverse relationship may show the HCO as “Employing” or otherwise related to the HCP, depending on the configured mapping. However, defining the mapping alone does not execute the automation. The trigger handler must be active so that when users create a new Affiliation record, Salesforce can generate the reciprocal Affiliation record using the configured reverse role mapping.

Option A, AffiliationUniquenessHandler , is incorrect because uniqueness logic prevents duplicate or invalid affiliation records; it does not create the reverse relationship. Option B, HardAffiliationHandler , is also incorrect because it is not the handler identified for reciprocal affiliation generation. Since the missing behavior is automatic creation of the reverse affiliation, the consultant must enable AffiliationReciprocalHandler .

The correct answer is B because the issue is the Activity Plan status transition. Salesforce describes Activity Plans as the mechanism to establish strategic plans and define activity goals for sales representatives over a specific period. The Life Sciences Activity Plans developer guidance also explains that activity plans define goals for employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

In this scenario, the plan exists and has a Start Date of today, but it is still in In Progress status. Reps cannot see the plan or their targets because the plan has not moved into the operational Active state. The specific job designed for this is Update Activity Plan Status , which evaluates the plan’s dates and moves eligible plans from In Progress to Active. Running that job makes the plan available for execution and dashboard reporting.

Option A is incorrect because Activity Plan Trigger Handler suggests trigger-based automation, not the named batch process that transitions plan status according to dates. Option C, Validate Activity Plans , is also incorrect because validation checks whether the plan setup is correct; it does not perform the status transition required by the question. The consultant should run Update Activity Plan Status in the Admin Console.

=========

The correct answer is B because the product must be enabled for discussion in the visit-detailing experience. Salesforce’s Life Sciences Visit Management developer documentation states that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples. Salesforce Trailhead also explains that Life Sciences Cloud uses product administration and product-message configuration to ensure reps only promote and discuss therapies within approved guardrails.

The scenario says the product exists in Salesforce, but it does not appear when the rep tries to add it to the Product Detailing section during a visit. That means the issue is not product creation; it is visit-discussion eligibility. The consultant should configure Product Discussion Settings in the Visit Administration area so Immunexis is available for product detailing and visit discussions.

Option A is incorrect because Territory Product Alignment Rules determine which products are aligned to territories, but the question specifically says the product must be explicitly enabled for use in visit discussions. Territory alignment alone does not guarantee the product appears in the Product Detailing search. Option C is also incorrect because Visit Record Type Mappings control record-type behavior, not whether a product can be discussed. Therefore, the correct configuration is Product Discussion Settings .

The correct answer is C because the scenario is asking for structured capture of field observations, sentiment changes, and competitive intelligence gathered during HCP interactions. Salesforce Life Sciences Cloud includes Medical Insights for capturing, analyzing, and sharing insights with medical, R & D, and commercial teams. Salesforce’s Life Sciences Cloud pharma materials describe the capability as helping teams detect, capture, analyze, and share medical insights across R & D and commercial teams, while Salesforce Help also provides setup guidance for Medical Insights in Life Sciences Cloud.

Medical Insights is the best fit because the business requirement is not merely to log a question from an HCP. It is to capture structured observations that can reveal commercial risks, such as competitor activity, sentiment shifts, or emerging concerns. These insights can then support early risk identification and mitigation planning.

Option A is incorrect because Medical Inquiries are used to capture, manage, and respond to critical questions from HCPs, including formal inquiries that may require medical information handling. Salesforce describes Medical Inquiries as a way to capture, manage, and respond to critical questions from HCPs. That is different from capturing strategic field insights. Option B is also incorrect because Account Ratings help prioritize or segment accounts, but they are not the structured feature for recording competitive intelligence and sentiment observations. Therefore, Medical Insights is the correct feature.

=========

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.

=========