Free Salesforce Certified Agentforce Life Sciences Consultant Als-Con-201 Exam Questions

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

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

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

The correct answer is B because the requirement is 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 off-label control in the visit experience is tied to product detailing behavior. In life sciences commercial engagement, product detailing governs what products, messages, indications, and approved content can be discussed or shown during a visit. Salesforce Trailhead describes Life Sciences Cloud content visibility as being filtered by territory, product assignment, and account restrictions to prevent off-label or noncompliant sharing. This aligns most closely with Visit Settings > Product Detailing Settings, because that is the visit configuration area where product discussion and detailing behavior is controlled.

The question asks where the consultant should configure whether reps are allowed to discuss products for unapproved indications. That is not a generic compliance switch; it is a visit-detailing control connected to product and indication behavior in the field engagement workflow. Product Detailing Settings are therefore the correct place to enforce whether off-label discussion is permitted, warned, or restricted according to company policy.

Option A is incorrect because ''Compliance Settings > Off-Label Validation'' is not the standard configuration path presented in the available options for the Life Sciences visit experience. Option C is also incorrect because Restricted Products would control whether products are available or restricted, but the scenario is specifically about discussion of unapproved indications during product detailing. Therefore, the consultant should use Visit Settings > Product Detailing Settings.

The correct answer is A because Salesforce Life Sciences Cloud provides the MIRF Share Management job specifically to manage sharing for medical inquiry records. Salesforce Help states that teams can save time, reduce manual errors, and maintain the integrity and reliability of inquiry data by using the MIRF Share Management job. Salesforce also has dedicated guidance for defining sharing settings for Medical Inquiries.

The requirement is territory-based sharing: all medical inquiries in a territory must be shared with all field sales reps in that same territory. A scheduled MIRF Share Management job is the Life Sciences-specific mechanism designed to maintain this sharing behavior for medical inquiry records. This is preferable because medical inquiry workflows often have regulated data-handling and access-control requirements, so using the purpose-built sharing-management capability is safer and more maintainable than creating generic sharing automation.

Option B is not the best answer because the described configuration is not simply a generic Territory Management setting in the Life Sciences Admin Console. The question asks specifically how to share medical inquiry records, and Salesforce points to MIRF Share Management for that purpose. Option C is also incorrect because an owner-based sharing rule on the Inquiry object would be a generic Salesforce sharing approach. It may not correctly reflect Life Sciences medical inquiry sharing logic or maintain the intended record integrity. Therefore, the consultant should schedule the MIRF Share Management job.

Option C is correct because Subject Management is the standard approach for organizing Medical Insights by topic. Salesforce Life Sciences Medical Insights allows users to capture, view, and work with insights from HCP engagements. Salesforce Help describes Medical Insights as a feature that can be made available in the Life Sciences mobile app so users can view their own insights and insights captured by users in their territories. Salesforce also documents Medical Insight object setup through page layouts and field sets, which supports structured capture and display of insight details.

The question asks for a way to organize insights for easy searching and filtering by topics. Subject Management fits that need because subjects provide a controlled way to classify insights into topics or categories. This helps reps and analytics teams search, filter, and review insights consistently rather than relying only on free-text notes.

Option A, Life Science Insight List Filter, is not the best answer because filtering is a user experience mechanism, not the underlying topic-management configuration. Option B, Actionable List Filter Criteria, is also not correct because actionable lists and filter criteria are broader account or list-management concepts; they do not define Medical Insight topics. Therefore, to organize Medical Insights by topic for better searching and filtering, the consultant should recommend Subject Management.

Option B, Product Item, is correct because Salesforce defines ProductItem as the object that represents the stock of a particular product at a particular location. Salesforce Field Service developer documentation states that ProductItem represents stock of a product at a location, such as items stored in a warehouse. The Field Service Inventory Management data model also states that inventory management starts with product items, which represent stock of a particular product at a particular location.

This exactly matches the reporting requirement. The analyst needs to calculate how much ''Immunexis 50mg'' exists in each sales rep's trunk. In Salesforce inventory architecture, each rep's trunk is modeled as a Location, and the stock quantity of a given Product2 at that Location is represented by Product Item records. Reporting on Product Item allows the analyst to group by Location, filter or group by Product, and calculate quantity or value.

Option A, Location Group, is incorrect because a location group organizes or groups locations; it does not represent the actual stock quantity of a specific product at an individual location. Option C, Product Request, is also incorrect because a product request is used for requesting or moving inventory, not for representing the on-hand inventory balance. Therefore, Product Item is the primary data source for this report.

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 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.

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 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.