Als-Con-201 Salesforce Certified Agentforce Life Sciences Consultant Questions and Answers

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

=========

Digital Verification is the correct answer because Salesforce Life Sciences resources describe it as the native capability used to manage electronic signatures in Salesforce and support an organization’s 21 CFR Part 11 compliance requirements. Salesforce Help states that Electronic Signatures can be set up using the Digital Verifications feature, allowing signatures to be managed in Salesforce instead of relying on a third-party application. It also references creating a “signature trail,” which is the key concept in this question: the signature is not just a stored image, but part of a controlled verification process tied to the signed record and signer context.

Field Audit Trail is not the best answer because it tracks field history and retention for data changes; it does not provide the electronic-signature process required for HCP sample acknowledgments. Adobe Sign is also not the best answer because the question asks for the Salesforce Life Sciences feature that generates the audit trail inside the Life Sciences process. The Salesforce Developer Guide also identifies Digital Verification standard objects as part of the electronic-signature data model, reinforcing that Digital Verification is the Life Sciences capability designed for this use case.

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 Salesforce Life Sciences Sample Inventory Management automatically adjusts the system count to match the actual count when an inventory-count discrepancy is recorded. Salesforce Help for Discrepancy Adjustments for Inventory Counts states that when a discrepancy is recorded in the inventory count, Sample Inventory Management adjusts the system count positively or negatively to match the actual count.

In this case, the physical count is 95 units, while the system balance is 100 units. The system must reflect the physical reality immediately for audit accuracy. Therefore, Life Sciences creates an adjustment transaction for the negative difference of 5 units so that the recorded inventory balance aligns with the counted quantity. This preserves the audit trail because the discrepancy is not silently overwritten; it is reconciled through an inventory adjustment transaction.

Option A is incorrect because a Product Request is used to request or replenish inventory, not to reconcile a counted discrepancy. The system should first record the loss or variance before any replenishment process is considered. Option B is also incorrect because locking the Product Item and triggering an assessment workflow is not the standard discrepancy reconciliation behavior described for inventory counts. The correct behavior is automatic generation of an adjustment transaction to reconcile the system balance with the physical count.

Option B is correct because the requirement is specifically to prevent visit creation when a Visit overlaps with a Time Off Territory record. Salesforce Life Sciences documentation references Time Off Territory overlapping rules as the standard mechanism that prevents creating visits during TOT events. Salesforce’s Winter ’26 Customer Engagement package patch notes also mention an issue where a visit could be created during a Time Off Territory event, bypassing the overlapping rule that should have prevented creation. That confirms TOT overlapping rules are the expected standard control for this scenario.

Because the business wants a hard stop, the overlapping rule behavior must be set to “Error.” This means the rep receives an error and cannot proceed with scheduling the visit while it conflicts with the TOT time block.

Option A is incorrect because a custom validation rule on Visit would duplicate a standard Life Sciences calendar/TOT capability and may not handle the full mobile scheduling experience correctly. Option C is also not the best answer because “Block Activity on Conflict” on the TOT record type is not the documented standard configuration in the Life Sciences Visit/Calendar settings. The correct standard configuration is to use TOT Overlapping Rules and set the overlap behavior to Error. This prevents scheduling visits during the rep’s logged time off.

=========

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 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 this is a global mobile consent-capture behavior that should be configured in Consent Administration , not enforced through a custom validation rule or permission workaround. Salesforce Life Sciences Consent Management is used to capture, manage, and track HCP consent for communication channels and subscription preferences. Salesforce’s setup guidance for Consent Management directs administrators to the Life Sciences Commercial app, then Admin Console , and then Consent setup areas, which is where consent behavior is configured for the Customer Engagement experience.

The scenario requires that every consent captured on a mobile device include an HCP signature. The appropriate admin configuration is to locate the Signature Section in Consent Administration and set it to Required . This makes the signature pad mandatory during the consent flow and ensures reps cannot submit consent records without capturing the required signature.

Option A is not the best answer because a validation rule on Communication Subscription Consent may block saves after the user attempts submission, but it does not configure the guided mobile consent experience or make the signature pad properly required in the flow. Option C is also incorrect because a custom permission would control access or behavior by profile, but the requirement is global enforcement in the mobile consent flow. Therefore, the consultant should configure the Signature Section as Required in Consent Administration.

=========

Option A is correct because routines are the Life Sciences Cloud capability intended for reusable visit schedules and recurring route patterns. Salesforce Help describes Customer Engagement features as including the ability to optimize daily schedules by showing key events and applying predefined routines on the calendar. This directly matches the requirement: field sales reps repeatedly visit the same groups of accounts across weekly routes or multi-day coverage patterns and want to reuse those planned schedules instead of rebuilding visits every time.

Routines support practical field planning because a rep can save a predefined pattern of planned visits and apply it later when the same route or schedule is needed. This is different from simply grouping accounts.

Option B is not the best answer because account lists help reps organize, filter, and target groups of accounts, but they do not by themselves preserve a reusable multi-day visit schedule. Account lists can help with planning, but they are not the direct solution for saving and reapplying a planned route. Option C is also incorrect because Activity Plans define strategic goals, targets, and activity expectations across a period. They align engagement activity to business objectives, but they are not designed to save and reapply recurring visit schedules. Therefore, the consultant should recommend creating a routine that saves the predefined set of visits and applying that routine as needed.

Option A is correct because this is a mobile rendering limitation, not a data or filter issue. Salesforce documentation for reports and dashboards on mobile describes differences and limitations between desktop and the Salesforce mobile app. When a dashboard component appears on desktop but not in the mobile app, the consultant should first check mobile dashboard support and component compatibility rather than assuming that the report data is missing.

The question states that the funnel charts appear on desktop, which strongly indicates that the underlying reports and reporting periods are valid. If the data were missing for the selected reporting period, the chart would fail or show no data consistently, not only on mobile. Option C is therefore not a good fit. Option B is also incorrect because dashboard filters can affect what data is shown, but they do not make an unsupported chart type render in the mobile app.

Salesforce Help also discusses making dashboards available in mobile workflows and notes that mobile dashboard behavior depends on how dashboards are embedded and rendered in the Salesforce mobile app. For this scenario, the consultant should recommend replacing the funnel chart with a mobile-supported visualization or providing an alternate dashboard component for mobile users. Therefore, the correct answer is that funnel charts are not supported in the mobile app.

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 MIRF Share Management is the Life Sciences Cloud batch job used to manage sharing for Medical Inquiry records. Salesforce Help describes Medical Inquiries as supporting batch jobs that share and manage multiple medical inquiry records consistently and efficiently, and specifically identifies the MIRF Share Management job as the job used to maintain inquiry-data sharing. This directly matches the scenario: after a territory reorganization, field sales reps need access recalculated for historical Medical Inquiry records associated with HCPs in their newly assigned territories.

Option A is not the best answer because Account Object Share Rule Calculation is a generic description of account sharing recalculation. The issue is not general Account visibility; it is Medical Inquiry record visibility after territory changes. Option C is also incorrect because aligning accounts to territories handles territory assignment, but the accounts have already been reorganized. The remaining problem is recalculating access to Medical Inquiry records that should now be shared according to the new territory model.

Therefore, the consultant should run MIRF Share Management. This batch job is the standard Life Sciences mechanism for recalculating Medical Inquiry record sharing and ensuring field users regain access to inquiry records that correspond to their current territory-aligned HCPs.

=========

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.

=========

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 A because Salesforce’s Remote Engagement setup guidance for Life Sciences Cloud specifically identifies the Experience Cloud site as the place where language support is configured for remote engagement experiences. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that, for language support, the administrator should select Components and drag the Language Selector component to the page. This directly supports the requirement for HCPs to review and accept terms and conditions in multiple languages when joining remote visits.

Remote Engagement involves an HCP-facing experience, not only a sales-rep mobile action. The terms and conditions are presented through the Experience Cloud site used for the remote session, so the language-selection capability must be available there. Adding the Language Selector lets the HCP choose the appropriate language in the site experience before reviewing the terms.

Option B is incorrect because configuring the Start Remote Session quick action may help reps launch or manage remote sessions, but it does not provide the HCP-facing multilingual site control required for terms and conditions. Option C is also incorrect because a survey can collect feedback or preferences, but it is not the Salesforce-recommended way to localize the terms-and-conditions experience. The correct configuration is to add the Language Selector component to the Experience Cloud site.

=========

The correct answer is A because Remote Engagement email notifications depend on email templates configured for the relevant automated email invitation context/action. Salesforce Help for uploading and creating email templates in Life Sciences Cloud includes configuration fields for automated email invitation context and action. For a rescheduled or updated virtual visit, the email template must be configured so the automated email invitation action corresponds to the update event.

The scenario asks specifically about email notifications when virtual visits are rescheduled. A reschedule is an update to an existing visit invitation, not a new invitation and not a cancellation. Therefore, the consultant must ensure there is an email template whose Automated Email Invitation Action is set to Update . That template is then used by the Remote Engagement process when the visit details change and the HCP needs to receive the revised meeting information.

Option B is incorrect because configuring a handler around a visit status value such as “Rescheduled” is not the core template configuration required for the notification content and action. Option C may sound plausible because trigger handlers often support automation, but the question asks which configuration is required to send email notifications for rescheduled virtual visits. The action-specific email template is the necessary configuration. Therefore, the consultant should use an Email Template with Automated Email Invitation Action set to Update .

=========

Option C is correct because the requirement is product-specific and should be configured through Product Discussion Settings, not through a generic page-layout or Visit validation rule. Salesforce’s Life Sciences Cloud Visit Management data model includes Provider Visit Product Discussion as the object that represents products discussed during a visit, including key details about the product brand, therapeutic area, and related information. Salesforce also documents ProviderVisitProdDiscussion as representing additional notes or information about products discussed during a healthcare provider visit.

The question asks for a configuration that applies when a specific product, such as Immunexis, is discussed. Enabling Require Discussion in Product Discussion Settings for the product record is the most targeted standard configuration because it ties the requirement to that product’s visit discussion behavior.

Option A is not the best answer because a custom validation rule on Visit would have to inspect related product-discussion records and could become complex or unreliable for mobile visit submission behavior. Option B is also insufficient because making a Comments field required on the page layout would apply based on the layout, not specifically when Immunexis is discussed. It also would not necessarily enforce product-specific discussion requirements across all relevant visit submission paths. Therefore, the consultant should enable Require Discussion in Product Discussion Settings for the Immunexis product record.

=========

Option C is correct because Medical Insight upvotes are handled through the UserReaction object and related out-of-the-box logic. Salesforce’s Life Sciences Cloud Developer Guide states that UserReaction represents a user’s reaction to a medical insight, such as an upvote or downvote, and that these reactions are used to identify trending insights. This directly supports the scenario because the problem involves duplicate upvotes and the inability to see total upvote counts on Medical Insight records.

Salesforce’s MedicalInsight object documentation also references fields related to ranking and upvotes, including a default rank determined based on linked insights and their upvotes. This confirms that upvote behavior is part of the standard Medical Insights data model rather than something that should be rebuilt manually.

Option A is not the best answer because MedicalInsightValidationHandler sounds focused on validating Medical Insight records generally, not specifically managing user reactions, duplicate reactions, or upvote counts. Option B is also not preferred because custom validation rules and a new roll-up summary field would duplicate behavior that Salesforce provides through the Medical Insights user-reaction framework. The requirement asks for the out-of-the-box configuration, so the consultant should activate the UserReactionMedicalInsightHandler to manage upvote reactions consistently and support the total-count behavior.

=========

The correct answer is B because the Provider Activity Goal object represents the parent-level association between a provider account and an activity plan, while Provider Activity Goal Measure stores the specific measurable targets associated with that goal. Salesforce’s Life Sciences Cloud Developer Guide describes ProviderActivityGoal as storing progress toward the target for an account, including the percentage of the overall goal achieved by completed activities. Salesforce’s Life Sciences standard objects also include ProviderActivityGoalMeasure , which represents the activity goal measure details.

In practical reporting and querying terms, the analyst should use Provider Activity Goal to identify the HCP/account’s association to the plan period, and then query the related Provider Activity Goal Measure records to retrieve the specific target values, such as total interaction target, channel target, product target, or other measurable plan goals depending on configuration.

Option A is incorrect because Assessment Task and Assessment Indicator are used for assessment-style workflows, not for storing provider activity-plan target measures. They may capture structured assessment responses, but they do not represent activity-plan goal targets. Option C is incorrect because while Activity Plan is the high-level planning object, it is not the direct account-to-plan parent association described in the question, and “Account Goal” is not the specific Life Sciences child object used for provider activity target measures. Therefore, the correct parent-child pairing is Provider Activity Goal and Provider Activity Goal Measure .

=========

Option A is correct because Account Summarization uses a cross-object graph to define which objects and relationships are included in the generated summary. Salesforce Help states that administrators can create cross-object graphs from a predefined Account Summarization template to provide a complete view of an account and its related objects. This directly matches the requirement to include Account data and related Healthcare Provider and Contact Point Address information in the summary.

The phrase “historical data” is also important. Salesforce Account Summarization setup includes configuring history tracking for the fields included in the template, so Agentforce can summarize recent changes from the selected objects and fields. The cross-object graph defines the relationship structure, while field history tracking provides the change history used in the summary.

Option B, Actionable Relationship Center, is not the best answer. Actionable Relationship Center is used to visualize related records and relationships, but the Account Summary configuration specifically relies on cross-object graphs. Option C, Affiliation Alignment Rules, is unrelated because those rules support territory alignment for affiliated accounts, not Account Summary object relationships. Therefore, the consultant should use a Cross-Object Field History Graph to define the Account, Healthcare Provider, Contact Point Address, and related-object structure used by Agentforce Account Summary.

=========

The correct answer is A because User Reaction is the object designed to capture user feedback or reactions related to a Medical Insight. Salesforce’s Life Sciences Cloud Developer Guide identifies the UserReaction object and states that it can be associated with a medical insight through the source reference record relationship. This makes it the most appropriate object when users need to provide feedback on Medical Insights that have already been captured.

The scenario is not asking field reps to complete a formal assessment or collect HCP feedback. It asks for reps to provide feedback on the medical insights captured in the system. A User Reaction record supports this by allowing a user-level response to be connected back to the relevant Medical Insight record, preserving the relationship between the insight and the feedback.

Option B, Assessment Task , is incorrect because assessment tasks are typically used as structured tasks or questionnaires within planning, account management, or guided evaluation workflows. They are not the direct object for providing reactions to Medical Insights. Option C, Survey , is also incorrect because surveys are used to collect responses, often from customers or HCPs, through a survey experience. A survey would be unnecessary and less precise for internal rep feedback on an existing Medical Insight. Therefore, User Reaction is the correct object to recommend.

=========

Option A is correct because Remote Engagement with Twilio uses Salesforce named and external credentials, and users need access to the external credential principal to use those credentials. Salesforce Help for configuring Twilio credentials in Life Sciences Remote Engagement states that the Life Sciences Customer Engagement managed package includes the named and external credentials for Twilio. The same Salesforce Help result specifically references selecting External Credential Principal Access as part of the setup. This aligns directly with the error: the field sales rep cannot access the video service credentials, even though the Life Sciences Field Sales Representative permission set has been verified.

Option B is incorrect because the solution is not to manually provide the rep with a Twilio authentication token. That approach would be insecure and inconsistent with Salesforce’s named/external credential model. Credentials should be managed centrally through Salesforce configuration, not distributed directly to end users. Option C is also incorrect because “Twilio Users Public Group” is not the documented permission mechanism for accessing the video service credentials in Life Sciences Cloud Remote Engagement.

Salesforce’s broader named credential security documentation also explains that external credential principals can be mapped to permission sets and profiles so users can make callouts to external systems with the right access. That supports the need to grant External Credential Principal Access rather than changing the rep’s profile or sharing tokens manually.

=========

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 B is correct because Salesforce Life Sciences Cloud Medical Insights uses Medical Insight and Medical Insight Account configuration to capture and surface qualitative observations from engagements. Salesforce Help states that admins configure Medical Insight and Medical Insight Account objects by customizing the record page layout and creating required field sets. This directly matches the requirement: MSLs need to record qualitative observations and make those insights visible in the related account and visit context.

Medical Insights are intended to record observations or insights from HCP engagements, while the related Medical Insight Account object supports association of those insights with relevant accounts. By configuring layouts and field sets, the consultant controls which insight fields are available to users and how the data appears in the Life Sciences user experience. This is a standard configuration approach rather than a custom development pattern.

Option A is incorrect because feed tracking supports collaboration and Chatter-style record-feed updates; it does not configure the Medical Insights data-entry and display model. Also, “Product Insight” is not the standard object referenced for this Life Sciences Medical Insights setup. Option C is incorrect because assessment task flows and Medical Inquiry metadata are separate capabilities. Medical Inquiries manage HCP questions and responses, while Medical Insights capture field observations. Therefore, the consultant should customize the Medical Insight page layout and create field sets on Medical Insight and Medical Insight Account objects.

=========

The correct answer is A because Salesforce Life Sciences Territory Management batch jobs can be scheduled with an hourly frequency. Salesforce Help for running Territory Management jobs states that, from the Life Sciences Commercial Admin Console, the job can be scheduled hourly, every selected hours , by selecting the hour from the dropdown. This confirms that hourly scheduling is a supported automatic execution option for Territory Management batch jobs.

Territory Management batch jobs are important because Life Sciences territory configuration affects field execution, account alignment, provider access, and downstream engagement processes. Scheduling these jobs automatically helps ensure that territory-related processing runs on a predictable cadence without requiring administrators to manually start each batch job. When the question asks how often the jobs can be scheduled to execute automatically, the available option that matches Salesforce’s documented scheduling capability is Hourly .

Option B, Every 12 hours , may sound plausible because some enterprise batch processes use longer intervals, but it is not the best answer because Salesforce’s documented configuration describes hourly scheduling and selecting the hour interval. Option C, Monthly , is also incorrect because monthly execution would be too infrequent for many territory-management operational updates and is not the option reflected in the documented batch-job scheduling guidance. Therefore, the consultant should identify Hourly as the correct scheduling frequency.

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

Option C is correct because Subject Management is the standard approach for organizing Medical Insights by topic. Salesforce Life Sciences Medical Insights allows users to capture, view, and work with insights from HCP engagements. Salesforce Help describes Medical Insights as a feature that can be made available in the Life Sciences mobile app so users can view their own insights and insights captured by users in their territories. Salesforce also documents Medical Insight object setup through page layouts and field sets, which supports structured capture and display of insight details.

The question asks for a way to organize insights for easy searching and filtering by topics. Subject Management fits that need because subjects provide a controlled way to classify insights into topics or categories. This helps reps and analytics teams search, filter, and review insights consistently rather than relying only on free-text notes.

Option A, Life Science Insight List Filter, is not the best answer because filtering is a user experience mechanism, not the underlying topic-management configuration. Option B, Actionable List Filter Criteria, is also not correct because actionable lists and filter criteria are broader account or list-management concepts; they do not define Medical Insight topics. Therefore, to organize Medical Insights by topic for better searching and filtering, the consultant should recommend Subject Management.

=========

The correct answer is A because Salesforce Life Sciences Cloud provides the MIRF Share Management job specifically to manage sharing for medical inquiry records. Salesforce Help states that teams can save time, reduce manual errors, and maintain the integrity and reliability of inquiry data by using the MIRF Share Management job. Salesforce also has dedicated guidance for defining sharing settings for Medical Inquiries.

The requirement is territory-based sharing: all medical inquiries in a territory must be shared with all field sales reps in that same territory. A scheduled MIRF Share Management job is the Life Sciences-specific mechanism designed to maintain this sharing behavior for medical inquiry records. This is preferable because medical inquiry workflows often have regulated data-handling and access-control requirements, so using the purpose-built sharing-management capability is safer and more maintainable than creating generic sharing automation.

Option B is not the best answer because the described configuration is not simply a generic Territory Management setting in the Life Sciences Admin Console. The question asks specifically how to share medical inquiry records, and Salesforce points to MIRF Share Management for that purpose. Option C is also incorrect because an owner-based sharing rule on the Inquiry object would be a generic Salesforce sharing approach. It may not correctly reflect Life Sciences medical inquiry sharing logic or maintain the intended record integrity. Therefore, the consultant should schedule the MIRF Share Management job .

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.

=========