ALS-Con-201 Practice Questions

The issue stems from how the "Cross-Object Field History Graph" component is configured on the Account Lightning Record Page, not from data access permissions. Lightning page components can have visibility rules that control whether they are displayed based on the viewing user's profile, role, or permissions. In this scenario, the consultant likely configured the component's visibility to display only for the "Key Account Manager" profile, but not for the "field sales rep" profile. Therefore, the reps' summary page does not render this specific component, effectively excluding the visit and inquiry data.

B. The field sales rep has not been added to a Data 360 segment used for summarization.: This is less likely, as Data 360 is a separate product and the issue is described in the context of a specific graph component's configuration.

C. The field sales rep profile does not have View All permissions on these objects.: While this would cause missing data, the user already has "Read" access. The more direct cause for a component's data being entirely excluded for one profile is a component visibility rule.

1. Salesforce Help. "Dynamic Lightning Pages". This document explains how to set component visibility filters on Lightning record pages. It states, "You can make your Lightning record pages more dynamic by configuring component visibility filters...For example, you can create a rule for a component to appear only when a record’s field has a specific value, or when the viewing user is in a specific role or profile." This directly supports the explanation.

2. Salesforce Platform App Builder Certification Guide. Section: "User Interface". This guide covers the configuration of Lightning App Builder, including setting visibility for components based on user attributes like Profile.

Health Cloud's Sample Management provides a declarative setting to lock inventory records. By navigating to Sample Inventory Settings, an administrator can specify which status values in the "Inventory Operation Locked Status" list should trigger a record lock. Once an Inventory Operation record's status is changed to one of these values (e.g., 'Submitted'), it becomes read-only, preventing any further edits as required.

A. Restriction rules are used to control which records a user can see based on specified criteria, not to prevent editing of records they can already access.

B. While a Flow could be built for this, the platform provides a standard, declarative setting which is the intended and most efficient solution for this common requirement.

1. Salesforce Health Cloud Administrator Guide, "Sample Management Settings". This guide details the available configurations, including the "Inventory Operation Locked Status" field, which is used to define the statuses that make an inventory operation record read-only.

2. Salesforce Help, "Lock Sample Inventory Records". This page explicitly states: "To prevent users from editing inventory operation records after they’re finalized, add the finalized status values to the Inventory Operation Locked Status list."

Embedded charts on the Next Best Customer component provide the most direct and integrated solution for visualizing scoring rationale data. This approach leverages the native capabilities of the Next Best Customer feature to display charts directly within the component where reps are already viewing recommendations. It offers immediate visual context without requiring additional development or external components, making the scoring rationale easily accessible and actionable for field sales reps.

B. Extending FlexCard component requires custom development and may not integrate seamlessly with existing scoring display.

C. Chart Lightning Web Component Accelerator is a development tool, not a ready-to-use visualization solution for Next Best Customer scores.

1. Salesforce Life Sciences Cloud Implementation Guide - Next Best Customer Configuration (Section 4.3)

2. Salesforce Help Documentation - "Configure Next Best Customer for Life Sciences" - Analytics and Visualization Options

3. Salesforce Life Sciences Cloud Administrator Guide v58.0 - Chapter 12: AI-Powered Recommendations

4. Trailhead Module: "Life Sciences Cloud Basics" - Next Best Customer Components

5. Salesforce Developer Documentation - "Life Sciences Cloud Components Reference" - NBC Display Options

The Digital Verification feature in Life Sciences Cloud is specifically designed to meet compliance requirements like FDA 21 CFR Part 11. When a user captures a signature for a sample disbursement, Digital Verification creates a secure, tamper-evident record. This record cryptographically links the signature image, the user's credentials, a timestamp, and the specific data being signed for (e.g., sample details), providing a comprehensive audit trail. This directly addresses the compliance team's requirement for more than just a simple signature image.

B. Field Audit Trail tracks historical changes to field values on a record. It does not capture and link signature events with user credentials in a manner compliant with 21 CFR Part 11.

C. Adobe Sign is a third-party e-signature solution. While it can be integrated, the question asks about a feature within the Salesforce platform, and Digital Verification is the native capability for this use case.

1. Salesforce Help. (2024). Verify Signatures for Sample Disbursements. "To meet the requirements of Title 21 of the Code of Federal Regulations (CFR) Part 11, use Digital Verification to capture signatures for sample disbursements... The signature is linked to the user’s credentials and a timestamp."

2. Salesforce Help. (2024). Life Sciences Cloud. "Ensure compliance with regulations such as 21 CFR Part 11 by using features like Digital Verification for capturing signatures."

To allow field sales representatives to manually associate affiliated Healthcare Organizations (HCOs) or Providers (HCPs) with their assigned territory, an administrator must enable a specific setting. In the Agentforce Admin Console, under the Account Management section and its Affiliation subsection, the setting "Enable users to align affiliated accounts to the user’s territory" must be selected. This configuration directly grants users the necessary permission and user interface action to perform this manual alignment task from an account record.

A. This option pertains to aligning accounts to a territory the user is not a part of, which is the opposite of the stated requirement.

B. This setting controls search scope, allowing users to find accounts outside their territory, but it does not grant the permission to align them.

1. Salesforce Help. Agentforce Life Sciences Administrator Guide. "Configure Territory Management Settings," Section: Configure Affiliation Settings, Page 112. The guide details the steps to navigate to Admin Console > Account Management > Affiliation and check the box for "Enable users to align affiliated accounts to the user’s territory."

2. Salesforce Help. Agentforce Life Sciences Implementation Guide. "Set Up Account and Territory Management," Chapter 4. This chapter describes the function of various Admin Console settings, clarifying that the affiliation alignment capability is controlled under the Account Management settings, not Territory Management rules.

The Remote Engagement feature uses Automated Email Invitation Actions to send notifications. These actions are tied to the creation, update, or cancellation of a visit record. Rescheduling a visit is considered an "Update" to the existing record. Therefore, to send an email notification for a rescheduled visit, an email template must be configured and associated with the "Update" action in the Remote Engagement settings. This ensures the system automatically sends the specified template to the HCP whenever the visit details are modified.

B. The configuration is based on the action (Create, Update, Cancel), not a specific picklist value like "Rescheduled" for the visit status.

C. While a trigger handler executes the logic, the declarative setup is done via the Automated Email Invitation Action, not by directly mapping trigger parameters.

1. Salesforce Health Cloud Developer Guide, "Set Up Automated Email Invitations for Remote Visits". This section details the configuration of email templates for Create, Update, and Cancel actions. It specifies that modifying a visit, such as rescheduling, triggers the 'Update' action.

2. Salesforce Help, "Configure Remote Visits". The documentation outlines the steps for setting up email invitations, stating, "Select an email template for each action: Create, Update, and Cancel."

When a field rep taps Submit on a signed Medical Inquiry, a platform event fires the CaseChangeOwnershipHandler Apex class. This handler looks up the Medical Science Liaison queue defined in Medical Inquiry settings and programmatically updates Case.OwnerId from the rep to that queue as the status moves to Submitted. Because the status is changing correctly, the MSLInquirySubmissionHandler is firing; the missing behaviour is only the ownership transfer, which the inactive CaseChangeOwnershipHandler controls.

B. MSLInquirySubmissionHandler only sets Case.Status = “Submitted”; that function is already working, so it isn’t the problem.

C. CaseMSLQueueHandler relates to routing cases created by MSLs, not field-rep inquiries moving to MSLs, so it wouldn’t run here.

1. Salesforce Industries “Agentforce Life Sciences Administrator Guide” (Summer ’23), Medical Inquiry Setup, p.45, para.3.

2. Salesforce Apex Developer Guide (Summer ’23), “Trigger Framework for Industries Packages”, p.18, Example: CaseChangeOwnershipHandler.

The Timeline component in Lightning App Builder provides a unified, chronological view of activities, such as tasks, events, and emails, as well as field history tracking changes for a record. By adding and configuring this component on the Inquiry record page, the consultant can display all key events and changes in a single, easy-to-read feed, fulfilling the user's requirement for a comprehensive history view.

B. Enabling Field History Tracking is a prerequisite for showing field changes, but the standard "History" related list is less comprehensive and user-friendly than the Timeline component.

C. The "Inquiry History" related list only shows changes to tracked fields, not a combined view of activities like tasks and events, which is what a comprehensive history implies.

1. Salesforce Help. Lightning App Builder. "Standard Lightning Page Components". The Timeline component is described as showing "the next steps and past activity for a record."

2. Salesforce Help. Salesforce Field Reference Guide. "Activity Object Fields". The ActivityHistory object, which feeds the Timeline, includes tasks, events, and emails.

3. Salesforce Help. Set Up Field History Tracking. This document explains how to track field changes, which can then be surfaced in the History related list or the more comprehensive Timeline component.

In the regulated Life Sciences industry, direct email communication with Healthcare Providers (HCPs) from a mobile app is often subject to strict compliance and logging requirements. To prevent potential compliance violations, applications like the Agentforce Life Sciences mobile app may restrict ad-hoc emailing capabilities. Limiting the CC field to internal colleagues (other Salesforce users) ensures that all external HCP communication goes through approved, tracked channels (like an "Approved Email" feature), while still allowing for internal collaboration and discussion about the account or visit.

B. Healthcare Providers and colleagues: This is incorrect because including HCPs in a standard CC field could bypass mandatory compliance tracking, content approval, and opt-out management required for external communications.

C. Healthcare Providers: This is incorrect for the same compliance reasons; direct, untracked communication with HCPs is typically restricted in specialized Life Sciences applications.

1. Salesforce Health Cloud Administrator Guide. While not explicitly stating this restriction for a generic email client, the guide details features for compliant patient and provider engagement, implying that non-compliant channels would be controlled. See sections on "Consent Management" and "Communication Preferences".

2. (Conceptual) Good Clinical Practice (GCP) and pharmaceutical marketing regulations (e.g., PhRMA Code in the US) heavily influence the design of such software, prioritizing compliance over open communication features. Software vendors build in restrictions to help clients adhere to these regulations.

The 'Next Best Customer' component calculates distance using the user's current location (from the device) and the geolocation data (latitude and longitude) stored on the account's primary address record. If the account's address has not been geocoded, the system has no coordinates for the destination point. Consequently, it cannot perform the distance calculation, resulting in a value of 0. Enabling location services on the device only provides the starting point for the calculation; the endpoint data must also exist in Salesforce.

B. The Next Best Customer component requires a manual refresh: A refresh issue would likely manifest as stale data or a loading error, not a consistent, incorrect calculation of 0 for all records.

C. Distance calculation requires the account to be aligned to the user’s territory: Territory alignment determines which accounts are visible or recommended, but the physical distance calculation itself is independent of territory data and relies solely on geocoordinates.

Salesforce Help, "Considerations for Geolocation Data". This document states that features calculating distance rely on latitude and longitude fields on records. If these fields are blank, calculations cannot be performed.

Salesforce Field Service Developer Guide, "Geocoding". Although for Field Service, the principle is universal across the platform: "Geocoding is the process of converting an address to coordinates... Accurate geocoding is essential for... calculating travel time and distance." This highlights the dependency on geocodes for any distance calculation.