Als-Con-201 Sample Questions Answers

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

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

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

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

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

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

Option C is correct because the issue occurs when an HCP joins a Remote Engagement call through an Experience Cloud site link. In this flow, the external HCP typically accesses the site as the Site Guest User, so the guest user needs the correct permission set to use the remote engagement experience. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that admins must assign permission sets to the guest user of the site, including Access Remote Engagement for Digital Experience . This directly matches the error in the question: the HCP reaches the site, but receives an insufficient permissions error.

Option A is incorrect because the Life Sciences Commercial Admin permission set is intended for administrative users, not the Site Guest User serving an unauthenticated Remote Engagement portal. Assigning broad admin permissions to a guest user would also be inappropriate from a security and compliance perspective. Option B is also incorrect because the requirement is not to license the HCP as a Customer Community Plus user. The scenario describes an HCP joining from a link, and the Salesforce setup guidance specifically identifies a permission-set assignment for the Site Guest User.

Therefore, the consultant should assign the Access Remote Engagement for Digital Experience permission set to the Experience Cloud Site Guest User.

=========

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.

=========

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 .

=========

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

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

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

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

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

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

=========

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

=========

Option A is correct because Account Summarization uses cross-object graphs to determine which related objects and relationships are included in generated summaries. Salesforce Life Sciences Account Summarization setup resources reference creating a cross-object graph for Account Summarization and assigning cross-object graphs to an org or profile. This supports persona-specific summary behavior because a graph can be configured with the additional custom objects and then assigned specifically to the KAM profile.

The requirement says the new information must be used only for the new KAM persona. That means the consultant should avoid changing the default or shared provider summary mapping used by other personas. By creating a separate cross-object graph from the template, adding the two custom insight and market-intelligence objects, and assigning that graph only to the KAM profile, the consultant isolates the new summary structure to the intended users.

Option B is not the best answer because globally updating Provider Summary Objects mapping could affect more than the KAM persona if the mapping is shared. Option C is also not the best answer because the key Account Summarization configuration pattern documented by Salesforce is graph creation and graph assignment to an org or profile. Therefore, the correct configuration is to create a new cross-object graph and assign it to the KAM profile.

=========

The correct answer is A from the available options, because the requirement is to control which user actions are exposed to different roles during the Medical Inquiry lifecycle. Salesforce Help for Medical Inquiries states that organizations can define relevant workflow actions for tasks users perform in the medical inquiry process, such as inquiry submission and assignment. Salesforce also describes a compliant role separation where field sales reps can submit medical inquiries, while Medical Science Liaisons can assign and respond to them.

The ideal Salesforce Life Sciences configuration pattern is to use Medical Inquiry workflow actions and workflow paths to control status transitions, actions, and permissions. However, among the provided answer choices, record types with role-specific page layouts is the only option that directly supports restricting the available buttons and actions by user role. This enables sales users to see only draft, sign, and submit actions, while MSL users see only assignment and response actions.

Option B is incorrect because a formula field can calculate or display logic, but it cannot enforce workflow actions or user interaction permissions by itself. Option C is also incorrect because a Flow action could add custom logic, but it is not the standard configuration approach for restricting Medical Inquiry lifecycle actions. Therefore, the best available answer is A .

=========

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

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

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

=========

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

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

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

=========

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

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

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

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

=========

Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep’s targets.

Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.

Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.

=========

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

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

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

=========

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.

=========

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 B because the product must be enabled for discussion in the visit-detailing experience. Salesforce’s Life Sciences Visit Management developer documentation states that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples. Salesforce Trailhead also explains that Life Sciences Cloud uses product administration and product-message configuration to ensure reps only promote and discuss therapies within approved guardrails.

The scenario says the product exists in Salesforce, but it does not appear when the rep tries to add it to the Product Detailing section during a visit. That means the issue is not product creation; it is visit-discussion eligibility. The consultant should configure Product Discussion Settings in the Visit Administration area so Immunexis is available for product detailing and visit discussions.

Option A is incorrect because Territory Product Alignment Rules determine which products are aligned to territories, but the question specifically says the product must be explicitly enabled for use in visit discussions. Territory alignment alone does not guarantee the product appears in the Product Detailing search. Option C is also incorrect because Visit Record Type Mappings control record-type behavior, not whether a product can be discussed. Therefore, the correct configuration is Product Discussion Settings .

Option A is correct because Salesforce Life Sciences Account Summarization uses field history tracking to include the latest changes for configured fields. Salesforce Help states that, to get summaries of the latest changes in a record, history tracking must be enabled for the fields configured in the Account Summarization template. This directly matches the issue: the summaries include related data, but recent updates to specific HCP Account fields are missing. The consultant must enable history tracking for the relevant fields so Agentforce can use those tracked changes when generating the account summary.

Feed tracking is not the best answer because Chatter feed tracking is primarily used to publish field changes to the record feed for collaboration and visibility. It does not satisfy the specific Account Summarization requirement documented by Salesforce. Field Audit Trail is also not correct for this scenario. Field Audit Trail is a Salesforce Shield capability used for long-term retention and audit-policy management of field history data, but the Account Summarization setup requirement is specifically field history tracking for the fields included in the template. Salesforce’s Account Summarization Data Setup documentation also confirms that the Provider Summary Lightning App Builder component can be configured to enable history tracking for fields included in the information summary.

Therefore, the consultant should enable history tracking for the Account fields configured in the Account Summarization template.

=========

The correct answer is C because Provider Account Territory Information is the standard object used to store provider-level territory information, including calculated territory-specific visit metrics. Salesforce Help states that the Account Address batch job creates Provider Account Territory Information records and calculates values such as year-to-date visits , next visit, and last visit. This directly matches the requirement to track the HCP’s Year-to-Date Visit Count separately by territory assignment.

The key detail is that the HCP is assigned to multiple territories. A single account-level field would not be sufficient because the visit count must be different depending on the territory relationship. Provider Account Territory Information supports this by storing data at the intersection of provider account and territory, allowing the same HCP to have separate calculated values for each assigned territory.

Option A, Provider Account Territory Summary , sounds plausible because it includes “summary,” but the Salesforce-documented batch process specifically creates Provider Account Territory Information records for territory-specific metrics. Option B, User Territory Affiliation Information , is not correct because the requirement is about an HCP’s territory-specific visit count, not user-territory affiliation data. Therefore, the consultant should use Provider Account Territory Information .

=========

Option C is correct because Product Batch Item is the Salesforce Life Sciences Cloud record that connects a production batch to a specific product inventory location or user inventory context. Salesforce Help describes creating Product Batch Items for sample inventory and states that a product batch item establishes the relationship between the Product, Life Science Marketable Product, Production Batch, Product Batch Item, Location, and User. This directly matches the scenario: Cumulus Pharma needs to allocate samples from a specific production batch to a field sales rep’s inventory and track remaining quantity at the batch level.

The ProductBatchItem object also includes the RemainingQuantity field, which supports the requirement to track remaining quantity by batch. Salesforce’s Life Sciences Cloud Developer Guide documents ProductBatchItem and identifies RemainingQuantity as a field on the object.

Option A is incorrect because simply assigning a Production Batch to the Life Sciences Marketable Product does not allocate batch-specific stock to a rep’s inventory. Visit submissions can update inventory, but the batch allocation must already be represented correctly. Option B is also incorrect because updating Quantity on Hand on Product Item only changes general product inventory at a location. It does not establish the production-batch relationship needed for batch-level tracking. Therefore, the consultant should create a Product Batch Item, associate it to the rep’s Product Item, mark it Active, and enter the Remaining Quantity.

=========

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.

=========

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

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

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

=========

The correct answer is B because Life Sciences mobile app configuration changes must be synchronized to the mobile experience through metadata cache generation. Salesforce Help states that configuration changes are synced to the Life Sciences Cloud mobile app by generating a metadata cache, and that the generated metadata cache includes object schemas and related metadata required by the mobile app. Salesforce also states that a new metadata cache should be generated when administrators update Lightning record pages, page layouts, object or schema changes, new or modified feature settings, or related mobile configuration.

In this case, the consultant correctly updated the Account Lists configuration in the Admin Console to use a new Account field set. The reason the app still shows the old Account List layout is that the mobile app has not received the updated metadata. Running the Mobile Metadata Cache update pushes the refreshed configuration to the app so that field sales reps can see the new Account List columns.

Option A is incorrect because the issue is not with the Account Lightning record page. The change was made to Account Lists in the Admin Console, not to the record page layout. Option C is also incorrect because deleting and reinstalling the app is a user-side workaround and does not publish new admin metadata. The proper administrator action is to run the metadata cache update.

=========

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

=========

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

=========

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

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

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

=========

The correct answer is B because the requirement combines two controls: a territory-level cap for a product during a defined period and a per-visit disbursement limit for sales reps. Salesforce Life Sciences documentation for Territory Product Quantity Allocations states that these allocations are used to manage sample product distribution to healthcare professionals, and the setup guidance specifically references the Max Disbursement Limit Quantity as the maximum amount a sales rep can disburse in a given visit.

A Territory Product Quantity Allocation record is designed for the exact scenario described: controlling how much of a specific product is allocated to a territory and limiting how much can be disbursed during a visit. The consultant would define the allocated quantity for Immunexis 50mg for the high-growth territory for the next quarter and set the Max Disbursement Limit Quantity to 50 so that an individual field sales rep cannot hand off more than 50 units in one visit.

Option A is incorrect because setting a product-level maximum sample order quantity would apply too broadly across the organization and would not satisfy the territory-specific allocation requirement. Option C is not the best answer because an Advanced Sample Limit Template at the Healthcare Provider account level controls limits by HCP/account, not the total quantity available to a territory. Therefore, Territory Product Quantity Allocation is the correct administrative configuration.