Pass the Salesforce Salesforce Consultant Als-Con-201 Questions and answers with CertsForce

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.

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 .

=========

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.

=========

Option B is correct because Life Sciences Cloud for Customer Engagement uses Life Sciences-specific Next Best components for the mobile and account-profile experience. Salesforce’s Life Sciences Next Best documentation explains that Next Best Action suggests timely actions such as visits and emails, and the Life Sciences Customer Engagement data model includes Life Sciences-specific recommendation objects such as Territory Account Recommended Action, Territory Account Product Message Score, and Territory Account Score. These are not the same as the generic Einstein Next Best Action component and strategy experience.

The question states that the recommendation data is already loaded and synced to mobile. That removes the most likely data-load or synchronization issue. If the data exists but the component is not visible on the account profile, the issue is most likely the wrong component placement. The page must use the Life Sciences Next Best Action component that is designed to render Life Sciences recommendations in the Life Sciences mobile app.

Option A is not the best answer because inactive strategy logic would generally prevent recommendations from being generated or returned, but the scenario confirms the recommendation data is present. Option C is also less likely because a permission problem would typically prevent access to the recommendation records or data, not specifically indicate that the component itself was configured incorrectly. Therefore, the consultant should replace the generic Einstein Next Best Action component with the Life Sciences Next Best Action component.

=========

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.

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.

=========

The correct answer is C because Salesforce Life Sciences Sample Inventory Management is intended to provide a unified view of sample-related inventory activity. Salesforce documentation describes Sample Inventory Management as providing a unified view of transactions, shipments, inventory counts, and assigned batches, helping users stay on top of items requiring attention. This directly matches the requirement for reps to monitor batch assignments, received inventory, disbursements, transfers, and returns from one experience rather than navigating across multiple object tabs.

To make that experience available in the Agentforce Life Sciences mobile app, the consultant should expose the Sample Inventory Management dashboard through the user’s navigation configuration. Adding it to Navigation Items ensures the field sales rep profile can access the dashboard from the mobile app. This is better than building a custom report type because the standard dashboard is purpose-built for Life Sciences sample inventory workflows and already aligns with the sample inventory data model and operations.

Option A is not the best answer because a custom report chart would be less functional than the standard inventory dashboard and would not provide the operational interface reps need. Option B is also incomplete. The Inventory Operations Timeline is useful for viewing transaction history, and Salesforce describes it as an overview of transactions and product requests in chronological order, but it does not provide the full dashboard experience for assigned batches, inventory counts, shipments, and operational status.

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

=========

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 .

=========