Salesforce Als-Con-201 Dumps

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 aligned account lists in Agentforce Life Sciences for Customer Engagement are configured through account list settings, where the consultant defines how the list appears to users in the mobile experience. Salesforce describes account management features in Life Sciences Cloud as enabling users to organize, prioritize, and focus on accounts through lists and filters in the Customer Engagement app. The account list configuration controls which fields appear to reps so they can quickly understand account context without opening every account record.

In this scenario, the business wants field sales reps to see the most relevant account information directly in the aligned account list. After creating the account list, the consultant should configure it as the Default list type and select up to four visible fields as columns. This gives reps a concise, mobile-friendly view of the most important account details.

Option A is incorrect because configuring the Search list affects search-result display behavior, not the aligned account list columns. It also refers to up to five account fields, which does not match the aligned account list column configuration described in the question. Option B is incorrect because assigning ownership to field sales reps does not define the visible columns in the list. Column configuration is an admin setup activity, not something resolved by record ownership. Therefore, the consultant should set the list type to Default and configure up to four visible fields.

=========

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.

=========

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 B because the business requirement says the system must block additional distributions once the sample limit is met. In Salesforce Life Sciences sample management, sample limits are used to control how many samples can be distributed to HCPs based on rules such as product, time period, and visit limits. Salesforce Help describes sample management features as supporting efficient and compliant handling and distribution of drug samples, while sample limits are part of the setup used to govern sample distribution.

The distinction between enforcement types is important. A Warning allows the rep to continue after being alerted. A Threshold is typically used to identify when a limit is nearing or reaching a defined point, but it does not satisfy the requirement to prevent excess sample distribution. An Error is the strictest enforcement behavior because it stops the transaction when the configured limit would be exceeded.

Here, Cumulus Pharma needs hard compliance enforcement: maximum 5 units per HCP per calendar year and maximum 2 units per visit. Since the system must prevent field sales reps from exceeding those values, the consultant should set the sample limit enforcement type to Error . This ensures the disbursement cannot proceed when the annual or per-visit limit has already been reached.

=========

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.

=========

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

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

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

=========

Option A is the best answer because the requirement is specifically tied to the Next Best Customer user experience. Salesforce Life Sciences Cloud uses Next Best Customer to help sales reps understand and work with the top accounts in their territory by configuring the Next Best Customer component, quick actions, scores, and rationales. Salesforce Help also references Account Scores and Rationales for Next Best Customer as part of the setup path, which confirms that scores and supporting rationale are standard parts of the Next Best Customer capability.

The reps are not asking for a separate generic charting capability or a custom extension. They want to see the data that explains why a customer is recommended and how the score was derived. Embedded charts on the Next Best Customer component meet this requirement because they keep the rationale visualization directly in the same workflow where reps prioritize accounts and plan visits.

Option B is not the best answer because extending the Next Best Customer FlexCard would imply custom development or UI customization when the requirement can be met through the standard component experience. Option C is also not the best answer because the Chart Lightning Web Component Accelerator is a generic charting component, not the Life Sciences-specific Next Best Customer configuration for showing recommendation rationale. Therefore, embedded charts on the Next Best Customer component are the correct recommendation.

=========

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

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

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

=========

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

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

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

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

=========

Option 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 A because distance-based sorting in the Next Best Customer mobile component requires geolocation data on the account’s relevant address. Salesforce Help for configuring Next Best Customer settings for the mobile app states that, to ensure accounts are accurately sorted by distance, geolocation data must be captured for the primary address or preferred address. Salesforce Help also explains that if no preferred address is available, distance is calculated using the account’s primary Contact Point Address.

The reps already confirmed that location services are enabled on the iPad, so the issue is not the mobile device’s ability to determine the user’s current location. The missing piece is the account-side location data. If the primary or preferred address does not contain valid latitude and longitude values, the component cannot accurately calculate the distance between the rep and the account. As a result, accounts may appear with a distance of 0 or behave incorrectly when sorted by distance.

Option B is incorrect because a manual refresh does not solve missing geolocation data. Refreshing the component may reload records, but it cannot calculate distance without valid address coordinates. Option C is also incorrect because territory alignment is important for determining which accounts are relevant to the rep, but the distance calculation itself depends on geolocation data. Therefore, the root cause is missing geolocation data on the account’s primary or preferred address.

=========

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

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

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

=========

The correct answer is 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 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 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.

=========

The correct answer is A because Account Summarization can use different Cross-Object Field History Graph assignments by org or profile. Salesforce Help for Life Sciences Account Summarization states that administrators can create a Cross-Object Graph for Account Summarization and assign cross-object graphs to an org or profile. Salesforce also describes the Account Summarization workflow as using configured cross-object field history so summaries can include recent and relevant account changes from related objects.

In this case, KAMs see summaries that include Provider Visit and Medical Inquiry records, while field sales reps do not. Both groups have Read access to the objects, so object permission is not the root cause. The difference is most likely profile-based summarization configuration: the graph containing Provider Visit and Medical Inquiry data has been assigned to the KAM profile but not to the field sales rep profile.

Option B is incorrect because Account Summary generation in this scenario is driven by Cross-Object Field History Graph configuration, not membership in a Data 360 segment. Option C is also incorrect because the question explicitly says both user groups have Read access. View All is not the stated requirement for using a graph in summarization. Therefore, the issue is that the Cross-Object Field History Graph is not assigned to the field sales rep profile.

=========

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 B because the requirement is about making a Samples option appear in the Life Sciences mobile app sidebar, not about adding a related list to a Salesforce desktop page. Salesforce Help for setting up the Life Sciences Cloud mobile app specifically includes tasks for configuring the Visit Engagement Page and the Sidebar Menu . Salesforce also states that mobile app configuration changes are handled through the Life Sciences Commercial app’s Admin Console and mobile configuration areas, with metadata cache used to sync configuration to the mobile device.

The Samples tab is part of the mobile visit engagement experience. Enabling the relevant Samples sidebar setting in Mobile App Settings makes the Samples entry available in the sidebar so reps can record sample disbursements during a visit. This is the correct configuration approach because it controls the mobile navigation and visit sidebar behavior.

Option A is incorrect because adding the Product Disbursements related list affects a record page layout, but it does not create the mobile sidebar tab required by the field sales team. Option C is also incorrect because simply placing a Lightning web component on the Visit Lightning record page does not necessarily add a Samples entry to the Life Sciences mobile sidebar menu. The consultant should enable the Samples sidebar setting in Mobile App Settings.

=========

Option C is correct because the business requirement is based on the HCP’s relationship with a hospital, not the HCP’s primary address. Salesforce Life Sciences Cloud Affiliations help organizations understand and map relationships between Healthcare Providers and Healthcare Organizations. Salesforce Help also describes Territory Alignment for Affiliated Accounts, where affiliated accounts can be aligned to territories based on affiliation relationships. This fits the scenario: the HCP’s primary address points to San Francisco South, but their practice relationship with a hospital points to San Francisco North.

Option A is not the best answer because manually assigning the HCP to San Francisco North and excluding the record from future assignment rules creates a one-off exception. That may work temporarily, but it does not meet the requirement for automatic mapping based on practice location and affiliation. Option B is incorrect because it would use the HCP’s primary address zip code, which the scenario says is aligned to San Francisco South. That would produce the wrong territory.

An affiliation assignment rule aligns the HCP based on their relationship with the hospital, so the HCP can be mapped to San Francisco North when the hospital affiliation drives the business alignment. Therefore, the correct configuration is to set up an affiliation assignment rule based on the HCP-HCO relationship.

=========

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

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

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

=========

The correct answer is A because 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.

=========

Option A is correct because Life Sciences Workflow Management is designed to control what users can do at different stages of a Life Sciences process, including Medical Inquiries. Salesforce Help for configuring Life Sciences workflow paths states that admins define stage operation conditions that must be met to grant users access to operations. Salesforce also provides specific setup guidance for workflow stages used to manage Medical Inquiries, including adding actions to stage operations and configuring stage operation conditions.

This fits the requirement exactly. The access rules change depending on the Medical Inquiry’s stage: Draft, Assigned, Responded, Signed, or Submitted. Salesforce’s Inquiry object documentation confirms these inquiry statuses are standard values used in the Medical Inquiries process.

Option B is incorrect because criteria-based sharing rules on Case would not dynamically manage stage-specific CRUD behavior for the Life Sciences Inquiry workflow. Also, the question is about Medical Inquiries, not generic Case sharing. Option C is also incorrect because validation rules and dynamic page layouts can restrict or hide fields and actions, but they do not provide the standard stage-based security model required here. Therefore, the consultant should configure Stage Operations and Stage Operation Conditions within Life Sciences Workflow Management.

=========

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.

=========

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 B because the standard field that represents whether a received document is incoming or outgoing is Direction . Salesforce’s Life Sciences Cloud Developer Guide for the ReceivedDocument object lists direction values such as INCOMING — Incoming and OUTGOING — Outgoing , which directly matches the reporting requirement in the scenario.

The operations manager wants to analyze document volume based on whether consent forms are flowing into the organization from HCPs or being sent out to HCPs. That is a directional reporting requirement, not a document lifecycle or status requirement. Grouping the report by the Direction field allows the team to separate inbound consent forms from outbound documents using standard Salesforce data rather than creating a custom field or relying on interpretation.

Option A, Flow Type , is incorrect because the question is not asking about a business process type, document-processing flow, or automation path. It specifically asks for whether the document was incoming or outgoing. Option C, Document Status , is also incorrect because status would indicate where the document is in its lifecycle, such as received, processed, pending, or completed depending on configuration. Status does not define the direction of the document exchange. Therefore, the consultant should recommend grouping and filtering the report by the standard Direction field on Received Document.

=========

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, Action Plan Template Assignment, is correct. In Salesforce Life Sciences Cloud Key Account Management, strategic planning uses goal definitions and action plan templates to standardize account-planning execution. A Goal Definition represents the reusable strategic goal blueprint, such as “Secure Formulary Access.” An Action Plan Template defines the repeatable tactical tasks that should be generated when that goal is added to an account plan. The object that connects these two pieces is ActionPlanTemplateAssignment. Salesforce’s Life Sciences Cloud Developer Guide describes ActionPlanTemplateAssignment as the object to which the action plan template is associated, including examples such as a problem definition, goal definition, or care plan template. This directly matches the scenario: the action plan template must be associated with the goal definition so that importing the predefined strategic goal can generate the related tactical action plan.

Option A is not correct because “Action Plan Template Goal” is not the standard object identified in the Salesforce Life Sciences Cloud data model for this association. Option C is also incorrect because an Action Plan Template Participant would relate to participants, not the relationship between a goal definition and an action plan template. Salesforce’s Key Account Management Account Plan data model also includes Action Plan Template Assignment, Action Plan Template, Action Plan Template Item, and Goal Definition as part of the standard account-planning architecture.

Therefore, the correct object for linking the tactical action plan template to the reusable strategic goal definition is Action Plan Template Assignment.

=========

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 .

=========

The correct answer is C because Life Sciences Calendar can display visits where the user is not the owner but is included as an attendee or visitor. Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit so that colleagues participating in the same HCP interaction can be recorded and the visit can be shared with them. Salesforce also describes Life Sciences Calendar as a place to visualize and prioritize key activities, including visits and other events, and Trailhead explains that reps can view colleagues’ visits in shared calendars to coordinate engagement.

In this scenario, the rep bulk deleted several planned visits from their calendar. The two remaining visits are likely not visits owned and managed by the rep. Instead, they are visits owned by another user where the rep is included as an attendee. Because the calendar is configured to show attendee visits, those records continue to appear even after the rep deletes their own planned visits.

Option A is incorrect because the issue is not tied to the selected account list. Option B is plausible for some filtered-calendar behavior, but the key clue is that only some visits remain visible after bulk deletion. The standard Life Sciences explanation is that attendee visits can remain visible because they belong to a colleague and are displayed for collaboration. Therefore, the visits remain because the rep is added as an attendee.

=========

Option A is correct because Salesforce Help for setting up the Inquiry record page for Medical Inquiries explicitly states that, to view timeline details for inquiries, the consultant should drag the Timeline component to the page. The requirement in the question is to expose a chronological list of key events and changes associated with the inquiry. That is exactly the purpose of the Timeline component on the Medical Inquiries record page.

Salesforce also documents Enhanced Timeline for Life Sciences Cloud, explaining that the Enhanced Timeline component shows key events relating to a person or a record. This supports the use case of giving users a consolidated, chronological view of relevant inquiry activity, rather than requiring them to inspect multiple related lists or audit records separately.

Option B is not the best answer because field history tracking and the standard History component are used for field-level audit history, not the Life Sciences Medical Inquiries timeline experience. Option C is also incorrect because adding an Inquiry History related list would expose related records, but it would not provide the configured timeline component experience described in Salesforce’s Medical Inquiries setup documentation.

Therefore, the consultant must drag the Timeline component onto the Lightning record page and configure its component details for the Inquiry record page.

Option B, Dynamic Segmentation, is correct because the sample limit assignment must change automatically when the HCP’s Engagement Tier changes. Salesforce’s Life Sciences Cloud segmentation data model supports entities and relationships for creating and managing static and dynamic account segmentations. It also shows the connection between account segmentation, Healthcare Provider records, Product2, Provider Sample Limit, Provider Sample Limit Template, and Life Science Account Group Assignment. This confirms that segmentation is reusable in sample limit scenarios and can drive which sample limit template applies to a provider.

The important phrase in the question is “automatically update.” Because Engagement Tier is a calculated Account field that changes monthly, the consultant needs a rule-based segmentation approach. Dynamic Segmentation evaluates account criteria and can move accounts between groups as their data changes. When the HCP qualifies for the Tier 1 segment, the higher sample limit template can apply without an administrator manually reassigning the provider.

Option A, Account Segmentation, is too broad and does not specifically indicate the automatic, rule-driven behavior needed here. Option C, Sample Segmentation, sounds related to samples, but the key requirement is not merely grouping sample policies; it is dynamic reassignment based on changing account criteria. Therefore, Dynamic Segmentation is the correct configuration to support automatic sample limit changes as HCP engagement tiers change.

=========