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

The correct answer is B because the deadlines and review windows for activity-plan adjustments are configured on the Activity Plan record, specifically in the review-related configuration. Salesforce Help for creating Activity Plans references fields such as Reviewer Plan Adjustment Start Date and Reviewer Plan Adjustment End Date , which define the date range in which the manager can review adjustment requests.

The scenario describes a plan-level governance requirement: field sales reps must submit proposed visit targets by a specific deadline, and adjustments above allowed thresholds must be reviewed. This belongs to the Activity Plan configuration because the plan defines the cycle, timing, targets, review process, and adjustment behavior for the territory or provider planning period. Configuring the Review Details section ensures that the plan controls when reps can submit changes and when managers can review them.

Option A is incorrect because Global Calculation Settings for a Provider Activity Measure Type would relate to how measures or calculations are evaluated, not the submission and manager-review deadline for a specific Activity Plan. Option C is also incorrect because a Goal Definition represents a reusable planning objective, but it does not control the operational review dates and adjustment thresholds for a specific West Coast Activity Plan. Therefore, the consultant should configure the deadlines and adjustment limits on the Activity Plan record within the Review Details section .

=========

Option B is correct because MIRF Share Management is the Life Sciences Cloud batch job used to manage sharing for Medical Inquiry records. Salesforce Help describes Medical Inquiries as supporting batch jobs that share and manage multiple medical inquiry records consistently and efficiently, and specifically identifies the MIRF Share Management job as the job used to maintain inquiry-data sharing. This directly matches the scenario: after a territory reorganization, field sales reps need access recalculated for historical Medical Inquiry records associated with HCPs in their newly assigned territories.

Option A is not the best answer because Account Object Share Rule Calculation is a generic description of account sharing recalculation. The issue is not general Account visibility; it is Medical Inquiry record visibility after territory changes. Option C is also incorrect because aligning accounts to territories handles territory assignment, but the accounts have already been reorganized. The remaining problem is recalculating access to Medical Inquiry records that should now be shared according to the new territory model.

Therefore, the consultant should run MIRF Share Management. This batch job is the standard Life Sciences mechanism for recalculating Medical Inquiry record sharing and ensuring field users regain access to inquiry records that correspond to their current territory-aligned HCPs.

=========

Option A, Provider Account Territory Summary, is the best answer because the requirement is to store summarized, territory-specific account metrics. The HCP belongs to more than one territory, and Cumulus Pharma must track Year-to-Date Visit Counts independently for each territory. Salesforce’s Life Sciences Account Management data model includes both Provider Account Territory Information and Provider Account Territory Summary as standard entities for managing healthcare provider and organization accounts, related profiles, and territory-specific information.

Provider Account Territory Summary is the object designed for summarized metrics at the provider-account-and-territory level. That makes it the appropriate place for values such as Year-to-Date Visit Counts, which are calculated or aggregated metrics rather than the raw alignment relationship itself.

Option C, Provider Account Territory Information, is related but not the best answer. Salesforce’s Developer Guide describes ProviderAcctTerritoryInfo as representing engagement data between an account and a user within an assigned territory, including items such as next provider visit date and preferred address. However, the question asks for territory-specific account metrics, not general engagement information between a user, account, and territory. Option B, Provider Account Territory Association, is also not correct because the issue is not simply associating an account to a territory. The HCP is already assigned to both territories. The need is to store independent summarized metrics for each territory. Therefore, Provider Account Territory Summary is the correct standard object.

=========

The correct answer is C because reverse affiliation creation is handled by the AffiliationReciprocalHandler . Salesforce Help for Life Sciences trigger handlers identifies AffiliationReciprocalHandler as the handler that manages reciprocal affiliations. The same documentation notes behavior related to reciprocal affiliations and affiliation type handling, which directly matches the scenario where a newly created affiliation should automatically create the reverse relationship.

Affiliation Reverse Role Mapping defines how the relationship role should translate between the original and reciprocal records. For example, if an HCP is “Attending” at an HCO, the reverse relationship may show the HCO as “Employing” or otherwise related to the HCP, depending on the configured mapping. However, defining the mapping alone does not execute the automation. The trigger handler must be active so that when users create a new Affiliation record, Salesforce can generate the reciprocal Affiliation record using the configured reverse role mapping.

Option A, AffiliationUniquenessHandler , is incorrect because uniqueness logic prevents duplicate or invalid affiliation records; it does not create the reverse relationship. Option B, HardAffiliationHandler , is also incorrect because it is not the handler identified for reciprocal affiliation generation. Since the missing behavior is automatic creation of the reverse affiliation, the consultant must enable AffiliationReciprocalHandler .

Option C is correct because Advanced Sample Limit Templates are designed for custom, complex sample-limit rules. Salesforce Help explains that advanced sample limit templates are used to define custom sample limit rules for more complex needs and stricter requirements. This scenario requires two non-basic behaviors: a dynamic period start based on the product launch date and soft-limit enforcement that warns the rep but still allows the disbursement to proceed. Those requirements go beyond a generic calendar-year rule.

A Generic Sample Limit Template is not the best answer because generic templates are better suited for standard sample-limit logic. The requirement explicitly says the limit period must begin on the Product Launch Date rather than the standard Calendar Year, which makes the rule more specialized. A Country Sample Limit Template is also not correct because country templates are used for country-specific legal or regulatory sampling limits. In this question, the control is strategic and inventory-driven, not a legal requirement tied to a specific country.

Advanced templates are the correct fit because they allow more flexible configuration for business-specific sample controls, including nonstandard periods and warning-based enforcement. Therefore, the consultant should use an Advanced Sample Limit Template for the Immunexis launch sampling rule.

=========

The correct answer is C because the requirement is about sampling eligibility and validation behavior during visits. Salesforce Life Sciences sample management features support compliant handling and distribution of samples, and visit-related sample behavior is configured through visit settings and sample management setup. Salesforce Help describes sample management as enabling pharmaceutical companies to efficiently handle and distribute drug samples to providers, while the broader Customer Engagement setup includes Life Sciences mobile and visit configuration areas where these rules are applied.

The scenario includes two validation-style requirements. First, the consultant must specify which types of HCOs are eligible to receive samples. Second, the system must require users to enter a batch number for every sample drop. Both requirements are about enforcing rules during the sampling process, not about presenting product details or general sample item display.

Option A, Product Detailing Settings , is incorrect because product detailing is used to configure how products are discussed or presented during an engagement. It does not control HCO sample eligibility or mandatory batch entry. Option B, Samples and Items Settings , sounds related to sample availability, but the requirement is specifically about compliance validation. Option C, Sample and Validation Settings , is the correct subsection because it governs sample-related validation behavior, including eligibility and required information such as batch number entry. Therefore, the consultant should use Sample and Validation Settings .

=========

The correct answer is A because Remote Engagement email notifications depend on email templates configured for the relevant automated email invitation context/action. Salesforce Help for uploading and creating email templates in Life Sciences Cloud includes configuration fields for automated email invitation context and action. For a rescheduled or updated virtual visit, the email template must be configured so the automated email invitation action corresponds to the update event.

The scenario asks specifically about email notifications when virtual visits are rescheduled. A reschedule is an update to an existing visit invitation, not a new invitation and not a cancellation. Therefore, the consultant must ensure there is an email template whose Automated Email Invitation Action is set to Update . That template is then used by the Remote Engagement process when the visit details change and the HCP needs to receive the revised meeting information.

Option B is incorrect because configuring a handler around a visit status value such as “Rescheduled” is not the core template configuration required for the notification content and action. Option C may sound plausible because trigger handlers often support automation, but the question asks which configuration is required to send email notifications for rescheduled virtual visits. The action-specific email template is the necessary configuration. Therefore, the consultant should use an Email Template with Automated Email Invitation Action set to Update .

=========

Option C is correct because the issue occurs when an HCP joins a Remote Engagement call through an Experience Cloud site link. In this flow, the external HCP typically accesses the site as the Site Guest User, so the guest user needs the correct permission set to use the remote engagement experience. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that admins must assign permission sets to the guest user of the site, including Access Remote Engagement for Digital Experience . This directly matches the error in the question: the HCP reaches the site, but receives an insufficient permissions error.

Option A is incorrect because the Life Sciences Commercial Admin permission set is intended for administrative users, not the Site Guest User serving an unauthenticated Remote Engagement portal. Assigning broad admin permissions to a guest user would also be inappropriate from a security and compliance perspective. Option B is also incorrect because the requirement is not to license the HCP as a Customer Community Plus user. The scenario describes an HCP joining from a link, and the Salesforce setup guidance specifically identifies a permission-set assignment for the Site Guest User.

Therefore, the consultant should assign the Access Remote Engagement for Digital Experience permission set to the Experience Cloud Site Guest User.

=========

The correct answer is C because Salesforce Life Sciences Cloud provides the Lsc4ce.EmailQueueProcessor interface for using a third-party email service. Salesforce Help for using a third-party email service states that administrators should create a global Apex class that implements the Lsc4ce.EmailQueueProcessor interface. This interface is the supported extension point for handing off Life Sciences email operations to an external email provider instead of relying only on Salesforce’s standard email sending behavior and limits.

This scenario is specifically about emails sent from the Agentforce Life Sciences mobile app. Salesforce’s Field Email capability is designed to streamline compliant email creation, sending, and tracking for Life Sciences users, and the developer documentation describes LifeScienceEmail as representing a collection of sendable messages that manages creation, sending, and tracking of email communications. When an organization needs an external provider to send those emails, the custom Apex implementation must process the queued email operation and pass it to the third-party service.

Option A is incorrect because Lsc4ce.ExternalEmailHandler is not the interface identified by Salesforce for third-party email service handoff. Option B is also incorrect because Lsc4ce.MessagingService is not the documented Life Sciences email queue processing interface. Therefore, the consultant should implement Lsc4ce.EmailQueueProcessor .

=========

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.

=========