Salesforce Als-Con-201 Exam Dumps

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.

=========

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 C is correct because an Ad Hoc inventory count assessment is used for an unscheduled inventory check, and Salesforce Life Sciences Sample Inventory Management supports discrepancy adjustments when the counted quantity differs from the system quantity. Salesforce Help states that when a discrepancy is recorded in an inventory count, Sample Inventory Management adjusts the system count positively or negatively to match the actual count. In this scenario, the rep physically counts 95 units while the system shows 100, so the compliant process is to submit the count and let the system create the adjustment transaction for the five-unit negative discrepancy.

Salesforce Help also describes Inventory Count Assessment as the object that captures the overview of the count, including where the assessment occurs and the assessment type. This supports using an inventory count assessment rather than manually changing inventory balances.

Option A is not correct because the missing units were not returned to the distribution center; creating a return would misrepresent the physical inventory event. Option B is also incorrect because an Initial inventory count is used for establishing an initial count, not for reconciling an unscheduled discrepancy after inventory already exists. Therefore, the correct compliant action is to submit an Ad Hoc inventory count assessment and let the system generate the adjustment transaction.

=========

Option B is correct because Salesforce Life Sciences Medical Inquiries uses workflow actions and persona/profile-based configuration to control who can perform specific inquiry actions, such as assigning and responding. Salesforce Help states that, before setting up Medical Inquiry, admins must make sure the required user profiles, licenses, and permission sets are in place. It also describes that medical science liaisons can assign and respond to inquiries, which confirms that these actions are intended to be controlled by role or persona.

Salesforce's Life Sciences workflow documentation also identifies workflow actions and workflow stages as part of the Medical Inquiry management setup. The Medical Inquiries workflow setup includes action buttons, workflow stages, stage operations, and conditions, allowing admins to expose or restrict actions based on configured roles and workflow state.

Option A is not the best answer because the requirement is not simply to grant a broad app permission; it is to ensure that only a designated persona can perform the assign and respond actions in the controlled Medical Inquiry process. Option C is incorrect because a custom formula field only affects display logic and does not enforce the standard workflow-action permission model. Formula-based visibility also creates compliance risk because it can hide buttons without truly governing the underlying operation. Therefore, the consultant should create workflow actions and associate those actions with the appropriate profiles in the Life Sciences Admin Console.

=========

The correct answer is A because Today's Pace is tied to the Activity Plan's calculation behavior, not the home page component itself. Salesforce describes Activity Plans as a way to establish a strategic activity plan and define activity goals for sales representatives over a specific period. Salesforce's Life Sciences Activity Plans developer guidance also describes Activity Plans as allowing administrators to define goals for specific employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

When the business wants Today's Pace calculated based on working days, that logic should be defined where the activity plan is created and governed. Selecting Working Days in the Today's Pace Calculation Type field ensures the pacing metric uses working-day logic for the plan instead of simply counting all calendar days. This is the correct place to configure the calculation because Today's Pace reflects plan progress against the plan timeline.

Option B is incorrect because editing the home page component only controls presentation. A component can display the metric, but it should not be the source of the calculation rules for the underlying Activity Plan. Option C is also not the best answer because the requirement is not a broad global enablement setting; it asks how to calculate Today's Pace for the relevant Activity Plan. Therefore, the consultant should configure the calculation type directly on the Activity Plan by selecting Working Days.