Salesforce Als-Con-201 Salesforce Certified Agentforce Life Sciences Consultant Exam Practice Test

The correct answer is B because Salesforce Life Sciences Cloud for Customer Engagement includes country-specific sample limit templates by default. Salesforce Help states that Life Sciences Cloud includes a generic sample limit template and several country-specific templates by default. These templates are intended to support sample-limit compliance where rules vary by country, including situations where statutory limits must be consistently applied without requiring administrators to rebuild complex legal rules from scratch.

In this scenario, Germany has strict legal limits on sample quantities that must apply to all HCPs. A default country-specific template is the best fit because it is designed to represent country-level sample compliance requirements in a reusable configuration. This approach reduces administrative maintenance, improves consistency, and helps ensure the sampling program follows local legal constraints.

Option A is incorrect because adding a new sample limit to custom metadata would require the admin or implementation team to manually maintain rule logic, which the requirement explicitly wants to avoid. Option C is also not the best answer because manually creating a sample limit rule in the Admin Console may work for custom business policies, but it is less appropriate when Salesforce provides a default country-specific template for statutory country rules. Therefore, the consultant should use the Default Country-Specific Template for Germany.

=========

The correct answer is B because the issue is the Activity Plan status transition. Salesforce describes Activity Plans as the mechanism to establish strategic plans and define activity goals for sales representatives over a specific period. The Life Sciences Activity Plans developer guidance also explains that activity plans define goals for employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.

In this scenario, the plan exists and has a Start Date of today, but it is still in In Progress status. Reps cannot see the plan or their targets because the plan has not moved into the operational Active state. The specific job designed for this is Update Activity Plan Status , which evaluates the plan’s dates and moves eligible plans from In Progress to Active. Running that job makes the plan available for execution and dashboard reporting.

Option A is incorrect because Activity Plan Trigger Handler suggests trigger-based automation, not the named batch process that transitions plan status according to dates. Option C, Validate Activity Plans , is also incorrect because validation checks whether the plan setup is correct; it does not perform the status transition required by the question. The consultant should run Update Activity Plan Status in the Admin Console.

=========

Option B is correct because the two requirements depend on two different territory-related maintenance jobs, and the territory information should be refreshed before historical visit sharing is recalculated. Salesforce’s Life Sciences Cloud documentation describes Provider Account Territory Information as engagement data between an account and a user within an assigned territory, including visit-related information such as next provider visit date and preferred address. After a major territory realignment, this data must be updated first so that territory-based account and visit metrics reflect the new alignments.

After that, the Visit Share Management job should be run. Salesforce Help states that, to share historical account visit records after territory realignments, admins run the Visit Share Management job so field users continue to have access to relevant historical visit data. That exactly matches the second requirement in the question: newly assigned reps must gain access to historical visit data for accounts that now belong to their territories.

Option A is incorrect because the question asks for the correct sequence, and Salesforce documentation does not indicate that Visit Share Management should be relied on to automatically execute the territory information update job. Option C is incorrect because running visit sharing before updating provider-account-territory information can share records based on stale territory data. Therefore, the correct operational sequence is: update Provider Account Territory Information first, then run Visit Share Management.

=========

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.

=========

The correct answer is C because Provider Cards are designed to consolidate key account information from multiple objects and fields into a single user-friendly account view. Salesforce Help describes Provider Cards in Life Sciences Cloud as consolidating an account’s information that is scattered across objects and fields, such as provider locations and related account information. Salesforce also describes the Provider Account Territory Info object as representing engagement data between an account and a user within an assigned territory, including account-territory context such as visit and engagement details.

The requirement is to display an indicator, not to filter accounts out of the card. Field reps need to see whether each account is a target or not. Adding an item group element to the Provider Card section and including the Targeted Account field from Provider Account Territory Info allows the template to display territory-specific targeting information. Visibility conditions can then show “Target” when the field value indicates the account is targeted and “Not Target” when it is not.

Option A is incorrect because filtering to show only targeted accounts would hide non-targeted accounts, but the requirement is to display both states. Option B is not the best answer because a repeater is used for repeating multiple related records, not for showing a single indicator from the account-territory information context. Therefore, the consultant should use an item group element with the Targeted Account field and visibility conditions.

=========

The correct answer is B because the requirement is specifically compliance-driven verification of sample holdings against an audit trail. Salesforce Help for Sample Inventory Management identifies inventory assessment types, including Ad hoc , Periodic , and Audited . It describes Ad hoc as an unplanned inventory count, Periodic as an inventory count used to comply with organizational guidelines, and Audited as a self-audit, declaration of inventory count, or peer audit.

The scenario mentions preparation for an FDA inspection, which is more rigorous than a routine count or unplanned check. The purpose is to verify current holdings against the digital audit trail and support compliance evidence. An Audited assessment is designed for this type of controlled verification because it supports audit-oriented sample inventory confirmation.

Option A, Ad Hoc , is incorrect because an ad hoc count is generally unplanned and operational, such as preparing for a visit or checking inventory outside a regular schedule. While useful, it does not best represent formal inspection readiness. Option C, Periodic , is also not the best answer because periodic counts are recurring counts based on company policy or schedule. The question focuses on audit preparation and verification against the digital audit trail, making Audited the most appropriate assessment type. Therefore, the consultant should recommend an Audited assessment.

=========

Option A is correct because Account Summarization uses a cross-object graph to define which objects and relationships are included in the generated summary. Salesforce Help states that administrators can create cross-object graphs from a predefined Account Summarization template to provide a complete view of an account and its related objects. This directly matches the requirement to include Account data and related Healthcare Provider and Contact Point Address information in the summary.

The phrase “historical data” is also important. Salesforce Account Summarization setup includes configuring history tracking for the fields included in the template, so Agentforce can summarize recent changes from the selected objects and fields. The cross-object graph defines the relationship structure, while field history tracking provides the change history used in the summary.

Option B, Actionable Relationship Center, is not the best answer. Actionable Relationship Center is used to visualize related records and relationships, but the Account Summary configuration specifically relies on cross-object graphs. Option C, Affiliation Alignment Rules, is unrelated because those rules support territory alignment for affiliated accounts, not Account Summary object relationships. Therefore, the consultant should use a Cross-Object Field History Graph to define the Account, Healthcare Provider, Contact Point Address, and related-object structure used by Agentforce Account Summary.

=========

Option B is correct because Salesforce Life Sciences Medical Inquiries uses workflow actions and persona/profile-based configuration to control who can perform specific inquiry actions, such as assigning and responding. Salesforce Help states that, before setting up Medical Inquiry, admins must make sure the required user profiles, licenses, and permission sets are in place. It also describes that medical science liaisons can assign and respond to inquiries, which confirms that these actions are intended to be controlled by role or persona.

Salesforce’s Life Sciences workflow documentation also identifies workflow actions and workflow stages as part of the Medical Inquiry management setup. The Medical Inquiries workflow setup includes action buttons, workflow stages, stage operations, and conditions, allowing admins to expose or restrict actions based on configured roles and workflow state.

Option A is not the best answer because the requirement is not simply to grant a broad app permission; it is to ensure that only a designated persona can perform the assign and respond actions in the controlled Medical Inquiry process. Option C is incorrect because a custom formula field only affects display logic and does not enforce the standard workflow-action permission model. Formula-based visibility also creates compliance risk because it can hide buttons without truly governing the underlying operation. Therefore, the consultant should create workflow actions and associate those actions with the appropriate profiles in the Life Sciences Admin Console.

=========

The correct answer is A because the described requirement matches a Provider Plan Cycle . In Salesforce Life Sciences Cloud, Activity Plans are used to organize and guide planned field activity. Salesforce Help specifically states that when creating Activity Plans, the consultant selects Provider Plan Cycle for the Usage Type. This usage type supports a planned engagement cycle where field sales reps work against defined goals for providers during a specific period.

The wording in the scenario is important: the goals are defined by the home office and executed by field sales reps during a strategic cycle. That is not the same as a broader account planning process or a standalone territory objective. A Provider Plan Cycle is designed for provider-focused execution, where commercial strategy is translated into actionable field goals for HCP engagement.

Option B, Account Plan , is incorrect because account plans are generally used for broader key account management and strategic relationship planning, especially for major accounts or account hierarchies. It does not specifically represent the activity-plan usage type for home-office-defined provider engagement cycles. Option C, Territory Objective , is also incorrect because a territory objective represents a goal or target at the territory level, but it is not the Usage Type required when creating the Activity Plan record for provider cycle execution. Therefore, the consultant should select Provider Plan Cycle .

=========

Option B is correct because Salesforce Life Sciences Cloud requires a specific API-name prefix for custom Lightning web components that should render as inline components in the Life Sciences mobile app. Salesforce Help for creating and adding an LWC as an inline component on a record page states that admins must create a custom mobile-ready LWC and add lscMobileInline_ as the prefix for the component’s API name. This exact prefix identifies the component as compatible with the Life Sciences mobile inline rendering framework.

This directly matches the issue in the scenario. The component exists and was added to the Account record page, but it does not render correctly as an inline component in the mobile app. The missing configuration is not the page placement itself, but the required naming convention that allows the Life Sciences mobile app to recognize and render the LWC inline.

Option A, lsc_mobile_, is incorrect because it is not the documented prefix for inline mobile LWCs. Option C, mobileInline_, is also incorrect because it omits the Life Sciences-specific lsc prefix and does not match the Salesforce Help requirement. Therefore, the consultant should rename or recreate the LWC API name using the lscMobileInline_ prefix so it functions correctly as an inline component in the Agentforce Life Sciences mobile app.

=========

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.

=========

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 .

The correct answer is A because Account Summarization can use different Cross-Object Field History Graph assignments by org or profile. Salesforce Help for Life Sciences Account Summarization states that administrators can create a Cross-Object Graph for Account Summarization and assign cross-object graphs to an org or profile. Salesforce also describes the Account Summarization workflow as using configured cross-object field history so summaries can include recent and relevant account changes from related objects.

In this case, KAMs see summaries that include Provider Visit and Medical Inquiry records, while field sales reps do not. Both groups have Read access to the objects, so object permission is not the root cause. The difference is most likely profile-based summarization configuration: the graph containing Provider Visit and Medical Inquiry data has been assigned to the KAM profile but not to the field sales rep profile.

Option B is incorrect because Account Summary generation in this scenario is driven by Cross-Object Field History Graph configuration, not membership in a Data 360 segment. Option C is also incorrect because the question explicitly says both user groups have Read access. View All is not the stated requirement for using a graph in summarization. Therefore, the issue is that the Cross-Object Field History Graph is not assigned to the field sales rep profile.

=========

The correct answer is A from the available options, because the requirement is to control which user actions are exposed to different roles during the Medical Inquiry lifecycle. Salesforce Help for Medical Inquiries states that organizations can define relevant workflow actions for tasks users perform in the medical inquiry process, such as inquiry submission and assignment. Salesforce also describes a compliant role separation where field sales reps can submit medical inquiries, while Medical Science Liaisons can assign and respond to them.

The ideal Salesforce Life Sciences configuration pattern is to use Medical Inquiry workflow actions and workflow paths to control status transitions, actions, and permissions. However, among the provided answer choices, record types with role-specific page layouts is the only option that directly supports restricting the available buttons and actions by user role. This enables sales users to see only draft, sign, and submit actions, while MSL users see only assignment and response actions.

Option B is incorrect because a formula field can calculate or display logic, but it cannot enforce workflow actions or user interaction permissions by itself. Option C is also incorrect because a Flow action could add custom logic, but it is not the standard configuration approach for restricting Medical Inquiry lifecycle actions. Therefore, the best available answer is A .

=========

Option C is correct because Life Sciences Cloud separates the overall visit activity from provider-specific visit details. In the Life Sciences Cloud data model, the Visit object tracks information related to a field representative’s visit to a healthcare provider and is used for Customer Engagement. Salesforce’s ProviderVisit object represents the details of a field user’s visit to a healthcare provider. The Customer Engagement data model also explains that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples.

For a group visit such as a “Lunch and Learn” with three HCPs, the overall event is represented by the parent Visit record. Each attendee requires their own provider-specific visit detail record because each HCP may have different product discussions, messages, samples, signatures, or follow-up activities. Therefore, the system creates one parent Visit and separate child Provider Visit records for each HCP attendee.

Option A is incorrect because a multi-select lookup field is not the correct Life Sciences Cloud visit data model pattern. Option B is also not correct because it implies individual parent-level Visit records for every attendee, which would duplicate the overall group interaction. The correct structure is one parent Visit for the group interaction and three child Provider Visit records, one for each Healthcare Provider attendee.

Option A is correct because routines are the Life Sciences Cloud capability intended for reusable visit schedules and recurring route patterns. Salesforce Help describes Customer Engagement features as including the ability to optimize daily schedules by showing key events and applying predefined routines on the calendar. This directly matches the requirement: field sales reps repeatedly visit the same groups of accounts across weekly routes or multi-day coverage patterns and want to reuse those planned schedules instead of rebuilding visits every time.

Routines support practical field planning because a rep can save a predefined pattern of planned visits and apply it later when the same route or schedule is needed. This is different from simply grouping accounts.

Option B is not the best answer because account lists help reps organize, filter, and target groups of accounts, but they do not by themselves preserve a reusable multi-day visit schedule. Account lists can help with planning, but they are not the direct solution for saving and reapplying a planned route. Option C is also incorrect because Activity Plans define strategic goals, targets, and activity expectations across a period. They align engagement activity to business objectives, but they are not designed to save and reapply recurring visit schedules. Therefore, the consultant should recommend creating a routine that saves the predefined set of visits and applying that routine as needed.

The correct answer is B because Salesforce Life Sciences calendar configuration represents General Event calendar entries using the standard Event object. Salesforce Help for configuring calendar events in Life Sciences Cloud lists calendar event types and shows General Event with the object/API reference Event . This means that the standard object used to store general, non-customer calendar activities is Event , even though the user-facing event type is called General Event.

In the scenario, the activities are internal items such as sales training or team lunch. They are not visits, HCP interactions, HCO engagements, or account-specific activities. They still need to appear on the rep’s calendar for capacity planning. Therefore, they should be logged as general calendar events on the standard Event object.

Option A, General Event , is tempting because it describes the business meaning of the schedule item. However, the question asks which object should be used. Salesforce’s configuration identifies the object as Event . Option C, Time Off Territory , is incorrect because that object is used to log and manage time away from assigned territories, such as PTO or territory unavailability. A team lunch or sales training is not necessarily time away from territory and is better represented as a general calendar event. Therefore, the consultant should use the Event object.

=========

Option C is correct because the requirement is product-specific and should be configured through Product Discussion Settings, not through a generic page-layout or Visit validation rule. Salesforce’s Life Sciences Cloud Visit Management data model includes Provider Visit Product Discussion as the object that represents products discussed during a visit, including key details about the product brand, therapeutic area, and related information. Salesforce also documents ProviderVisitProdDiscussion as representing additional notes or information about products discussed during a healthcare provider visit.

The question asks for a configuration that applies when a specific product, such as Immunexis, is discussed. Enabling Require Discussion in Product Discussion Settings for the product record is the most targeted standard configuration because it ties the requirement to that product’s visit discussion behavior.

Option A is not the best answer because a custom validation rule on Visit would have to inspect related product-discussion records and could become complex or unreliable for mobile visit submission behavior. Option B is also insufficient because making a Comments field required on the page layout would apply based on the layout, not specifically when Immunexis is discussed. It also would not necessarily enforce product-specific discussion requirements across all relevant visit submission paths. Therefore, the consultant should enable Require Discussion in Product Discussion Settings for the Immunexis product record.

=========

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.

=========

The correct answer is C because the HCP should be aligned to the San Francisco North territory based on an affiliation relationship with Bay Area General Hospital, not based on the HCP’s primary address. Salesforce Life Sciences Cloud documentation explains that affiliation alignment rules are used to automatically align affiliated accounts to specific territories, and that rules can be created based on criteria such as account type and affiliation details. Salesforce also describes territory alignment for affiliated accounts as a way to determine which accounts users can view and manage based on affiliation-based territory logic.

In this scenario, the hospital is already aligned to San Francisco North through geography. The HCP’s personal primary address places them in Los Angeles South, but their active work relationship with Bay Area General Hospital means they should also be aligned to San Francisco North. An affiliation alignment rule can evaluate that relationship and the relevant Affiliation Role , such as “Affiliated Practice,” so the HCP is automatically aligned to the hospital-based territory.

Option A is incorrect because a geo assignment rule using the hospital zip code would not apply correctly to an HCP whose primary address is in Beverly Hills. Option B is incorrect because the relationship is not described as a parent-account hierarchy; it is an affiliation. Therefore, the correct configuration is an affiliation alignment rule with the appropriate territory and affiliation role.

Option A is correct because the requirement is specifically to allow field sales reps to add colleagues as CC recipients when sending emails from the Life Sciences Cloud mobile app. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails from the Life Sciences Cloud mobile app from areas such as the home page, visit and account records, the content library, and the presentation player. The same Salesforce Help result also states that users can add colleagues as CC recipients, depending on the Salesforce admin’s configuration.

That wording directly matches the option “Add Colleagues as CC.” The purpose of the setting is not simply to expose a generic CC field, but to enable the Life Sciences mobile email experience where reps can copy internal colleagues on compliant business communications.

Option B, “Add CC Recipients,” is too generic and does not match the Life Sciences-specific setting name in the question. It describes the general email behavior but not the precise admin setting. Option C, “Enable CC Field Representative,” is also not correct because it implies a setting focused on copying the field representative, rather than allowing the field representative to add colleagues as CC recipients.

Therefore, to let field sales reps CC colleagues from the Agentforce Life Sciences mobile app, the consultant should enable Add Colleagues as CC.

=========

Option A is the best answer because the requirement is specifically tied to the Next Best Customer user experience. Salesforce Life Sciences Cloud uses Next Best Customer to help sales reps understand and work with the top accounts in their territory by configuring the Next Best Customer component, quick actions, scores, and rationales. Salesforce Help also references Account Scores and Rationales for Next Best Customer as part of the setup path, which confirms that scores and supporting rationale are standard parts of the Next Best Customer capability.

The reps are not asking for a separate generic charting capability or a custom extension. They want to see the data that explains why a customer is recommended and how the score was derived. Embedded charts on the Next Best Customer component meet this requirement because they keep the rationale visualization directly in the same workflow where reps prioritize accounts and plan visits.

Option B is not the best answer because extending the Next Best Customer FlexCard would imply custom development or UI customization when the requirement can be met through the standard component experience. Option C is also not the best answer because the Chart Lightning Web Component Accelerator is a generic charting component, not the Life Sciences-specific Next Best Customer configuration for showing recommendation rationale. Therefore, embedded charts on the Next Best Customer component are the correct recommendation.

=========

The correct answer is B because the business requirement says the system must block additional distributions once the sample limit is met. In Salesforce Life Sciences sample management, sample limits are used to control how many samples can be distributed to HCPs based on rules such as product, time period, and visit limits. Salesforce Help describes sample management features as supporting efficient and compliant handling and distribution of drug samples, while sample limits are part of the setup used to govern sample distribution.

The distinction between enforcement types is important. A Warning allows the rep to continue after being alerted. A Threshold is typically used to identify when a limit is nearing or reaching a defined point, but it does not satisfy the requirement to prevent excess sample distribution. An Error is the strictest enforcement behavior because it stops the transaction when the configured limit would be exceeded.

Here, Cumulus Pharma needs hard compliance enforcement: maximum 5 units per HCP per calendar year and maximum 2 units per visit. Since the system must prevent field sales reps from exceeding those values, the consultant should set the sample limit enforcement type to Error . This ensures the disbursement cannot proceed when the annual or per-visit limit has already been reached.

=========

The correct answer is B because the requirement is based on HCP affiliation with an aligned HCO plus a specialty filter. Salesforce Help for Life Sciences affiliations explains that affiliation alignment rules can automatically align affiliated accounts to specific territories. Salesforce also describes territory alignment for affiliated accounts as a way for a user’s territory to determine which accounts they can view and manage, with affiliated-account alignment supporting territory assignment through relationships.

In this scenario, the territory is driven by the hospital relationship: Bay Area General Hospital is the major HCO that defines the hospital-based territory. Both HCPs are affiliated with that hospital, but only the oncology HCP should be aligned. Therefore, the correct configuration is an affiliation alignment rule for the territory with Care Specialty = Oncology . This lets the system evaluate the affiliation relationship and apply the specialty constraint before aligning the HCP to the San Francisco Oncology territory.

Option A is incorrect because a geo assignment rule based on zip code would not correctly model the hospital-based affiliation logic. It might align accounts by location, but it does not address the HCP-HCO affiliation relationship. Option C is incorrect because sharing rules control record visibility, not territory alignment. The requirement is automatic territory alignment, so the consultant should configure an affiliation alignment rule with the oncology specialty filter.

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.

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.

=========

Option C is correct because Life Sciences mobile offline behavior depends on metadata cache for page layouts, metadata definitions, and offline user interface configuration. Salesforce Help for customizing the Life Sciences Cloud mobile app states that the generated metadata cache includes object schemas and metadata definitions that the mobile app stores locally to support both online and offline modes. Salesforce Help for setting up the Life Sciences Cloud mobile app also identifies object metadata cache settings, application settings, profile-based configurations, and UI customizations as part of the mobile setup process.

This directly matches the issue. The reps completed a data sync, but data sync alone does not necessarily refresh page layout metadata or translation changes used by the offline mobile app. Since the consultant changed Account page layout configuration and translation files, the correct action is to regenerate the metadata cache for the relevant profiles so offline users receive the updated metadata package.

Option A is incorrect because resetting the Sync Processor job status addresses synchronization processing, not metadata or translation availability. Option B is also incorrect because Mobile Offline Briefcase filters control which records or data are available offline; they do not publish updated page layouts or translated labels. Therefore, the consultant should generate a new metadata cache for the affected profiles.

Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.

The key word in the question is “collaborate.” Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because “availability” typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user’s territories, and the named handler that most directly supports that requirement is the sharing handler.

Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.

The correct answer is C because field sales reps only need to view and consume Tableau Next metrics in the Life Sciences mobile app. Salesforce Help for Tableau Next in Life Sciences Cloud explains that Tableau Next integrates with Life Sciences Cloud to provide actionable insights and enhanced visualizations. Salesforce’s Tableau Next permission guidance also identifies Tableau Next Consumer as the permission set used for viewing Tableau Next content and interacting with metrics, while creator-level access is intended for users who create and manage Tableau Next assets.

In this scenario, the technical setup has already been completed: the metrics exist, the Tableau View component has been placed on the Mobile Home Page Lightning record page, and the mobile metadata cache has been refreshed. The remaining issue is an insufficient-privileges error, which indicates that the user lacks the Tableau Next permissions required to load and consume the metric. Assigning Tableau Next Consumer grants the field rep the appropriate access level without giving unnecessary authoring privileges.

Option A, Tableau Next Creator , is incorrect because field sales reps are not creating or administering metrics; they only need to consume them. Option B, CRM Analytics Plus User , is also incorrect because the requirement is specifically for Tableau Next metrics, not legacy CRM Analytics access. Therefore, the consultant should assign the Tableau Next Consumer permission set.

=========

The correct answer is B because the requirement is persona-specific. Cumulus Pharma does not want the two additional custom objects to influence provider summaries for all users; the new insights and market intelligence must be used only when the provider summary is generated for the Key Account Manager profile. Salesforce Life Sciences Account Summarization is designed to generate contextual provider summaries from the latest changes, interactions, and insights related to a healthcare provider, and its configuration includes profile-specific setup so different personas can receive summaries grounded in the information relevant to their role.

Creating mapping records in the Provider Summary Profile Mappings tab associates the relevant summary data with the KAM profile. This is the most precise configuration because it controls which profile receives access to the additional summary context. Option A is not the best answer because creating a cross-object graph and assigning it directly to a profile is not the described administrative mechanism for persona-based provider summary control. Option C is also too broad: updating the Provider Summary Objects mapping may make the custom objects available to the summarization framework, but the key requirement is limiting usage to the new KAM persona. Profile mapping is what ensures the new objects are applied only for that persona’s provider summary generation.

=========

The correct answer is B because the Provider Activity Goal object represents the parent-level association between a provider account and an activity plan, while Provider Activity Goal Measure stores the specific measurable targets associated with that goal. Salesforce’s Life Sciences Cloud Developer Guide describes ProviderActivityGoal as storing progress toward the target for an account, including the percentage of the overall goal achieved by completed activities. Salesforce’s Life Sciences standard objects also include ProviderActivityGoalMeasure , which represents the activity goal measure details.

In practical reporting and querying terms, the analyst should use Provider Activity Goal to identify the HCP/account’s association to the plan period, and then query the related Provider Activity Goal Measure records to retrieve the specific target values, such as total interaction target, channel target, product target, or other measurable plan goals depending on configuration.

Option A is incorrect because Assessment Task and Assessment Indicator are used for assessment-style workflows, not for storing provider activity-plan target measures. They may capture structured assessment responses, but they do not represent activity-plan goal targets. Option C is incorrect because while Activity Plan is the high-level planning object, it is not the direct account-to-plan parent association described in the question, and “Account Goal” is not the specific Life Sciences child object used for provider activity target measures. Therefore, the correct parent-child pairing is Provider Activity Goal and Provider Activity Goal Measure .

=========

Option B is correct because the requirement is specifically about making Consent Management data available in the Life Sciences mobile app. Salesforce Help for Consent Management states that admins must create object metadata cache configuration for supported Consent Management objects and generate a metadata cache so sales reps can view and update consent data. Salesforce also has a dedicated setup topic for creating Object Metadata Cache Configuration, which is accessed from the Life Sciences Commercial app Admin Console under Mobile.

This is important because the Life Sciences mobile app depends on generated metadata cache so that configured objects, fields, and layouts are available to field users on iPad and mobile workflows. Without the metadata cache for the Consent Management objects, reps may not be able to access or update consent preferences during visits, even if the consent model itself is configured correctly.

Option A is not the best answer because Subscription Filtering Fields help control filtering behavior for consent subscriptions, but they do not make the consent objects available in the mobile app. Option C is also incorrect because configuring a desktop Lightning record page does not satisfy the Life Sciences mobile app metadata requirement. Therefore, the consultant should create the object metadata cache configuration for Consent Management objects and generate the metadata cache.

=========

The correct answer is C because the requirement is to lock a submitted visit report so it can no longer be edited. Salesforce Life Sciences Visit Management supports compliant planning, execution, and reporting for provider visits, and Salesforce Help directs administrators to use the Visit Management Admin Console to configure what fields users can see and how users can interact with and manage visit records.

A submitted visit report often represents a compliance-sensitive record, especially in life sciences, where visit details, sampling activity, consent capture, and inquiry handling may need to remain auditable after submission. Enabling VisitLockHandler enforces the locking behavior, while leaving Unlock submitted visit unchecked prevents the record from being reopened or edited after final submission. This configuration best matches the requirement that the submitted visit report become immutable.

Option A is incorrect because VisitAutoSaveHandler relates to saving visit data, and checking “Allow edits after submission” would contradict the stated requirement. The business specifically wants no further edits after submission. Option B is also incorrect because disabling a permissions handler and setting the status to Closed does not directly enforce immutable submitted-visit behavior. Status alone is not the same as a record lock. Therefore, the consultant should enable VisitLockHandler and ensure submitted visits remain locked by unchecking Unlock submitted visit in the Admin Console.

=========

The correct answer is C: Perform audits of Inventory Count Assessment records user permission. In Life Sciences Cloud sample inventory management, Inventory Count Assessment records are used to support inventory count and audit processes. Salesforce documentation distinguishes between conducting or performing an audit and requesting an audit. The wording in the question asks which permission is needed for a user to conduct a self-audit of their inventory count. Because the action is to perform the audit, the required permission is the user permission that allows users to perform audits of Inventory Count Assessment records.

Option A is incorrect because the Life Sciences Field Sales Representative permission set alone should not be assumed to include every inventory audit capability by default. Salesforce Life Sciences sample inventory features use specific user permissions for different inventory audit actions, so the named permission is the safer and more precise answer. Option B is incorrect because “Request audits of multiple Inventory Count Assessment records” is related to submitting or requesting audits, especially peer-audit-style workflows, not personally conducting the self-audit. Salesforce Help notes that requesting a peer audit requires the Request Multiple Inventory Count Assessment Audits user permission, which confirms that request permission is separate from the permission to perform audits.

Therefore, for a self-audit where the user is actually conducting the audit activity, the correct permission is “Perform audits of Inventory Count Assessment records.”

The correct answer is B because Life Sciences Cloud supports configuring quick actions for the mobile app through the Admin Console. Salesforce Help for Medical Insights states that Medical Insights can be made available to users in the Life Sciences mobile app so users can view their own insights and insights shared with them. Salesforce Help also describes Quick and Custom Action Management as the way to simplify user experiences in Salesforce and the Life Sciences for Customer Engagement mobile app by leveraging quick actions and custom actions.

The requirement is not merely to expose the Medical Insights tab. The rep must be able to quickly report a medical insight while managing a visit on an iPad. Configuring the Create Medical Insights quick action in the Admin Console makes the action available in the mobile workflow where reps need it. This supports fast, in-context capture of field observations during a visit.

Option A is incorrect because creating a custom action and custom flow adds unnecessary complexity when the standard quick action can be configured declaratively. Option C is also not the best answer because editing the Visit page layout and adding a generic standard action may not make the action available correctly in the Life Sciences mobile app experience. The Admin Console is the correct configuration point for mobile quick actions. Therefore, the consultant should configure the Create Medical Insights quick action using the Admin Console.

The correct answer is A because Salesforce Life Sciences Sample Inventory Management includes a process for fixing unresolved product disbursements. Salesforce Help for managing samples references Fix Unresolved Product Disbursements , and the same Sample Inventory Management area describes inventory operations such as transfers, returns, shipments, assigned batches, and product disbursements as part of the sample lifecycle.

The issue occurs because the rep physically received samples and handed them to an HCP before formally acknowledging the inventory in the system. To preserve inventory integrity, Salesforce cannot simply reduce inventory counts as if the stock were already confirmed in the rep’s available inventory. Instead, the system flags the Product Disbursement as unresolved. The rep must first acknowledge the inventory so the system recognizes the received stock, and then use the Resolve Disbursement quick action to complete the reconciliation and finalize the inventory count updates.

Option B is incorrect because the process does not require an admin to manually override an unresolved status in org-wide settings. This is an operational correction handled by the rep through the sample inventory workflow. Option C is also incorrect because forcing a Manual Adjustment would bypass the intended reconciliation process and could weaken auditability. The proper Life Sciences process is to acknowledge the inventory and then resolve the disbursement using the quick action.

=========