Salesforce Als-Con-201 - Salesforce Certified Agentforce Life Sciences Consultant

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 the out-of-the-box Account Address batch job resolves duplicate primary Contact Point Address records by using the last modified record that is marked as primary . Salesforce Help for Life Sciences Account Address batch jobs states that if multiple Contact Point Address records are marked as primary, the job uses the last modified record marked as primary. This directly matches the scenario where the sales rep creates or updates another Contact Point Address and marks it as primary while the previous primary address remains unchanged.

Because both address records are now marked as primary, the batch job must determine which one should be treated as the effective primary address. Since the newly captured address was modified most recently and is marked as primary, the nightly Account Address batch job will use that last modified primary record. This behavior helps Life Sciences Cloud maintain a consistent primary-address reference when conflicting primary flags exist.

Option A is incorrect because the previous primary record is no longer the most recently modified primary record. The system does not automatically prefer the older record simply because it was primary first. Option B is incorrect because the newly captured record is not non-primary; the rep explicitly marked it as primary. The rule applies to records marked as primary, and among those records, the most recently modified one is selected. Therefore, the batch job will use the last modified record .

=========

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 .

=========

The correct answer is C because aligned account lists in Agentforce Life Sciences for Customer Engagement are configured through account list settings, where the consultant defines how the list appears to users in the mobile experience. Salesforce describes account management features in Life Sciences Cloud as enabling users to organize, prioritize, and focus on accounts through lists and filters in the Customer Engagement app. The account list configuration controls which fields appear to reps so they can quickly understand account context without opening every account record.

In this scenario, the business wants field sales reps to see the most relevant account information directly in the aligned account list. After creating the account list, the consultant should configure it as the Default list type and select up to four visible fields as columns. This gives reps a concise, mobile-friendly view of the most important account details.

Option A is incorrect because configuring the Search list affects search-result display behavior, not the aligned account list columns. It also refers to up to five account fields, which does not match the aligned account list column configuration described in the question. Option B is incorrect because assigning ownership to field sales reps does not define the visible columns in the list. Column configuration is an admin setup activity, not something resolved by record ownership. Therefore, the consultant should set the list type to Default and configure up to four visible fields.

=========

The correct answer is A because the requirement is for a single embedded, interactive graph that visualizes multiple relationship types around an HCP. Salesforce describes Actionable Relationship Center (ARC) as a capability for viewing relationships among people and businesses in an interactive graph. Salesforce also describes ARC as supporting entity hierarchy and entity relationship visualization, and Life Sciences provider-card guidance references account-related object relationships in an ARC graph.

This scenario includes more than a simple parent-child hierarchy. The HCP has an employment relationship with one hospital, affiliation relationships with two additional hospitals, and a Key Opinion Leader role for a research study. ARC is designed for this type of multi-object, multi-relationship visualization. It allows users to see related entities in context and navigate through connected records from a graph-based interface rather than moving through several related lists.

Option B, Einstein Relationship Insights , is incorrect because it is not the Life Sciences page component used to display a configured relationship graph for HCP-related records. Option C, Account Hierarchy Visualization , is also too limited because account hierarchy is generally used for hierarchical account structures, not a broader relationship network involving employment, affiliations, KOL status, and research-study connections. Since the requirement calls for an interactive relationship graph embedded on the record page, the consultant should implement Actionable Relationship Center .

=========

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.

=========