Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep’s targets.

Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.

Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.

=========

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 the symptom is specifically about Case ownership not changing after a Medical Inquiry is submitted. Salesforce Help for Medical Inquiries shows that the inquiry workflow uses Case status values such as Draft , Signed , Submitted , and Assigned , and Life Sciences Cloud also provides Trigger Handler Administration for configuring Life Sciences trigger handlers, including trigger handlers related to Case objects.

In the scenario, the status update is working correctly: the signed inquiry becomes Submitted . That means the submission process itself is functioning. The failure is isolated to ownership routing: the Case remains owned by the field sales rep instead of being routed to the Medical Science Liaison team or queue. Based on the available options, CaseChangeOwnershipHandler is the handler that directly corresponds to changing ownership on the Case record.

Option B, MSLInquirySubmissionHandler , sounds related to Medical Inquiry submission, but the submission status already updates correctly, so that is unlikely to be the inactive piece. Option C, CaseMSLQueueHandler , sounds like queue routing, but the Salesforce-style handler name that most directly describes the failed behavior is CaseChangeOwnershipHandler . Since the issue is ownership transfer after submission, the inactive trigger handler is CaseChangeOwnershipHandler .

=========

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 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 A because the requirement is for a single embedded, interactive graph that visualizes multiple relationship types around an HCP. Salesforce describes Actionable Relationship Center (ARC) as a capability for viewing relationships among people and businesses in an interactive graph. Salesforce also describes ARC as supporting entity hierarchy and entity relationship visualization, and Life Sciences provider-card guidance references account-related object relationships in an ARC graph.

This scenario includes more than a simple parent-child hierarchy. The HCP has an employment relationship with one hospital, affiliation relationships with two additional hospitals, and a Key Opinion Leader role for a research study. ARC is designed for this type of multi-object, multi-relationship visualization. It allows users to see related entities in context and navigate through connected records from a graph-based interface rather than moving through several related lists.

Option B, Einstein Relationship Insights , is incorrect because it is not the Life Sciences page component used to display a configured relationship graph for HCP-related records. Option C, Account Hierarchy Visualization , is also too limited because account hierarchy is generally used for hierarchical account structures, not a broader relationship network involving employment, affiliations, KOL status, and research-study connections. Since the requirement calls for an interactive relationship graph embedded on the record page, the consultant should implement Actionable Relationship Center .

=========

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 .

=========