Als-Con-201 Exam Dumps - Salesforce Consultant Questions and Answers

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 Remote Engagement email notifications depend on email templates configured for the relevant automated email invitation context/action. Salesforce Help for uploading and creating email templates in Life Sciences Cloud includes configuration fields for automated email invitation context and action. For a rescheduled or updated virtual visit, the email template must be configured so the automated email invitation action corresponds to the update event.

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

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

=========

Option A is correct because the Medical Inquiries record page setup depends on configuring the Inquiry Question Answer related-list experience with the correct field set. Salesforce Help for setting up the Inquiry record page for Medical Inquiries instructs admins to add tabs and Lightning components to the Inquiry page. It also specifically references the “Inquiry Question Answer” tab and requires the field set name for the Inquiry Question Answer field set. That means the field set must exist before the consultant can properly configure the Medical Inquiries record page component.

This requirement fits the business process described in the question. Field sales reps create and submit medical inquiry requests, and MSLs respond to the inquiry questions. The Inquiry Question Answer object supports the question-and-answer details used by the record page component, so the field set determines which fields appear to users when viewing or entering inquiry responses.

Option B is not the best answer because a support process is typically associated with Case status handling. While medical inquiries may be operationally similar to case management, the Salesforce Life Sciences setup step in this question is specifically about the Medical Inquiries record page. Option C is also not correct because syncing statuses between Case and Medical Inquiries is not identified as the prerequisite for configuring the page. Therefore, the consultant should first create the required field set for the Inquiry Question Answer object.

=========

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.

=========

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

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

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

Option A is correct because Life Sciences Cloud Visit Management includes an Admin Console configuration called Map Visit Types to Accounts. This configuration is designed to associate the correct Visit record type with the relevant Account type. Salesforce Life Sciences setup resources reference Visit Management Admin Console tasks, including Configure Visit Settings, Activate Trigger Handlers, Schedule Visit Jobs, and Map Visit Types to Accounts. That mapping is the appropriate configuration when a company has separate visit processes for HCOs and HCPs.

In this scenario, Cumulus Pharma already has separate Account record types and separate Visit record types. The missing configuration is the relationship between those two sets of record types. Mapping Visit Types to Accounts ensures that, when a sales rep creates a visit from an HCO account, the HCO visit process is used, and when the rep creates a visit from an HCP account, the HCP visit process is used.

Option B is not the best answer because trigger handlers enable underlying Visit Management automation, but they do not define which Visit type is associated with each Account type. Option C is also incorrect because page layouts control what users see on record pages; they do not determine the visit process or Visit record type mapping. Therefore, the consultant should configure mappings in Map Visit Types to Accounts.

=========

Option A, Provider Account Territory Summary, is the best answer because the requirement is to store summarized, territory-specific account metrics. The HCP belongs to more than one territory, and Cumulus Pharma must track Year-to-Date Visit Counts independently for each territory. Salesforce’s Life Sciences Account Management data model includes both Provider Account Territory Information and Provider Account Territory Summary as standard entities for managing healthcare provider and organization accounts, related profiles, and territory-specific information.

Provider Account Territory Summary is the object designed for summarized metrics at the provider-account-and-territory level. That makes it the appropriate place for values such as Year-to-Date Visit Counts, which are calculated or aggregated metrics rather than the raw alignment relationship itself.

Option C, Provider Account Territory Information, is related but not the best answer. Salesforce’s Developer Guide describes ProviderAcctTerritoryInfo as representing engagement data between an account and a user within an assigned territory, including items such as next provider visit date and preferred address. However, the question asks for territory-specific account metrics, not general engagement information between a user, account, and territory. Option B, Provider Account Territory Association, is also not correct because the issue is not simply associating an account to a territory. The HCP is already assigned to both territories. The need is to store independent summarized metrics for each territory. Therefore, Provider Account Territory Summary is the correct standard object.

=========

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

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

Option C is correct. Salesforce Life Sciences Cloud documentation for Synchronization Management describes Simulation Mode as the feature used to proactively find and fix synchronization problems before they affect users. This is directly aligned with the question’s wording: the consultant must identify potential synchronization transaction failures that could prevent recently created records from being available offline in the Life Sciences mobile app. Simulation Mode helps admins validate synchronization behavior in advance, rather than waiting for sales users to encounter missing or failed offline records.

Option B is not the best answer, even though the question included it as the proposed answer. Event Monitoring can be useful for broader Salesforce activity monitoring, but the Salesforce Life Sciences synchronization documentation points specifically to Synchronization Management and Simulation Mode for identifying and resolving sync problems in the Life Sciences mobile app context. Option A is also incorrect because sending warning emails to sales users would notify people after a problem or warning occurs; it does not test synchronization transactions or identify potential failures before users are impacted.

Therefore, to identify potential synchronization transaction failures and reduce offline data issues for field sales users, the consultant should leverage Simulation Mode to test transactions.

=========