Free Salesforce Als-Con-201 Practice Exam with Questions & Answers | Set: 3

The correct answer is C: Perform audits of Inventory Count Assessment records user permission. In Life Sciences Cloud sample inventory management, Inventory Count Assessment records are used to support inventory count and audit processes. Salesforce documentation distinguishes between conducting or performing an audit and requesting an audit. The wording in the question asks which permission is needed for a user to conduct a self-audit of their inventory count. Because the action is to perform the audit, the required permission is the user permission that allows users to perform audits of Inventory Count Assessment records.

Option A is incorrect because the Life Sciences Field Sales Representative permission set alone should not be assumed to include every inventory audit capability by default. Salesforce Life Sciences sample inventory features use specific user permissions for different inventory audit actions, so the named permission is the safer and more precise answer. Option B is incorrect because “Request audits of multiple Inventory Count Assessment records” is related to submitting or requesting audits, especially peer-audit-style workflows, not personally conducting the self-audit. Salesforce Help notes that requesting a peer audit requires the Request Multiple Inventory Count Assessment Audits user permission, which confirms that request permission is separate from the permission to perform audits.

Therefore, for a self-audit where the user is actually conducting the audit activity, the correct permission is “Perform audits of Inventory Count Assessment records.”

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 .

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 C is correct because Medical Insight upvotes are handled through the UserReaction object and related out-of-the-box logic. Salesforce’s Life Sciences Cloud Developer Guide states that UserReaction represents a user’s reaction to a medical insight, such as an upvote or downvote, and that these reactions are used to identify trending insights. This directly supports the scenario because the problem involves duplicate upvotes and the inability to see total upvote counts on Medical Insight records.

Salesforce’s MedicalInsight object documentation also references fields related to ranking and upvotes, including a default rank determined based on linked insights and their upvotes. This confirms that upvote behavior is part of the standard Medical Insights data model rather than something that should be rebuilt manually.

Option A is not the best answer because MedicalInsightValidationHandler sounds focused on validating Medical Insight records generally, not specifically managing user reactions, duplicate reactions, or upvote counts. Option B is also not preferred because custom validation rules and a new roll-up summary field would duplicate behavior that Salesforce provides through the Medical Insights user-reaction framework. The requirement asks for the out-of-the-box configuration, so the consultant should activate the UserReactionMedicalInsightHandler to manage upvote reactions consistently and support the total-count behavior.

=========

Option B is correct. In Agentforce Life Sciences for Customer Engagement, the visit engagement screen in the mobile app can be customized so field users have quick access to key visit information and related records while preparing for or conducting a visit. Salesforce Help identifies the Life Sciences Cloud mobile app setup area as the place where admins configure the visit engagement page, sidebar menu, visit information fields, visit record types, quick actions, and other customer engagement mobile settings. The sidebar menu is intended to provide focused, in-context access to the most relevant information, not to replicate every possible related list from the desktop experience.

The maximum number of custom object-related lists that can be added to the sidebar is five. This limit helps preserve mobile usability and keeps the visit engagement experience streamlined for field sales reps using an iPad or mobile device during HCP or HCO interactions.

Option A is incorrect because 10 related lists would create a heavier mobile interface than the supported sidebar configuration allows. Option C is also incorrect because the product allows more than two custom object-related lists. Therefore, when configuring the visit engagement sidebar, the consultant should plan for a maximum of five custom object-related lists and prioritize the most important related records for the field workflow.

=========

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.

=========

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

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

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

=========

Option B is correct because 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.

=========

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 B is correct because the requirement is specifically about making Consent Management data available in the Life Sciences mobile app. Salesforce Help for Consent Management states that admins must create object metadata cache configuration for supported Consent Management objects and generate a metadata cache so sales reps can view and update consent data. Salesforce also has a dedicated setup topic for creating Object Metadata Cache Configuration, which is accessed from the Life Sciences Commercial app Admin Console under Mobile.

This is important because the Life Sciences mobile app depends on generated metadata cache so that configured objects, fields, and layouts are available to field users on iPad and mobile workflows. Without the metadata cache for the Consent Management objects, reps may not be able to access or update consent preferences during visits, even if the consent model itself is configured correctly.

Option A is not the best answer because Subscription Filtering Fields help control filtering behavior for consent subscriptions, but they do not make the consent objects available in the mobile app. Option C is also incorrect because configuring a desktop Lightning record page does not satisfy the Life Sciences mobile app metadata requirement. Therefore, the consultant should create the object metadata cache configuration for Consent Management objects and generate the metadata cache.

=========