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

Option C is correct because Salesforce Life Sciences Cloud supports manual territory alignment for affiliated accounts. Salesforce Help for Territory Alignment for Affiliated Accounts states that a user’s territory determines which accounts they can view and manage, and that users can manually align an affiliated account to their territory. The broader Affiliations documentation also explains that affiliation alignment rules can automatically align affiliated accounts, but the scenario specifically asks for manual alignment by field users when needed.

The correct Admin Console setting is therefore the one that enables users to align affiliated accounts to the user’s territory. This setting allows reps working with complex HCO/HCP affiliation networks to bring relevant affiliated accounts into their current territory alignment when the relationship is valid for their business process.

Option A is not the best answer because the requirement is not to align accounts outside the user’s territory. It is to let users align affiliated accounts to their own current territory. Option B is also incorrect because searching for accounts outside the user’s territory only affects discoverability. It does not grant the ability to perform the actual affiliated-account alignment. Therefore, the consultant should enable “Enable users to align affiliated accounts to the user’s territory” in Account Management > Affiliation.

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 .

=========

The correct answer is C because sample visibility during visits depends on the product being configured as a Life Sciences Marketable Product with an appropriate distribution method. Salesforce Help for setting up Sample Inventory Management data states that, to designate a product as a sample product, administrators create a corresponding Life Science Marketable Product record. Salesforce’s Life Sciences Cloud Developer Guide for LifeSciMarketableProduct identifies distribution methods such as Drop , DropAndShip , and Ship , which define how a product is distributed to a provider.

In a provider visit, a product must be configured as marketable and available for the relevant distribution method before reps can select it for sample drop-off. If the product is meant to be handed directly to the HCP during the visit, the distribution method must include Drop . If it can be either handed off during the visit or shipped, Drop and Ship is appropriate. This setup makes the product eligible for visit-based sampling workflows.

Option A is incorrect because permissions alone do not make a specific sample product visible. Reps may have access to sampling functionality, but the product still must be configured correctly. Option B is also incorrect because profile configuration in Visit Administration is not the key product-availability control. The essential configuration is the Life Sciences Marketable Product record with the correct distribution method. Therefore, the consultant should set the distribution method to Drop or Drop and Ship .

Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.

The key word in the question is “collaborate.” Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because “availability” typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user’s territories, and the named handler that most directly supports that requirement is the sharing handler.

Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.

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.

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 B is correct because Salesforce Life Sciences Cloud provides a standard Data Change Requests framework for governed master-data updates. The requirement is not simply to block a change or create a manual task; it is to route critical HCP data changes to a Data Steward for review before the change is applied. Salesforce’s Life Sciences Cloud Account Management documentation describes Data Change Requests as a capability used to validate data changes by objects and fields and configure data changes by profile and record type. That aligns directly with controlled governance over fields such as Medical License Number.

The specific configuration object in the question, LifeSciDataChgPersonaDef, represents the persona-based data-change configuration. Salesforce’s Developer Guide identifies LifeSciDataChgPersonaDef as part of Data Change Requests and includes the ChangeUpdateType picklist field. Setting ChangeUpdateType to DoNotApplyChangesImmediately means changes are not applied directly by the sales rep persona and can instead be managed through the data-change governance process.

Option A is not the best answer because a custom record-triggered flow would duplicate standard Life Sciences Cloud data-change governance and could create maintenance or compliance risk. Option C is also not ideal because a validation rule only blocks the update; it does not create the governed change-request process needed for Data Steward review. Salesforce’s Data Change Requests data model includes Life Science Data Change Definition, managed fields, record types, persona definitions, and Life Science Data Change Request, confirming this is the intended standard architecture.

=========

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.

=========

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

=========

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 B because the requirement is based on HCP affiliation with an aligned HCO plus a specialty filter. Salesforce Help for Life Sciences affiliations explains that affiliation alignment rules can automatically align affiliated accounts to specific territories. Salesforce also describes territory alignment for affiliated accounts as a way for a user’s territory to determine which accounts they can view and manage, with affiliated-account alignment supporting territory assignment through relationships.

In this scenario, the territory is driven by the hospital relationship: Bay Area General Hospital is the major HCO that defines the hospital-based territory. Both HCPs are affiliated with that hospital, but only the oncology HCP should be aligned. Therefore, the correct configuration is an affiliation alignment rule for the territory with Care Specialty = Oncology . This lets the system evaluate the affiliation relationship and apply the specialty constraint before aligning the HCP to the San Francisco Oncology territory.

Option A is incorrect because a geo assignment rule based on zip code would not correctly model the hospital-based affiliation logic. It might align accounts by location, but it does not address the HCP-HCO affiliation relationship. Option C is incorrect because sharing rules control record visibility, not territory alignment. The requirement is automatic territory alignment, so the consultant should configure an affiliation alignment rule with the oncology specialty filter.

The correct answer is B because Life Sciences Cloud supports configuring quick actions for the mobile app through the Admin Console. Salesforce Help for Medical Insights states that Medical Insights can be made available to users in the Life Sciences mobile app so users can view their own insights and insights shared with them. Salesforce Help also describes Quick and Custom Action Management as the way to simplify user experiences in Salesforce and the Life Sciences for Customer Engagement mobile app by leveraging quick actions and custom actions.

The requirement is not merely to expose the Medical Insights tab. The rep must be able to quickly report a medical insight while managing a visit on an iPad. Configuring the Create Medical Insights quick action in the Admin Console makes the action available in the mobile workflow where reps need it. This supports fast, in-context capture of field observations during a visit.

Option A is incorrect because creating a custom action and custom flow adds unnecessary complexity when the standard quick action can be configured declaratively. Option C is also not the best answer because editing the Visit page layout and adding a generic standard action may not make the action available correctly in the Life Sciences mobile app experience. The Admin Console is the correct configuration point for mobile quick actions. Therefore, the consultant should configure the Create Medical Insights quick action using the Admin Console.

The correct answer is A because provider summary generation depends on the prompt template and the data supplied to that prompt. In Life Sciences Cloud account summarization, Salesforce documentation references custom prompt templates for account summarization and the account summarization workflow, while the workflow uses the Generate Provider Account Territory Summary flow as part of the summary-generation process. Salesforce also documents that this flow calls actions such as Get Object Relationship Data and Get Life Sciences Configuration Field Names , meaning the flow participates in retrieving relationship-based data, but the generated business summary still needs the prompt template to know what information to use and how to summarize it.

Updating the ARC graph alone makes additional objects and fields available in the relationship structure, but it does not automatically change the prompt’s summarization behavior. To ensure the new information is used correctly, the consultant should create a new prompt template version, update the input dataset so the new fields are included, revise the summarization instructions so the AI knows how to use them, and then activate that version. This aligns with Salesforce’s guidance that prompt-based generation relies on the configured prompt and its grounding/input data. Option B is incomplete because changing only the flow does not update the prompt’s instructions. Option C is also incorrect because batch-job configuration controls bulk execution, not the actual summarization logic.

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

=========

Option B is correct because the Healthcare Provider object contains provider-specific Life Sciences attributes, including whether the provider is designated as a speaker for engagement. Salesforce’s Life Sciences Cloud Developer Guide for the HealthcareProvider object states that the object and its fields are used by Account Management and Segmentation, and the search result for the same Salesforce object documentation identifies a field that indicates whether the provider is designated as a speaker for engagement, with a default value of false. This directly matches the question’s requirement to identify whether a physician is flagged as a speaker.

Option A, Board Certification, is incorrect because board certification stores credential or certification information about a provider. It may help qualify the provider professionally, but it does not represent the commercial engagement flag that identifies whether the provider is a speaker. Option C, Person Account, is also not the best answer. In Life Sciences Cloud, physicians are commonly represented through Person Accounts, but the speaker designation is stored in the Healthcare Provider data model, not as a generic Person Account-only attribute.

Therefore, when the consultant needs to identify whether a physician is flagged as a speaker in Agentforce Life Sciences for Customer Engagement, the correct object to reference is Healthcare Provider .

=========

The correct answer is B because the requirement is persona-specific. Cumulus Pharma does not want the two additional custom objects to influence provider summaries for all users; the new insights and market intelligence must be used only when the provider summary is generated for the Key Account Manager profile. Salesforce Life Sciences Account Summarization is designed to generate contextual provider summaries from the latest changes, interactions, and insights related to a healthcare provider, and its configuration includes profile-specific setup so different personas can receive summaries grounded in the information relevant to their role.

Creating mapping records in the Provider Summary Profile Mappings tab associates the relevant summary data with the KAM profile. This is the most precise configuration because it controls which profile receives access to the additional summary context. Option A is not the best answer because creating a cross-object graph and assigning it directly to a profile is not the described administrative mechanism for persona-based provider summary control. Option C is also too broad: updating the Provider Summary Objects mapping may make the custom objects available to the summarization framework, but the key requirement is limiting usage to the new KAM persona. Profile mapping is what ensures the new objects are applied only for that persona’s provider summary generation.

=========

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 the best answer because the requirement is specifically to activate Activity Plans based on the time period. In Life Sciences Cloud, Activity Plans define activity goals for sales representatives over a specific period, including goals, measures, territories, accounts, and activity targets. Salesforce Help describes Activity Plans as a way to transform provider interaction strategies into actionable tasks with defined goals and targets for field representatives.

When the key requirement is status activation based on the plan’s effective time period, the relevant job is the Update Activity Plan Status batch job. The wording of this option directly aligns with the requested outcome: activate the plans according to time period. Validate Activity Plans is related to validation and activation readiness. Salesforce Help notes that the Validate Activity Plans batch job is used in the activity-plan approval and activation process, but the question does not ask merely to validate plans or activate approved provider activity goals.

Process Provider Activity Plans is also not the best answer because it is more closely associated with processing provider-level plan records and goal calculations after plans are configured. The question asks which step completes configuration and activates plans based on time period, making the status update job the precise fit. Therefore, the consultant should schedule or immediately trigger the Update Activity Plan Status batch job.

=========

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.

=========

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.

=========

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.

Option C is correct because the requirement is to display a conditional indicator on the Provider Card based on the Targeted Account field. Salesforce Help states that Provider Cards consolidate account information from scattered objects and fields into a single interface. Salesforce also documents that, in the Provider Card template, admins can use data from Provider Account Territory Information, including the Targeted Account field, to show whether an account is a target account.

The correct pattern is to add an item group element to a section, include the Targeted Account field from the Provider Account Territory Info source object, and configure visibility conditions so the card shows the appropriate label. When the field value indicates that the account is targeted, the card can show “Target.” When it is not targeted, a separate condition can show “Not Target.”

Option A is not correct because applying record-level filters to show only targeted accounts would hide non-targeted accounts rather than displaying both “Target” and “Not Target” states. Option B is not the best answer because a repeater element is used for repeating sets of records; this requirement is a single account-level indicator. Therefore, item group elements with visibility conditions are the right configuration for the Provider Card indicator.

=========

Option C, Account Plan Stakeholder, is correct because the requirement is to capture stakeholder-profiling attributes within a Key Account Management account plan. Salesforce Help describes Account Plan Stakeholders as the way to influence an account’s decision-making policies by adding stakeholders to an account plan. That aligns directly with the scenario, where the KAM is mapping the influence structure of a hospital’s Pharmacy & Therapeutics committee and classifying an HCP as “High Influence” and a “Supporter.”

The Salesforce Key Account Management Account Plan data model includes Account Plan, Account Plan Participant, Account Plan Participant Stakeholder, Account Plan Stakeholder, Account Plan Stakeholder Action, and Account Plan Stakeholder Product. This confirms that stakeholder management is part of the standard KAM account-planning architecture, and Account Plan Stakeholder is the object used to represent stakeholders in the account plan context.

Option A is incorrect because Account Contact Relation represents a relationship between an account and a contact in standard Salesforce account modeling. It does not represent the stakeholder’s role, sentiment, or influence inside a specific Life Sciences Account Plan. Option B, Account Plan Participant, is also not the best answer because participants are users or collaborators who work on the account plan, while stakeholders represent the external decision-makers or influencers being profiled. Therefore, the correct object for storing stakeholder attributes such as influence level and support position is Account Plan Stakeholder.

=========

The correct answer is B because sprint completion values are configured in the Life Sciences Admin Console under Key Account Management sprint settings. Salesforce Help for Configure Sprint Completion Statuses states that administrators should go to the App Launcher, open Admin Console , select Key Account Management , and then select Sprints Settings in the left navigation pane. From there, admins add the sprint values that indicate completion.

The scenario says KAMs are selecting a picklist value called “Finished,” but the system does not recognize the sprint as closed for reporting. That means the label exists as a picklist option, but it has not been mapped as a completion status in the Life Sciences Key Account Management sprint configuration. The consultant must configure the completion-status mapping in Sprint Settings so the platform treats “Finished” as a closed/completed sprint value.

Option A is too broad and does not point to the specific sprint completion configuration. Option C is also incorrect because editing the Status picklist in Object Manager only changes or adds picklist values. It does not tell the Life Sciences Key Account Management logic which values count as completed for reporting and process behavior. Therefore, the mapping should be configured in Admin Console > Key Account Management > Sprint Settings .

=========

The correct answer is C because Salesforce’s electronic signature capability for Life Sciences is Digital Verification . Salesforce Help states that the Electronic Signature feature provides 21 CFR Part 11-ready electronic signature functionality , and the setup guidance directs administrators to configure the Digital Verifications feature to manage electronic signatures in Salesforce rather than relying on a third-party application.

The requirement is specific to regulated sample drop-off. The system must capture the HCP’s signature image, associate it with the sample disbursement, preserve the timestamp, and maintain an audit trail that supports compliance expectations. Digital Verification is the Salesforce Life Sciences feature designed to support electronic-signature capture in this type of regulated workflow.

Option A, Shield Audit Trail , is incorrect because Salesforce Shield can help with broader platform security, event monitoring, and auditability, but it is not the Life Sciences feature that captures an HCP’s electronic signature for sample drop-off. Option B, DocuSign for Salesforce , is also incorrect because the question asks for the Agentforce Life Sciences for Customer Engagement feature that supports this requirement. Salesforce Help specifically points to Digital Verification for managing electronic signatures directly in Salesforce. Therefore, the consultant should enable Digital Verification to support the 21 CFR Part 11-ready signature and audit requirements.

=========

The correct answer is B because off-label control in the visit experience is tied to product detailing behavior. In life sciences commercial engagement, product detailing governs what products, messages, indications, and approved content can be discussed or shown during a visit. Salesforce Trailhead describes Life Sciences Cloud content visibility as being filtered by territory, product assignment, and account restrictions to prevent off-label or noncompliant sharing. This aligns most closely with Visit Settings > Product Detailing Settings , because that is the visit configuration area where product discussion and detailing behavior is controlled.

The question asks where the consultant should configure whether reps are allowed to discuss products for unapproved indications. That is not a generic compliance switch; it is a visit-detailing control connected to product and indication behavior in the field engagement workflow. Product Detailing Settings are therefore the correct place to enforce whether off-label discussion is permitted, warned, or restricted according to company policy.

Option A is incorrect because “Compliance Settings > Off-Label Validation” is not the standard configuration path presented in the available options for the Life Sciences visit experience. Option C is also incorrect because Restricted Products would control whether products are available or restricted, but the scenario is specifically about discussion of unapproved indications during product detailing. Therefore, the consultant should use Visit Settings > Product Detailing Settings .

=========

Option C is correct because Life Sciences mobile offline behavior depends on metadata cache for page layouts, metadata definitions, and offline user interface configuration. Salesforce Help for customizing the Life Sciences Cloud mobile app states that the generated metadata cache includes object schemas and metadata definitions that the mobile app stores locally to support both online and offline modes. Salesforce Help for setting up the Life Sciences Cloud mobile app also identifies object metadata cache settings, application settings, profile-based configurations, and UI customizations as part of the mobile setup process.

This directly matches the issue. The reps completed a data sync, but data sync alone does not necessarily refresh page layout metadata or translation changes used by the offline mobile app. Since the consultant changed Account page layout configuration and translation files, the correct action is to regenerate the metadata cache for the relevant profiles so offline users receive the updated metadata package.

Option A is incorrect because resetting the Sync Processor job status addresses synchronization processing, not metadata or translation availability. Option B is also incorrect because Mobile Offline Briefcase filters control which records or data are available offline; they do not publish updated page layouts or translated labels. Therefore, the consultant should generate a new metadata cache for the affected profiles.

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 C because the Life Sciences Cloud mobile app relies on metadata cache configuration to make updated page metadata available in the mobile experience. Salesforce documentation for customizing the Life Sciences Cloud mobile app states that administrators should generate a new metadata cache whenever they update Lightning record pages, page layouts, object or schema changes, new or modified feature settings, or related mobile configuration. The official setup path also references the Life Sciences Commercial app, Admin Console, Mobile, and Object Metadata Cache Configuration.

In this scenario, the Lightning web component was deployed and added correctly to the Lightning page, and the page was activated as the Org Default for Desktop and Phone. That means the desktop Lightning configuration is not the issue. The missing step is refreshing or creating the mobile metadata cache so the Agentforce Life Sciences mobile app can recognize the updated Lightning page structure and component metadata.

Option A is incorrect because activating a trigger handler is not the normal remedy for mobile page metadata visibility. Trigger handlers relate to backend automation behavior, not rendering a newly added component in the mobile UI. Option B is also not the best answer because reinstalling the app is a user-side workaround and does not address the administrator-controlled metadata cache. The correct administrative action is to create a new metadata cache in the Admin Console.

=========

The correct answer is C because the requirement is about sampling eligibility and validation behavior during visits. Salesforce Life Sciences sample management features support compliant handling and distribution of samples, and visit-related sample behavior is configured through visit settings and sample management setup. Salesforce Help describes sample management as enabling pharmaceutical companies to efficiently handle and distribute drug samples to providers, while the broader Customer Engagement setup includes Life Sciences mobile and visit configuration areas where these rules are applied.

The scenario includes two validation-style requirements. First, the consultant must specify which types of HCOs are eligible to receive samples. Second, the system must require users to enter a batch number for every sample drop. Both requirements are about enforcing rules during the sampling process, not about presenting product details or general sample item display.

Option A, Product Detailing Settings , is incorrect because product detailing is used to configure how products are discussed or presented during an engagement. It does not control HCO sample eligibility or mandatory batch entry. Option B, Samples and Items Settings , sounds related to sample availability, but the requirement is specifically about compliance validation. Option C, Sample and Validation Settings , is the correct subsection because it governs sample-related validation behavior, including eligibility and required information such as batch number entry. Therefore, the consultant should use Sample and Validation Settings .

=========

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.