Als-Con-201 Exam Dumps : Salesforce Certified Agentforce Life Sciences Consultant

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.

=========

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

=========