Choose 1 option.
When a field sales rep delivers samples they have physically received but have not yet acknowledged in the system, a Product Disbursement record is created with a warning. The system must maintain inventory integrity.
Which action is required to reconcile the product sample count?
Answer : A
The correct answer is A because Salesforce Life Sciences Sample Inventory Management includes a process for fixing unresolved product disbursements. Salesforce Help for managing samples references Fix Unresolved Product Disbursements, and the same Sample Inventory Management area describes inventory operations such as transfers, returns, shipments, assigned batches, and product disbursements as part of the sample lifecycle.
The issue occurs because the rep physically received samples and handed them to an HCP before formally acknowledging the inventory in the system. To preserve inventory integrity, Salesforce cannot simply reduce inventory counts as if the stock were already confirmed in the rep's available inventory. Instead, the system flags the Product Disbursement as unresolved. The rep must first acknowledge the inventory so the system recognizes the received stock, and then use the Resolve Disbursement quick action to complete the reconciliation and finalize the inventory count updates.
Option B is incorrect because the process does not require an admin to manually override an unresolved status in org-wide settings. This is an operational correction handled by the rep through the sample inventory workflow. Option C is also incorrect because forcing a Manual Adjustment would bypass the intended reconciliation process and could weaken auditability. The proper Life Sciences process is to acknowledge the inventory and then resolve the disbursement using the quick action.
=========
Choose 1 option.
An Agentforce Life Sciences Consultant built an Experience Cloud page for Remote Engagement. They need to drag the specific standard component onto the canvas that renders the video player and handles the Terms & Conditions logic.
Which out-of-the-box component should the consultant select?
Answer : A
Option A, HCP Remote Platform Conference, is correct. In Salesforce Life Sciences Cloud Remote Engagement, the consultant creates an Experience Cloud site so Healthcare Providers can join remote visits. Salesforce Help specifically states that the HCP Remote Platform Conference component is available under Custom Components and can also be found through the search bar when building the Experience Cloud page. This is the component that is placed on the page to support the remote engagement conference experience.
The question also mentions video playback and Terms & Conditions logic. Salesforce Life Sciences Cloud Remote Engagement setup includes configuration for video call settings and video call Terms and Conditions, and the Experience Cloud site component is the user-facing component that brings the HCP remote conference experience onto the page. Salesforce Help also references Remote Engagement setup tasks such as configuring video call settings with Twilio and configuring video call Terms and Conditions, showing that Twilio is part of the underlying video-call configuration rather than the Experience Cloud page component itself.
Option B, Twilio Connector, is incorrect because Twilio configuration supports the video service settings, but it is not the component dragged onto the Experience Cloud page canvas. Option C, Remote Video Player, is not the standard component name identified in the Salesforce setup documentation. Therefore, the out-of-the-box component the consultant should select is HCP Remote Platform Conference.
Choose 1 option.
Cumulus Pharma wants to roll out Tableau Next to provide its field sales team with real-time performance insights, such as ''Visit Plan Attainment,'' directly within the Agentforce Life Sciences mobile app. The relevant Metrics have been created, the Tableau View component has been added to the Mobile Home Page Lightning record page, and the metadata cache has been refreshed. However, when a field sales rep logs in to the app, the Metrics component displays an error indicating insufficient privileges and the metrics do not load.
Which Tableau Next permission set should the Agentforce Life Sciences Consultant assign to resolve this issue?
Answer : C
The correct answer is C because field sales reps only need to view and consume Tableau Next metrics in the Life Sciences mobile app. Salesforce Help for Tableau Next in Life Sciences Cloud explains that Tableau Next integrates with Life Sciences Cloud to provide actionable insights and enhanced visualizations. Salesforce's Tableau Next permission guidance also identifies Tableau Next Consumer as the permission set used for viewing Tableau Next content and interacting with metrics, while creator-level access is intended for users who create and manage Tableau Next assets.
In this scenario, the technical setup has already been completed: the metrics exist, the Tableau View component has been placed on the Mobile Home Page Lightning record page, and the mobile metadata cache has been refreshed. The remaining issue is an insufficient-privileges error, which indicates that the user lacks the Tableau Next permissions required to load and consume the metric. Assigning Tableau Next Consumer grants the field rep the appropriate access level without giving unnecessary authoring privileges.
Option A, Tableau Next Creator, is incorrect because field sales reps are not creating or administering metrics; they only need to consume them. Option B, CRM Analytics Plus User, is also incorrect because the requirement is specifically for Tableau Next metrics, not legacy CRM Analytics access. Therefore, the consultant should assign the Tableau Next Consumer permission set.
=========
Choose 1 option.
Cumulus Pharma implemented the Affiliations feature in Agentforce Life Sciences for Customer Engagement to map relationships between Healthcare Providers (HCPs) and Healthcare Organizations (HCOs). The Agentforce Life Sciences Consultant configured the Affiliation Reverse Role Mapping in the Admin Console to define how roles should translate, for example, Attending translates to Employing. However, users report that when they create a new Affiliation record, the system fails to automatically generate the record of the reverse relationship.
Which trigger handler must the consultant enable to complete this action?
Answer : C
The correct answer is C because reverse affiliation creation is handled by the AffiliationReciprocalHandler. Salesforce Help for Life Sciences trigger handlers identifies AffiliationReciprocalHandler as the handler that manages reciprocal affiliations. The same documentation notes behavior related to reciprocal affiliations and affiliation type handling, which directly matches the scenario where a newly created affiliation should automatically create the reverse relationship.
Affiliation Reverse Role Mapping defines how the relationship role should translate between the original and reciprocal records. For example, if an HCP is ''Attending'' at an HCO, the reverse relationship may show the HCO as ''Employing'' or otherwise related to the HCP, depending on the configured mapping. However, defining the mapping alone does not execute the automation. The trigger handler must be active so that when users create a new Affiliation record, Salesforce can generate the reciprocal Affiliation record using the configured reverse role mapping.
Option A, AffiliationUniquenessHandler, is incorrect because uniqueness logic prevents duplicate or invalid affiliation records; it does not create the reverse relationship. Option B, HardAffiliationHandler, is also incorrect because it is not the handler identified for reciprocal affiliation generation. Since the missing behavior is automatic creation of the reverse affiliation, the consultant must enable AffiliationReciprocalHandler.
Choose 1 option.
Cumulus Pharma uses a territory model where a Healthcare Provider (HCP) is assigned to both the ''Cardiology West'' and ''Launch Team'' territories. The company needs to store ''Year-to-Date Visit Counts'' for the HCP for each territory independently.
Which standard object should the company use to store these territory-specific account metrics?
Answer : A
Option A, Provider Account Territory Summary, is the best answer because the requirement is to store summarized, territory-specific account metrics. The HCP belongs to more than one territory, and Cumulus Pharma must track Year-to-Date Visit Counts independently for each territory. Salesforce's Life Sciences Account Management data model includes both Provider Account Territory Information and Provider Account Territory Summary as standard entities for managing healthcare provider and organization accounts, related profiles, and territory-specific information.
Provider Account Territory Summary is the object designed for summarized metrics at the provider-account-and-territory level. That makes it the appropriate place for values such as Year-to-Date Visit Counts, which are calculated or aggregated metrics rather than the raw alignment relationship itself.
Option C, Provider Account Territory Information, is related but not the best answer. Salesforce's Developer Guide describes ProviderAcctTerritoryInfo as representing engagement data between an account and a user within an assigned territory, including items such as next provider visit date and preferred address. However, the question asks for territory-specific account metrics, not general engagement information between a user, account, and territory. Option B, Provider Account Territory Association, is also not correct because the issue is not simply associating an account to a territory. The HCP is already assigned to both territories. The need is to store independent summarized metrics for each territory. Therefore, Provider Account Territory Summary is the correct standard object.
=========
Choose 1 option.
An Agentforce Life Sciences Consultant has configured the Medical Inquiry process for Cumulus Pharma. When a field sales rep submits a signed inquiry, the status correctly updates to ''Submitted,'' but the Case record remains owned by the rep instead of being automatically routed to the Medical Science Liaisons (MSLs).
Which trigger handler is inactive?
Answer : A
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.
=========
Choose 1 option.
Cumulus Pharma implemented a custom predictive model outside of Salesforce to determine the optimal product message for Healthcare Providers (HCPs). The company wants to display these recommendations to its field sales teams within Salesforce.
Which object should an Agentforce Life Sciences Consultant load the external scores and rankings into to use the Next Best Message feature?
Answer : A
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.
=========