Practice Free Als-Con-201 Salesforce Certified Agentforce Life Sciences Consultant Exam Questions Answers With Explanation

Option C is correct because Salesforce Help identifies “Access Life Sciences Customer Engagement Agentforce” as the permission required for Life Sciences Customer Engagement Agentforce capabilities. In the Salesforce Help reference for the Life Sciences “Generate Healthcare Provider Summary” action, Salesforce lists the required access as Access Life Sciences Customer Engagement Agentforce. It also notes that, to run flows associated with agent actions, users need the Run Flows app permission or access to the individual flows.

This directly matches the scenario. The Life Sciences Field Sales agent template has already been configured and activated, but the field sales rep cannot use the agent-generated HCP summary capability. That means the issue is not the existence of the agent or the template; it is the user’s permission to access the Life Sciences Customer Engagement Agentforce features. Salesforce’s Account Summarization permissions documentation also references Access Life Sciences Customer Engagement Agentforce as part of the permission setup for account summarization, alongside standard Life Sciences user permission sets.

Option A, Life Sciences Commercial User, is not specific enough to grant access to these Agentforce capabilities. Option B, Agentforce Service Agent User, relates to Agentforce service use cases and is not the Life Sciences Customer Engagement permission named in the documentation. Therefore, the consultant should assign Access Life Sciences Customer Engagement Agentforce.

Option B is correct because Life Sciences Cloud for Customer Engagement uses Life Sciences-specific Next Best components for the mobile and account-profile experience. Salesforce’s Life Sciences Next Best documentation explains that Next Best Action suggests timely actions such as visits and emails, and the Life Sciences Customer Engagement data model includes Life Sciences-specific recommendation objects such as Territory Account Recommended Action, Territory Account Product Message Score, and Territory Account Score. These are not the same as the generic Einstein Next Best Action component and strategy experience.

The question states that the recommendation data is already loaded and synced to mobile. That removes the most likely data-load or synchronization issue. If the data exists but the component is not visible on the account profile, the issue is most likely the wrong component placement. The page must use the Life Sciences Next Best Action component that is designed to render Life Sciences recommendations in the Life Sciences mobile app.

Option A is not the best answer because inactive strategy logic would generally prevent recommendations from being generated or returned, but the scenario confirms the recommendation data is present. Option C is also less likely because a permission problem would typically prevent access to the recommendation records or data, not specifically indicate that the component itself was configured incorrectly. Therefore, the consultant should replace the generic Einstein Next Best Action component with the Life Sciences Next Best Action component.

=========

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, Product Item, is correct because Salesforce defines ProductItem as the object that represents the stock of a particular product at a particular location. Salesforce Field Service developer documentation states that ProductItem represents stock of a product at a location, such as items stored in a warehouse. The Field Service Inventory Management data model also states that inventory management starts with product items, which represent stock of a particular product at a particular location.

This exactly matches the reporting requirement. The analyst needs to calculate how much “Immunexis 50mg” exists in each sales rep’s trunk. In Salesforce inventory architecture, each rep’s trunk is modeled as a Location, and the stock quantity of a given Product2 at that Location is represented by Product Item records. Reporting on Product Item allows the analyst to group by Location, filter or group by Product, and calculate quantity or value.

Option A, Location Group, is incorrect because a location group organizes or groups locations; it does not represent the actual stock quantity of a specific product at an individual location. Option C, Product Request, is also incorrect because a product request is used for requesting or moving inventory, not for representing the on-hand inventory balance. Therefore, Product Item is the primary data source for this report.

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 .

Option B is correct because Communication Subscription Channel Type is the junction record that links a Communication Subscription to an Engagement Channel Type. Salesforce’s Life Sciences Consent Management data model includes Communication Subscription, Communication Subscription Channel Type, Communication Subscription Consent, Data Use Purpose, Engagement Channel Type, and related consent objects. This confirms that subscription-channel availability is modeled through Communication Subscription Channel Type, not only through the subscription or channel records separately.

Salesforce’s Communication Subscription objects documentation states that Communication Subscription Channel Type specifies the engagement channel that can be used to contact the customer for a communication subscription. The Salesforce object reference also identifies fields on Communication Subscription Channel Type such as EngagementChannelTypeId, confirming that this object connects the subscription to the channel.

Option A is incorrect because there is no indication that a generic “Allow Email Channel” checkbox controls this relationship. Option C is also incorrect because Communication Subscription Consent stores an individual HCP’s consent preference after the channel-subscription combination exists. It does not make the Email channel selectable for the subscription. Therefore, the consultant must create a Communication Subscription Channel Type record linking “Immunexis KOL Webinar Series” to the Email Engagement Channel Type.

The correct answer is B because Salesforce Life Sciences Cloud for Customer Engagement includes country-specific sample limit templates by default. Salesforce Help states that Life Sciences Cloud includes a generic sample limit template and several country-specific templates by default. These templates are intended to support sample-limit compliance where rules vary by country, including situations where statutory limits must be consistently applied without requiring administrators to rebuild complex legal rules from scratch.

In this scenario, Germany has strict legal limits on sample quantities that must apply to all HCPs. A default country-specific template is the best fit because it is designed to represent country-level sample compliance requirements in a reusable configuration. This approach reduces administrative maintenance, improves consistency, and helps ensure the sampling program follows local legal constraints.

Option A is incorrect because adding a new sample limit to custom metadata would require the admin or implementation team to manually maintain rule logic, which the requirement explicitly wants to avoid. Option C is also not the best answer because manually creating a sample limit rule in the Admin Console may work for custom business policies, but it is less appropriate when Salesforce provides a default country-specific template for statutory country rules. Therefore, the consultant should use the Default Country-Specific Template for Germany.

=========

The correct answer is B because Salesforce Life Sciences calendar configuration represents General Event calendar entries using the standard Event object. Salesforce Help for configuring calendar events in Life Sciences Cloud lists calendar event types and shows General Event with the object/API reference Event . This means that the standard object used to store general, non-customer calendar activities is Event , even though the user-facing event type is called General Event.

In the scenario, the activities are internal items such as sales training or team lunch. They are not visits, HCP interactions, HCO engagements, or account-specific activities. They still need to appear on the rep’s calendar for capacity planning. Therefore, they should be logged as general calendar events on the standard Event object.

Option A, General Event , is tempting because it describes the business meaning of the schedule item. However, the question asks which object should be used. Salesforce’s configuration identifies the object as Event . Option C, Time Off Territory , is incorrect because that object is used to log and manage time away from assigned territories, such as PTO or territory unavailability. A team lunch or sales training is not necessarily time away from territory and is better represented as a general calendar event. Therefore, the consultant should use the Event object.

=========

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 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 B because the deadlines and review windows for activity-plan adjustments are configured on the Activity Plan record, specifically in the review-related configuration. Salesforce Help for creating Activity Plans references fields such as Reviewer Plan Adjustment Start Date and Reviewer Plan Adjustment End Date , which define the date range in which the manager can review adjustment requests.

The scenario describes a plan-level governance requirement: field sales reps must submit proposed visit targets by a specific deadline, and adjustments above allowed thresholds must be reviewed. This belongs to the Activity Plan configuration because the plan defines the cycle, timing, targets, review process, and adjustment behavior for the territory or provider planning period. Configuring the Review Details section ensures that the plan controls when reps can submit changes and when managers can review them.

Option A is incorrect because Global Calculation Settings for a Provider Activity Measure Type would relate to how measures or calculations are evaluated, not the submission and manager-review deadline for a specific Activity Plan. Option C is also incorrect because a Goal Definition represents a reusable planning objective, but it does not control the operational review dates and adjustment thresholds for a specific West Coast Activity Plan. Therefore, the consultant should configure the deadlines and adjustment limits on the Activity Plan record within the Review Details section .

=========

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.

=========

Option C is correct because Sample Inventory Management includes standard lock behavior for inventory operations based on status. The requirement is to prevent edits after a field sales rep submits inventory records such as transfers and adjustments. Salesforce Help references trigger handlers for Product Batch Item and Product Transfer objects, including ProductTransferLockHandler, which prevents modifications to Product Transfer records when the associated inventory operation is locked. This supports the standard Life Sciences pattern: the Inventory Operation reaches a locked status, and related inventory transaction records can no longer be modified.

Adding finalized status values to the Inventory Operation Locked Status list in Sample Inventory Settings is the appropriate administrative configuration because it tells the system which statuses should make the inventory operation locked. Once the record enters one of those statuses, the standard inventory lock handlers can enforce the restriction.

Option A is not the best answer because a restriction rule controls record visibility, not the complete GxP-style lock behavior for submitted inventory operations and related records. Option B is also not the best answer because a generic flow lock template is not the documented Sample Inventory Settings mechanism for locking inventory operations. Therefore, the consultant should configure the Inventory Operation Locked Status list with the finalized statuses that must prevent further edits.

=========

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 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 requirement is to send Medical Insights to an external system without delay , which points to an event-driven integration pattern. Salesforce’s Life Sciences Cloud Developer Guide defines MedicalInsight as important information observed or heard through outlets such as meetings, calls, or research and used to inform strategy or follow-up. For near-real-time downstream processing, the appropriate Life Sciences configuration is to publish the standard Medical Insight platform event by activating the handler designed for that purpose.

Activating PublishMedicalInsightEventHandler allows newly captured Medical Insight data to be published as a MedicalInsightEvent platform event. Platform events are the correct Salesforce pattern when an external system needs to subscribe and react quickly as records are created or changed. This avoids waiting for scheduled jobs, exports, or manual data transfers, and it supports timely intelligence generation from field-captured insights.

Option A is incorrect because creating a custom platform event is unnecessary when the Life Sciences feature provides a standard MedicalInsightEvent mechanism. Custom events add avoidable implementation and maintenance complexity. Option C is also incorrect because MedicalInsightIntegrationHandler is not the specific handler described for publishing the MedicalInsightEvent platform event. The key words in the question are “without any delays,” which make an event-based publishing configuration the best fit. Therefore, the consultant should activate PublishMedicalInsightEventHandler .

=========

The correct answer is A because Remote Engagement video traffic requires Twilio endpoints to be trusted by the Salesforce org. Salesforce Help for setting up Twilio for Remote Engagement states that participants can connect to video calls by adding Twilio WSS endpoints as Trusted URLs in the Salesforce org. This is specifically required for secure video-call connectivity, which directly matches the symptom in the question: the Twilio credentials and Experience Cloud site are configured, but the video media fails to load.

Twilio External Credentials handle authentication and connection details for the integration, and the Experience Cloud site provides the HCP-facing remote engagement experience. However, browser and Salesforce security controls still need to allow the required Twilio WebSocket Secure traffic. If those URLs are not trusted, the page can load while the actual audio/video media connection fails.

Option B is incorrect because assigning a field-sales permission set to the Site Guest User would be inappropriate and overly permissive. The issue is media connectivity, not guest-user access to sales functions. Option C is also incorrect because a trigger handler for remote-session invitations would relate to record automation or invitation behavior, not secure loading of Twilio video traffic. Therefore, the consultant must add Twilio’s required endpoints to Trusted URLs .

=========

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 B because physical sample disbursement to an HCP requires compliant signature capture to confirm the handoff and support the audit trail. Salesforce’s Life Sciences Customer Engagement data model states that Provider Visit Management supports compliance requirements for sample eligibility, sample limits, allocations, and e-signature capture . Salesforce also describes Electronic Signatures through Digital Verifications as the way to set up signature trails for records or workflows that require users to verify key updates.

In this scenario, the field sales rep is physically transferring custody of a restricted product to the HCP. To finalize that disbursement and generate the required electronic receipt, the rep must capture the HCP’s digital signature directly on the mobile device. This ties the transaction to the HCP, the product, the quantity, the timestamp, and the specific disbursement event.

Option A is incorrect because an Inventory Adjustment is used to reconcile inventory discrepancies or administrative stock changes, not to document a compliant HCP sample handoff. Option C is also incorrect because a confirmation email is not the standard Life Sciences sample-disbursement action for chain-of-custody compliance. The required mobile action is direct digital signature capture from the HCP.

=========

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 B is correct because Salesforce Life Sciences Cloud for Customer Engagement provides sample limit templates that help organizations enforce country-specific sampling rules. Salesforce Help states that Life Sciences Cloud includes a generic sample limit template and several country-specific templates by default. These templates are designed to support sample governance where regulations vary by country or region. In the scenario, Cumulus Pharma must comply with regional laws, such as Belgian requirements, while maintaining GxP standards for sample distribution. Using the default country-specific templates is the most appropriate standard configuration because it applies predefined sample-limit governance based on regional compliance expectations.

Option A is not the best answer because Territory Product Quantity Allocation is used to allocate product quantities by territory, but the requirement is about legal and GxP compliance by country. Allocation controls available quantities; it does not, by itself, represent the compliant sample-limit template framework. Option C is incorrect because manually adjusting Quantity On Hand on Product Item would change inventory balances directly and could create audit, traceability, and compliance risk. Product Item represents stock at a location, but manual quantity changes are not the correct way to enforce regional sampling laws.

Therefore, the consultant should use the default country-specific sample limit templates so sample distribution follows regional compliance rules while remaining aligned with Life Sciences Cloud’s controlled sample-management framework.

=========

Option A is correct because the requirement is specifically to allow field sales reps to add colleagues as CC recipients when sending emails from the Life Sciences Cloud mobile app. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails from the Life Sciences Cloud mobile app from areas such as the home page, visit and account records, the content library, and the presentation player. The same Salesforce Help result also states that users can add colleagues as CC recipients, depending on the Salesforce admin’s configuration.

That wording directly matches the option “Add Colleagues as CC.” The purpose of the setting is not simply to expose a generic CC field, but to enable the Life Sciences mobile email experience where reps can copy internal colleagues on compliant business communications.

Option B, “Add CC Recipients,” is too generic and does not match the Life Sciences-specific setting name in the question. It describes the general email behavior but not the precise admin setting. Option C, “Enable CC Field Representative,” is also not correct because it implies a setting focused on copying the field representative, rather than allowing the field representative to add colleagues as CC recipients.

Therefore, to let field sales reps CC colleagues from the Agentforce Life Sciences mobile app, the consultant should enable Add Colleagues as CC.

=========

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.

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.

=========

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.

=========

Option C is correct because Life Sciences Cloud separates the overall visit activity from provider-specific visit details. In the Life Sciences Cloud data model, the Visit object tracks information related to a field representative’s visit to a healthcare provider and is used for Customer Engagement. Salesforce’s ProviderVisit object represents the details of a field user’s visit to a healthcare provider. The Customer Engagement data model also explains that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples.

For a group visit such as a “Lunch and Learn” with three HCPs, the overall event is represented by the parent Visit record. Each attendee requires their own provider-specific visit detail record because each HCP may have different product discussions, messages, samples, signatures, or follow-up activities. Therefore, the system creates one parent Visit and separate child Provider Visit records for each HCP attendee.

Option A is incorrect because a multi-select lookup field is not the correct Life Sciences Cloud visit data model pattern. Option B is also not correct because it implies individual parent-level Visit records for every attendee, which would duplicate the overall group interaction. The correct structure is one parent Visit for the group interaction and three child Provider Visit records, one for each Healthcare Provider attendee.

Option C is correct because the issue is isolated to the selected target account list, not to the overall availability of HCO accounts in the territory or application. Salesforce Life Sciences Cloud supports Lists and Filters so users can quickly identify a target group of accounts. These lists can be manually curated or filtered, meaning the accounts shown depend on the criteria or membership of the specific list being used. If only HCP accounts appear while HCO accounts are still aligned to the territory and visible elsewhere, the most likely cause is that the selected target account list itself includes only HCP accounts. Salesforce’s Life Sciences Cloud Developer Guide describes Lists and Filters as a way to quickly identify target account groups, and the LifeScienceAccountList object represents account list types such as filter, static list, and routine list.

Option A is not the best answer because Planner Administration record type settings would more broadly control planner behavior, not only one selected target account list. Option B is also not the best answer because Account Management record type configuration would affect how account types are configured or displayed more generally. The question states that HCO accounts are aligned and available elsewhere, which eliminates a broad record type or account management restriction. The problem occurs only when using the selected target account list during visit creation. Therefore, the consultant should review and correct the target account list criteria or membership so that both HCP and HCO accounts are included when needed.

=========

Option C is correct because an Ad Hoc inventory count assessment is used for an unscheduled inventory check, and Salesforce Life Sciences Sample Inventory Management supports discrepancy adjustments when the counted quantity differs from the system quantity. Salesforce Help states that when a discrepancy is recorded in an inventory count, Sample Inventory Management adjusts the system count positively or negatively to match the actual count. In this scenario, the rep physically counts 95 units while the system shows 100, so the compliant process is to submit the count and let the system create the adjustment transaction for the five-unit negative discrepancy.

Salesforce Help also describes Inventory Count Assessment as the object that captures the overview of the count, including where the assessment occurs and the assessment type. This supports using an inventory count assessment rather than manually changing inventory balances.

Option A is not correct because the missing units were not returned to the distribution center; creating a return would misrepresent the physical inventory event. Option B is also incorrect because an Initial inventory count is used for establishing an initial count, not for reconciling an unscheduled discrepancy after inventory already exists. Therefore, the correct compliant action is to submit an Ad Hoc inventory count assessment and let the system generate the adjustment transaction.

=========

The correct answer is A because Next Best Message uses product-message scoring data at the territory-account-product-message level. Salesforce’s Life Sciences Cloud Developer Guide states that Next Best Message provides tailored and relevant messages for each product associated with an account. Salesforce also documents the related scoring object and describes the calculation agent used to calculate the territory account product message score based on various metrics.

The scenario says Cumulus Pharma already has a custom predictive model outside Salesforce. The goal is not to build the model inside Salesforce, but to surface the model’s results to reps through the standard Next Best Message capability. Therefore, the external scores and rankings should be loaded into the object that stores ranked product-message recommendations for accounts in territories: Territory Account Product Message Score .

Option B, Visit Recommendation , is not the best answer because the requirement is specifically about product messages for HCPs, not general recommendations tied to a visit. Option C, Score Explainability Info , may support interpretation or explanation of scoring, but it is not the primary object used to load the external product-message score and ranking. To use Next Best Message with external model outputs, the consultant should load the results into Territory Account Product Message Score .

=========

Option C is correct because Advanced Sample Limit Templates are designed for custom, complex sample-limit rules. Salesforce Help explains that advanced sample limit templates are used to define custom sample limit rules for more complex needs and stricter requirements. This scenario requires two non-basic behaviors: a dynamic period start based on the product launch date and soft-limit enforcement that warns the rep but still allows the disbursement to proceed. Those requirements go beyond a generic calendar-year rule.

A Generic Sample Limit Template is not the best answer because generic templates are better suited for standard sample-limit logic. The requirement explicitly says the limit period must begin on the Product Launch Date rather than the standard Calendar Year, which makes the rule more specialized. A Country Sample Limit Template is also not correct because country templates are used for country-specific legal or regulatory sampling limits. In this question, the control is strategic and inventory-driven, not a legal requirement tied to a specific country.

Advanced templates are the correct fit because they allow more flexible configuration for business-specific sample controls, including nonstandard periods and warning-based enforcement. Therefore, the consultant should use an Advanced Sample Limit Template for the Immunexis launch sampling rule.

=========

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 .

=========