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

Option A is correct because Remote Engagement with Twilio uses Salesforce named and external credentials, and users need access to the external credential principal to use those credentials. Salesforce Help for configuring Twilio credentials in Life Sciences Remote Engagement states that the Life Sciences Customer Engagement managed package includes the named and external credentials for Twilio. The same Salesforce Help result specifically references selecting External Credential Principal Access as part of the setup. This aligns directly with the error: the field sales rep cannot access the video service credentials, even though the Life Sciences Field Sales Representative permission set has been verified.

Option B is incorrect because the solution is not to manually provide the rep with a Twilio authentication token. That approach would be insecure and inconsistent with Salesforce’s named/external credential model. Credentials should be managed centrally through Salesforce configuration, not distributed directly to end users. Option C is also incorrect because “Twilio Users Public Group” is not the documented permission mechanism for accessing the video service credentials in Life Sciences Cloud Remote Engagement.

Salesforce’s broader named credential security documentation also explains that external credential principals can be mapped to permission sets and profiles so users can make callouts to external systems with the right access. That supports the need to grant External Credential Principal Access rather than changing the rep’s profile or sharing tokens manually.

=========

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 .

Option B is correct because Salesforce Life Sciences Cloud for Customer Engagement provides sample limit templates that help organizations enforce country-specific sampling rules. Salesforce Help states that Life Sciences Cloud includes a generic sample limit template and several country-specific templates by default. These templates are designed to support sample governance where regulations vary by country or region. In the scenario, Cumulus Pharma must comply with regional laws, such as Belgian requirements, while maintaining GxP standards for sample distribution. Using the default country-specific templates is the most appropriate standard configuration because it applies predefined sample-limit governance based on regional compliance expectations.

Option A is not the best answer because Territory Product Quantity Allocation is used to allocate product quantities by territory, but the requirement is about legal and GxP compliance by country. Allocation controls available quantities; it does not, by itself, represent the compliant sample-limit template framework. Option C is incorrect because manually adjusting Quantity On Hand on Product Item would change inventory balances directly and could create audit, traceability, and compliance risk. Product Item represents stock at a location, but manual quantity changes are not the correct way to enforce regional sampling laws.

Therefore, the consultant should use the default country-specific sample limit templates so sample distribution follows regional compliance rules while remaining aligned with Life Sciences Cloud’s controlled sample-management framework.

=========

The correct answer is A because Salesforce’s Remote Engagement setup guidance for Life Sciences Cloud specifically identifies the Experience Cloud site as the place where language support is configured for remote engagement experiences. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that, for language support, the administrator should select Components and drag the Language Selector component to the page. This directly supports the requirement for HCPs to review and accept terms and conditions in multiple languages when joining remote visits.

Remote Engagement involves an HCP-facing experience, not only a sales-rep mobile action. The terms and conditions are presented through the Experience Cloud site used for the remote session, so the language-selection capability must be available there. Adding the Language Selector lets the HCP choose the appropriate language in the site experience before reviewing the terms.

Option B is incorrect because configuring the Start Remote Session quick action may help reps launch or manage remote sessions, but it does not provide the HCP-facing multilingual site control required for terms and conditions. Option C is also incorrect because a survey can collect feedback or preferences, but it is not the Salesforce-recommended way to localize the terms-and-conditions experience. The correct configuration is to add the Language Selector component to the Experience Cloud site.

=========

Option C is correct. Salesforce Life Sciences Cloud documentation for Synchronization Management describes Simulation Mode as the feature used to proactively find and fix synchronization problems before they affect users. This is directly aligned with the question’s wording: the consultant must identify potential synchronization transaction failures that could prevent recently created records from being available offline in the Life Sciences mobile app. Simulation Mode helps admins validate synchronization behavior in advance, rather than waiting for sales users to encounter missing or failed offline records.

Option B is not the best answer, even though the question included it as the proposed answer. Event Monitoring can be useful for broader Salesforce activity monitoring, but the Salesforce Life Sciences synchronization documentation points specifically to Synchronization Management and Simulation Mode for identifying and resolving sync problems in the Life Sciences mobile app context. Option A is also incorrect because sending warning emails to sales users would notify people after a problem or warning occurs; it does not test synchronization transactions or identify potential failures before users are impacted.

Therefore, to identify potential synchronization transaction failures and reduce offline data issues for field sales users, the consultant should leverage Simulation Mode to test transactions.

=========

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.

=========

Option C is correct because Salesforce Life Sciences Cloud supports manual territory alignment for affiliated accounts. Salesforce Help for Territory Alignment for Affiliated Accounts states that a user’s territory determines which accounts they can view and manage, and that users can manually align an affiliated account to their territory. The broader Affiliations documentation also explains that affiliation alignment rules can automatically align affiliated accounts, but the scenario specifically asks for manual alignment by field users when needed.

The correct Admin Console setting is therefore the one that enables users to align affiliated accounts to the user’s territory. This setting allows reps working with complex HCO/HCP affiliation networks to bring relevant affiliated accounts into their current territory alignment when the relationship is valid for their business process.

Option A is not the best answer because the requirement is not to align accounts outside the user’s territory. It is to let users align affiliated accounts to their own current territory. Option B is also incorrect because searching for accounts outside the user’s territory only affects discoverability. It does not grant the ability to perform the actual affiliated-account alignment. Therefore, the consultant should enable “Enable users to align affiliated accounts to the user’s territory” in Account Management > Affiliation.

The correct answer is C because an Action Plan Template Assignment connects predefined action-plan tasks to reusable planning objectives so Key Account Managers can import standardized objectives into account plans with tactical steps already attached. Salesforce Help for Life Sciences Key Account Management explains that a Goal Definition represents a broad business objective that can be reused across global, national, and territory levels. It also states that when creating account plan objectives, users can import templates and choose goal definitions with action plans and assessment tasks to add to account plans.

The key phrase in the scenario is “with predefined tactical steps.” A high-level corporate objective alone would not be enough. The organization also wants repeatable execution tasks that KAMs can bring into individual account plans. Creating an Action Plan Template Assignment supports this by associating the action plan template with the goal definition, so the imported objective includes the structured actions needed for execution.

Option A, Account Plan Objective Link , is incorrect because it suggests linking an objective after the fact rather than defining a reusable objective with tactical steps. Option B, Goal Definition Product , is also not the best answer. A product association may be useful for a product launch, but it does not provide the predefined action-plan tasks required by the business process. Therefore, the consultant should create an Action Plan Template Assignment .

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 the scenario is asking for structured capture of field observations, sentiment changes, and competitive intelligence gathered during HCP interactions. Salesforce Life Sciences Cloud includes Medical Insights for capturing, analyzing, and sharing insights with medical, R & D, and commercial teams. Salesforce’s Life Sciences Cloud pharma materials describe the capability as helping teams detect, capture, analyze, and share medical insights across R & D and commercial teams, while Salesforce Help also provides setup guidance for Medical Insights in Life Sciences Cloud.

Medical Insights is the best fit because the business requirement is not merely to log a question from an HCP. It is to capture structured observations that can reveal commercial risks, such as competitor activity, sentiment shifts, or emerging concerns. These insights can then support early risk identification and mitigation planning.

Option A is incorrect because Medical Inquiries are used to capture, manage, and respond to critical questions from HCPs, including formal inquiries that may require medical information handling. Salesforce describes Medical Inquiries as a way to capture, manage, and respond to critical questions from HCPs. That is different from capturing strategic field insights. Option B is also incorrect because Account Ratings help prioritize or segment accounts, but they are not the structured feature for recording competitive intelligence and sentiment observations. Therefore, Medical Insights is the correct feature.

=========