Free Salesforce-Agentforce-Life-Sciences-Consultant Practice Test Questions (2026)

Explanation
The requirement is to automatically align an HCP to a new territory based on their work at a hospital in that region, not their primary office address. In Life Sciences Cloud, Affiliation Alignment Rules are specifically designed to assign HCPs to commercial territories based on their affiliations with Healthcare Organizations (HCOs), rather than geographic address criteria . This enables reps to manage relationships based on where the HCP actually treats patients.

Correct Option:

C. Create an affiliation alignment rule specifying the Territory and the Affiliation Role, for example, “Affiliated Practice.”

Affiliation Alignment Rules automate territory assignment by evaluating an HCP's relationship (affiliation) with an HCO and the role they hold .

In Life Sciences Cloud, key objects like ProviderAffiliation capture connections between HCPs and hospitals. The affiliation record includes fields for the HCO, the HCP, and the Role (e.g., "Hospital Staff", "Affiliated Practice") .

By creating a rule that aligns the "San Francisco North" territory with the "Bay Area General Hospital" affiliation and filters by the appropriate Role ("Hospital Staff" or "Affiliated Practice"), only HCPs with that specific affiliation will be assigned to the new territory.

Incorrect Options

A. Create a territory geo assignment rule using the zip code of the hospital and apply it to the HCP’s record.
Geo assignment rules evaluate the primary address of an account (HCP) record. Since the HCP's primary address is in Beverly Hills, the rule would not assign them to the San Francisco territory. This method does not consider their affiliations .

B. Create an account assignment rule in Territory Management to inherit the territory from the Parent Account field.
This approach is used for standard hierarchical account models. An HCP record is not typically a child record of an HCO in this inheritance context; the affiliation object is the standard way to model the relationship.

Reference
Salesforce Life Sciences Cloud documentation details the use of Affiliation Alignment Rules to automate the assignment of HCP and HCO records to commercial territories . This feature ensures users have appropriate access to the records they need, reducing manual errors and improving data consistency . HCP affiliations with HCOs are a core component of the account model, used to establish referral networks and influence .

Explanation
The requirement is to automatically align only oncology-specialty HCPs who are affiliated with a specific HCO to the territory, excluding others at the same institution. Affiliation alignment rules evaluate an HCP's connections (affiliations) to HCOs using attributes like Care Specialty, enabling precise territory assignment based on both affiliation and clinical role .

Correct Option:

B. Create an affiliation alignment rule for the territory and select Care Specialty as "Oncology."
Affiliation alignment rules automate territory assignment by evaluating an HCP's relationship with an HCO, ensuring users have appropriate access to records they need while reducing manual errors .

The rule can filter on specific affiliation attributes, such as Care Specialty, to include only HCPs with the "Oncology" specialty .

This approach correctly uses the affiliation to identify the connection to the HCO and then applies a specialty filter to include only the targeted clinical role.

Incorrect Options

A. Create a territory geo assignment rule where PersonAccount.Specialty equals "Oncology."
This approach uses geography (zip code) as the primary assignment logic. Since all HCPs at the same HCO share the same geographic location, both the oncology and cardiology HCPs would be assigned. Filtering directly on the account record's specialty does not override the geographical inclusion of both.

C. Create a sharing rule on the Care Specialty object to share Oncology records.
This is conceptually flawed. Sharing rules control record-level access to objects, not territory assignment. The Care Specialty is an attribute or field value, not an object that can be shared. Territory assignment requires configuration within Enterprise Territory Management, specifically using affiliation alignment rules.

Reference
Salesforce Life Sciences Cloud documentation details the use of Affiliation Alignment Rules to automate the assignment of HCP records to commercial territories . These rules are configured to evaluate affiliations and can apply criteria such as role or specialty, ensuring precise territory alignment based on clinical activities .

Explanation
The scenario describes a common sample management workflow where a rep has physically received samples but has not yet acknowledged them in the system. To maintain inventory integrity, Life Sciences Cloud uses a "pending" state: the disbursement record is created with a warning, but inventory counts are not immediately updated. The rep must first acknowledge receipt of the physical inventory, then use the Resolve Disbursement action to reconcile the transaction and finalize the count updates . This ensures sample traceability and accurate stock levels.

Correct Option:

A. The system temporarily pauses updates to the Remaining Quantity and Quantity On Hand fields; the rep must acknowledge the inventory, and then click the Resolve Disbursement quick action button to finalize the update.
Sample disbursements in Life Sciences Cloud maintain inventory integrity by creating a "pending" record that does not immediately decrement quantity fields .

The rep must first acknowledge the physical receipt of inventory in the system, which confirms the stock has been received.

The Resolve Disbursement quick action then reconciles the transaction—only after this action does the system update the remaining quantity and quantity on hand fields, ensuring the digital audit trail accurately reflects physical reality.

Incorrect Options

B. The disbursement is blocked until the Life Sciences Commercial Admin manually overrides the "Unresolved" status in the Admin Console under Org-Wide Settings.
This is incorrect because the resolution workflow is performed by the rep, not a manual admin override. Life Sciences Cloud is designed for self-service reconciliation by field users to avoid operational delays.

C. The system automatically triggers a Manual Adjustment operation to force the counts to match; the rep must then generate an electronic receipt to clear the warning.
This is incorrect because the reconciliation is not automatic. The system does not force count adjustments; it requires the rep's explicit acknowledgment and the Resolve action to finalize the transaction.

Reference
Salesforce Life Sciences Cloud documentation details the sample management process, where sample disbursement transactions support traceability and automated reconciliation workflows to ensure accurate stock levels . Industry implementations emphasize automated alert systems and rep accountability to maintain inventory integrity .

Explanation
After Activity Plan configurations are completed and aligned with business objectives, they must be activated for the correct time period to become effective for field reps. The Update Activity Plan Status batch job is specifically designed to update the status of activity plans based on their start and end dates, ensuring that plans are automatically activated or deactivated according to the configured time periods.

Correct Option:

C. Schedule or immediately trigger the Update Activity Plan Status batch job.

This batch job evaluates activity plans against their defined effective date ranges.

It updates the plan status to "Active" when the current date falls within the planned period, making them available to reps.

It also automatically deactivates plans that have passed their end date, ensuring only current objectives are active.

Scheduling this job ensures that future plans will activate automatically without manual intervention.

Incorrect Options

A. Schedule or immediately trigger the Validate Activity Plans batch job.
The Validate Activity Plans batch job is used to check the integrity and completeness of activity plan configurations, such as ensuring all required fields are populated. It does not activate plans or manage their statuses based on time periods.

B. Schedule or immediately trigger the Process Provider Activity Goals batch job.
The Process Provider Activity Goals batch job is responsible for generating or updating goal measure records for individual Healthcare Providers based on the activity plans. It does not handle the activation or status management of the plans themselves.

Reference
This aligns with the standard batch processing architecture in Salesforce Life Sciences Cloud, where specific batch jobs handle distinct functions: validation, goal processing, and status management. The Update Activity Plan Status batch job is the designated process for activating plans according to their configured time periods.

Explanation
The question describes configuring an Experience Cloud page for remote visits that require video functionality and compliance controls like Terms & Conditions. The HCP Remote Platform Conference component is the standard Life Sciences Cloud component designed specifically for this purpose, bundling video conferencing capabilities with built-in compliance features for healthcare engagements.

Correct Option:

A. HCP Remote Platform Conference
This component natively provides the video conferencing interface required for remote HCP engagements, supporting both audio/video communication and screen sharing .

It is designed with the compliance guardrails essential for Life Sciences, which include capturing consent and managing the Terms & Conditions review workflow within the session flow .

The component streamlines the remote visit experience, allowing reps to present approved materials and record interactions directly within the video session, reducing the need for disparate tools .

Incorrect Options

B. Twilio Connector:
This refers to a development tool that integrates Twilio's communication APIs for building custom workflows . It is not a drag-and-drop Experience Cloud component for a remote visit page. It requires custom code and does not include the pre-built Life Sciences compliance logic for consent or Terms & Conditions.

C. Remote Video Player:
This is a more generic description that could apply to various third-party Experience Cloud components (like Avonni's video player) that handle video embedding but not the specific visit workflow, compliance logic, or engagement tracking required for a regulated Life Sciences remote visit .

Reference
This is consistent with the Life Sciences Cloud Mobile app features, which include "Remote engagement: audio/video, content sharing, e-consent" as a key integrated capability . It also aligns with the standard Salesforce Trailhead content describing how remote visits use the same workflow as in-person visits, ensuring records remain consistent regardless of format and all actions are "validated, logged, and tied back to compliance" .

Explanation
The question asks about a specific configuration limit for the visit engagement screen sidebar in the Agentforce Life Sciences mobile app. This is a defined platform constraint regarding how many custom object-related lists can be added to that particular sidebar component. The limit is set to a maximum of 5 such lists .

Correct Option:

B. 5
The sidebar on the visit engagement screen is designed to provide quick access to key related records without overwhelming the mobile interface. It has a specific limit of 5 custom object-related lists that can be added. This constraint ensures optimal performance and a streamlined user experience on mobile devices, preventing the sidebar from becoming cluttered and difficult to navigate during a visit .

Incorrect Options
A. 10:
This number is not the documented limit for custom object-related lists in the visit engagement screen sidebar.

C. 2:
This is lower than the actual maximum of 5 allowed lists for this specific sidebar configuration.

Reference
This configuration limit is specific to the Life Sciences Cloud mobile app's visit engagement screen and is noted in related certification preparation materials .

Explanation
The requirement is to send captured medical insights to an external system without delay, meaning in real-time or near-real-time. Platform Events are Salesforce's native solution for event-driven architecture and real-time, scalable communication between Salesforce and external systems . The MedicalInsightEvent is a pre-built platform event in Life Sciences Cloud designed for this exact purpose. Activating its dedicated handler (PublishMedicalInsightEventHandler) publishes the event whenever a Medical Insight record is created, triggering immediate delivery to any subscribed external systems.

Correct Option:

B. Activate PublishMedicalInsightEventHandler to publish the MedicalInsightEvent platform event.
Platform Events enable a publish-subscribe model, allowing decoupled systems to communicate in real time . This is ideal for sending data to an external intelligence system without delay.

The MedicalInsightEvent is a standard platform event provided with Life Sciences Cloud for medical insights. Activating the PublishMedicalInsightEventHandler is the standard, low-code configuration to publish this event .

This approach ensures that the moment a rep saves a Medical Insight, the external system receives it instantly, enabling immediate intelligence processing.

Incorrect Options

A. Create a custom platform event and activate MedicalInsightRecordHandler to publish this event.
While creating a custom platform event is a valid approach for custom integrations, it is unnecessary here. Life Sciences Cloud already provides the standard MedicalInsightEvent for this purpose. Reinventing the wheel with a custom event adds unnecessary complexity and goes against using the pre-built platform capabilities.

C. Activate MedicalInsightIntegrationHandler to share the insight record with the external system.
This is a distractor as MedicalInsightIntegrationHandler is not a standard, pre-built component for this use case. The described solution leverages a platform event handler; an integration handler would typically refer to a custom Apex class or middleware, which requires development work rather than a simple activation.

Reference
Salesforce uses Platform Events for event-driven architecture and real-time communication . Life Sciences Cloud includes standard platform events like MedicalInsightEvent for data integration scenarios . Activating the corresponding event handler is the recommended approach for publishing these events without delay.

Explanation
The requirement is to automatically send email notifications to HCPs when a virtual visit is rescheduled (updated). In Life Sciences Cloud, email notifications for virtual visits are configured through Email Templates and automated actions triggered by visit status changes. Using an automated email invitation action configured for the "Update" event ensures that the system sends the appropriate notification whenever a visit record is rescheduled .

Correct Option:

A. Email Template with Automated Email Invitation Action set to "Update".

Email Templates provide the structured content and formatting for notifications sent to HCPs about their virtual visits .

The Automated Email Invitation Action is a workflow or event-driven mechanism that sends these emails when specific changes occur to a visit record .

Setting this action to "Update" triggers the email to be sent specifically when a visit is rescheduled or modified, ensuring timely and appropriate communication with the HCP.

Incorrect Options

B. Email Invitation Action Handler configuration with visit status as "Rescheduled".
While an action handler might be involved, the described configuration path focuses on the Email Invitation Action itself and the associated Email Template. The action is what triggers the email; the template defines its content.

C. Email Invitation Trigger Handler is active and visit status parameter is mapped.
This is a more generic description that lacks the specific association with an Email Template. An active trigger handler alone doesn't specify that an email notification will be sent; it requires a configured action and template to define the communication.

Reference
Salesforce documentation and release notes describe the functionality for automated email communications triggered by changes to engagement records, including virtual visits . Approved Email and email templates are standard features used for compliant, automated communication with HCPs .

Explanation
The question asks about the scheduling frequency for Territory Management batch jobs. In Salesforce, these automated batch processes can be scheduled to run frequently to ensure territory assignments remain current. The platform supports scheduling these jobs as often as every hour .

Correct Option:

A. Hourly
Territory Management batch jobs can be scheduled to execute automatically on an hourly basis . This allows organizations to maintain up-to-date territory assignments, ensuring that new accounts, opportunities, or changes to existing records are quickly assigned to the correct sales representatives. This configuration is often used for high-volume data processing, where hourly execution provides a balance between system performance and data freshness

Incorrect Options

B. Every 12 hours:
While 12-hour scheduling is possible, it is less frequent than the system's maximum allowed frequency. This is a valid scheduling option, but it is not the limit of how often jobs can run .

C. Monthly:
This is a valid scheduling option for jobs that do not require frequent updates. However, it is significantly less frequent than the hourly limit and is typically used for large-scale, non-time-sensitive processing rather than for maintaining real-time or near-real-time territory assignments.

Reference
While official Salesforce documentation on Territory Management batch scheduling limits is not directly quoted in the search results, Salesforce Stack Exchange discussions confirm the practical use case of scheduling these jobs hourly for timely processing , with common implementations running nightly or on similarly frequent schedules .

Explanation
When a sales representative is reassigned to a new territory, the access to historical records like Medical Inquiries must be recalculated to match the new alignment. This is a specific data visibility task. The MIRF Share Management batch job is specifically designed to handle the sharing and access recalculations for Medical Inquiry records, ensuring that reps can view historical data for HCPs in their newly assigned territories.

Correct Option:

B. MIRF Share Management
In Life Sciences Cloud, a "MIRF" refers to a Medical Inquiry Record. This object requires its own sharing recalculation when territory alignments change.

The MIRF Share Management batch job is the specific automated process that manages the sharing rules and visibility for these Medical Inquiry records.

Running this job ensures that historical medical inquiry records associated with HCPs are correctly shared with the newly assigned reps, granting them the necessary access to information for future engagements.

Incorrect Options

A. Account Object Share Rule Calculation:
This is a generic term. While account sharing is relevant, the requirement specifies Medical Inquiry records, which are distinct from Account records. Recalculating account sharing alone will not guarantee visibility into the associated Medical Inquiry data, which may have its own sharing settings.

C. Align Account to Territory:
This process typically handles the assignment of Accounts (like HCPs) to territories in the first place. After the reorganization, this job would be used to assign the HCPs to new territories. However, the problem states that the territories have already been reorganized; reps now need to view historical records, which requires recalculating access and sharing for those records, not re-running the alignment itself.