Als-Con-201 Exam Dumps and Practice Questions

Option B is correct because Salesforce Life Sciences Cloud provides a standard Data Change Requests framework for governed master-data updates. The requirement is not simply to block a change or create a manual task; it is to route critical HCP data changes to a Data Steward for review before the change is applied. Salesforce's Life Sciences Cloud Account Management documentation describes Data Change Requests as a capability used to validate data changes by objects and fields and configure data changes by profile and record type. That aligns directly with controlled governance over fields such as Medical License Number.

The specific configuration object in the question, LifeSciDataChgPersonaDef, represents the persona-based data-change configuration. Salesforce's Developer Guide identifies LifeSciDataChgPersonaDef as part of Data Change Requests and includes the ChangeUpdateType picklist field. Setting ChangeUpdateType to DoNotApplyChangesImmediately means changes are not applied directly by the sales rep persona and can instead be managed through the data-change governance process.

Option A is not the best answer because a custom record-triggered flow would duplicate standard Life Sciences Cloud data-change governance and could create maintenance or compliance risk. Option C is also not ideal because a validation rule only blocks the update; it does not create the governed change-request process needed for Data Steward review. Salesforce's Data Change Requests data model includes Life Science Data Change Definition, managed fields, record types, persona definitions, and Life Science Data Change Request, confirming this is the intended standard architecture.

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.

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.

Option B is correct because Salesforce Life Sciences Activity Plans use weighted goals to measure activities differently based on business importance. Salesforce Help for creating Activity Plans states that, to track weighted goals, administrators create Provider Activity Goal Measure records to define weights, select Weighted Goal in the Type field, and assign a value in Activity Weight Value. This directly supports the requirement to measure high-impact activities differently from standard activities.

Activity Plans are designed to transform provider interaction strategies into actionable goals and targets for field representatives. When certain activities with specific HCPs are more strategically important, weighted goals allow those activities to contribute differently to plan performance. This is more precise than simply counting every activity equally.

Option A is incorrect because ''High Impact Goal'' is not the documented Type value for this configuration. The Salesforce Help wording identifies ''Weighted Goal'' as the Type value used for weighted measurement. Option C is also not correct because the documented field is Activity Weight Value, not Activity Impact. Even if a percentage-based concept sounds plausible, the standard configuration step is to set the Provider Activity Goal Measure Type to Weighted Goal and enter the weight value. Therefore, the consultant should select Weighted Goal for the Type field.

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.