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

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 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 A because Salesforce Life Sciences Territory Management batch jobs can be scheduled with an hourly frequency. Salesforce Help for running Territory Management jobs states that, from the Life Sciences Commercial Admin Console, the job can be scheduled hourly, every selected hours , by selecting the hour from the dropdown. This confirms that hourly scheduling is a supported automatic execution option for Territory Management batch jobs.

Territory Management batch jobs are important because Life Sciences territory configuration affects field execution, account alignment, provider access, and downstream engagement processes. Scheduling these jobs automatically helps ensure that territory-related processing runs on a predictable cadence without requiring administrators to manually start each batch job. When the question asks how often the jobs can be scheduled to execute automatically, the available option that matches Salesforce’s documented scheduling capability is Hourly .

Option B, Every 12 hours , may sound plausible because some enterprise batch processes use longer intervals, but it is not the best answer because Salesforce’s documented configuration describes hourly scheduling and selecting the hour interval. Option C, Monthly , is also incorrect because monthly execution would be too infrequent for many territory-management operational updates and is not the option reflected in the documented batch-job scheduling guidance. Therefore, the consultant should identify Hourly as the correct scheduling frequency.

The correct answer is A because Salesforce Life Sciences Field Email allows field users to add colleagues as CC recipients. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails to healthcare professionals and healthcare organizations from their workflow, select an email template, and add colleagues as CC recipients.

This distinction matters for compliance. In Life Sciences engagement, HCPs and HCOs are the intended external recipients of approved email communications. The CC field is not intended as a free-form way to add additional HCPs. Instead, CC is used for internal collaboration or visibility, such as copying a colleague involved in the account, territory, or follow-up process. This helps keep HCP communications controlled, trackable, and aligned with approved email workflows.

Option B is incorrect because it suggests both HCPs and colleagues can be CC’d. Although emails are sent to HCPs or HCOs, Salesforce’s documented CC behavior specifically references colleagues as CC recipients. Option C is also incorrect because HCPs are the primary external recipients, not the users who should be copied in the CC field. Therefore, when sending email from the Agentforce Life Sciences mobile app, field sales reps can CC colleagues .

=========

The correct answer is B because Life Sciences Cloud supports configuring quick actions for the mobile app through the Admin Console. Salesforce Help for Medical Insights states that Medical Insights can be made available to users in the Life Sciences mobile app so users can view their own insights and insights shared with them. Salesforce Help also describes Quick and Custom Action Management as the way to simplify user experiences in Salesforce and the Life Sciences for Customer Engagement mobile app by leveraging quick actions and custom actions.

The requirement is not merely to expose the Medical Insights tab. The rep must be able to quickly report a medical insight while managing a visit on an iPad. Configuring the Create Medical Insights quick action in the Admin Console makes the action available in the mobile workflow where reps need it. This supports fast, in-context capture of field observations during a visit.

Option A is incorrect because creating a custom action and custom flow adds unnecessary complexity when the standard quick action can be configured declaratively. Option C is also not the best answer because editing the Visit page layout and adding a generic standard action may not make the action available correctly in the Life Sciences mobile app experience. The Admin Console is the correct configuration point for mobile quick actions. Therefore, the consultant should configure the Create Medical Insights quick action using the Admin Console.

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.

=========