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

Option B is correct. In Salesforce Life Sciences Cloud Remote Engagement, the standard object used for the executed video engagement details is the remote-call/video-call record. Salesforce’s Life Sciences Developer Guide includes the VideoCall object for Remote Engagement and describes it as storing important information about the remote engagement, including its relationship to the associated provider visit. This aligns with the requirement to verify that the remote interaction occurred and review engagement metrics after the call concludes.

Provider Visit is related to the customer interaction and can represent the overall HCP visit context, but it is not the most precise object for the executed video-call details. The remote engagement session itself needs its own object because it can store video-specific information such as call status, timing, service details, and other remote-session metadata.

Option C, Video Log, is not the correct standard Life Sciences object name in the Salesforce documentation. “Video Log” sounds like a generic audit or logging object, but the documented Remote Engagement object is VideoCall. Since the answer options use “Remote Call” rather than “VideoCall,” Remote Call is the closest and intended answer for the standard remote engagement execution record. Therefore, the consultant should use the Remote Call/VideoCall record to review the executed Remote Engagement details.

=========

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 .

=========

The correct answer is B because the standard field that represents whether a received document is incoming or outgoing is Direction . Salesforce’s Life Sciences Cloud Developer Guide for the ReceivedDocument object lists direction values such as INCOMING — Incoming and OUTGOING — Outgoing , which directly matches the reporting requirement in the scenario.

The operations manager wants to analyze document volume based on whether consent forms are flowing into the organization from HCPs or being sent out to HCPs. That is a directional reporting requirement, not a document lifecycle or status requirement. Grouping the report by the Direction field allows the team to separate inbound consent forms from outbound documents using standard Salesforce data rather than creating a custom field or relying on interpretation.

Option A, Flow Type , is incorrect because the question is not asking about a business process type, document-processing flow, or automation path. It specifically asks for whether the document was incoming or outgoing. Option C, Document Status , is also incorrect because status would indicate where the document is in its lifecycle, such as received, processed, pending, or completed depending on configuration. Status does not define the direction of the document exchange. Therefore, the consultant should recommend grouping and filtering the report by the standard Direction field on Received Document.

=========

The correct answer is A because Remote Engagement video traffic requires Twilio endpoints to be trusted by the Salesforce org. Salesforce Help for setting up Twilio for Remote Engagement states that participants can connect to video calls by adding Twilio WSS endpoints as Trusted URLs in the Salesforce org. This is specifically required for secure video-call connectivity, which directly matches the symptom in the question: the Twilio credentials and Experience Cloud site are configured, but the video media fails to load.

Twilio External Credentials handle authentication and connection details for the integration, and the Experience Cloud site provides the HCP-facing remote engagement experience. However, browser and Salesforce security controls still need to allow the required Twilio WebSocket Secure traffic. If those URLs are not trusted, the page can load while the actual audio/video media connection fails.

Option B is incorrect because assigning a field-sales permission set to the Site Guest User would be inappropriate and overly permissive. The issue is media connectivity, not guest-user access to sales functions. Option C is also incorrect because a trigger handler for remote-session invitations would relate to record automation or invitation behavior, not secure loading of Twilio video traffic. Therefore, the consultant must add Twilio’s required endpoints to Trusted URLs .

=========

Option C, Account Plan Stakeholder, is correct because the requirement is to capture stakeholder-profiling attributes within a Key Account Management account plan. Salesforce Help describes Account Plan Stakeholders as the way to influence an account’s decision-making policies by adding stakeholders to an account plan. That aligns directly with the scenario, where the KAM is mapping the influence structure of a hospital’s Pharmacy & Therapeutics committee and classifying an HCP as “High Influence” and a “Supporter.”

The Salesforce Key Account Management Account Plan data model includes Account Plan, Account Plan Participant, Account Plan Participant Stakeholder, Account Plan Stakeholder, Account Plan Stakeholder Action, and Account Plan Stakeholder Product. This confirms that stakeholder management is part of the standard KAM account-planning architecture, and Account Plan Stakeholder is the object used to represent stakeholders in the account plan context.

Option A is incorrect because Account Contact Relation represents a relationship between an account and a contact in standard Salesforce account modeling. It does not represent the stakeholder’s role, sentiment, or influence inside a specific Life Sciences Account Plan. Option B, Account Plan Participant, is also not the best answer because participants are users or collaborators who work on the account plan, while stakeholders represent the external decision-makers or influencers being profiled. Therefore, the correct object for storing stakeholder attributes such as influence level and support position is Account Plan Stakeholder.

=========

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 C is correct because Territory Product Quantity Allocations are designed to manage sample product distribution at the territory level. Salesforce Help explains that territory product quantity allocations and sample limits both help manage sample distribution to HCPs, but territory product quantity allocation is used when the business needs to allocate a defined product quantity to a territory. Salesforce’s setup guidance for Territory Product Quantity Allocations also states that Max Disbursement Limit Quantity is the maximum amount a sales rep can disburse in a given visit.

This directly matches the requirement. Cumulus Pharma wants to cap the total quantity of Immunexis 50mg available for a high-growth territory in the next quarter and also prevent reps from handing off more than 50 units in a single visit. A Territory Product Quantity Allocation record can store the territory-level allocated quantity, while Max Disbursement Limit Quantity enforces the per-visit disbursement cap.

Option A is incorrect because an Advanced Sample Limit Template focuses on account or provider-level sample limits, not the total allocation available to a territory. Option B is also incorrect because changing the Life Sciences Marketable Product globally would affect the entire organization, not just the high-growth territory. Therefore, the correct recommendation is to create a Territory Product Quantity Allocation record and set the per-visit max disbursement limit to 50.

=========

Option B is correct because the requirement is specifically to prevent visit creation when a Visit overlaps with a Time Off Territory record. Salesforce Life Sciences documentation references Time Off Territory overlapping rules as the standard mechanism that prevents creating visits during TOT events. Salesforce’s Winter ’26 Customer Engagement package patch notes also mention an issue where a visit could be created during a Time Off Territory event, bypassing the overlapping rule that should have prevented creation. That confirms TOT overlapping rules are the expected standard control for this scenario.

Because the business wants a hard stop, the overlapping rule behavior must be set to “Error.” This means the rep receives an error and cannot proceed with scheduling the visit while it conflicts with the TOT time block.

Option A is incorrect because a custom validation rule on Visit would duplicate a standard Life Sciences calendar/TOT capability and may not handle the full mobile scheduling experience correctly. Option C is also not the best answer because “Block Activity on Conflict” on the TOT record type is not the documented standard configuration in the Life Sciences Visit/Calendar settings. The correct standard configuration is to use TOT Overlapping Rules and set the overlap behavior to Error. This prevents scheduling visits during the rep’s logged time off.

=========

Option B, Dynamic Segmentation, is correct because the sample limit assignment must change automatically when the HCP’s Engagement Tier changes. Salesforce’s Life Sciences Cloud segmentation data model supports entities and relationships for creating and managing static and dynamic account segmentations. It also shows the connection between account segmentation, Healthcare Provider records, Product2, Provider Sample Limit, Provider Sample Limit Template, and Life Science Account Group Assignment. This confirms that segmentation is reusable in sample limit scenarios and can drive which sample limit template applies to a provider.

The important phrase in the question is “automatically update.” Because Engagement Tier is a calculated Account field that changes monthly, the consultant needs a rule-based segmentation approach. Dynamic Segmentation evaluates account criteria and can move accounts between groups as their data changes. When the HCP qualifies for the Tier 1 segment, the higher sample limit template can apply without an administrator manually reassigning the provider.

Option A, Account Segmentation, is too broad and does not specifically indicate the automatic, rule-driven behavior needed here. Option C, Sample Segmentation, sounds related to samples, but the key requirement is not merely grouping sample policies; it is dynamic reassignment based on changing account criteria. Therefore, Dynamic Segmentation is the correct configuration to support automatic sample limit changes as HCP engagement tiers change.

=========

Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep’s targets.

Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.

Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.

=========