Salesforce Als-Con-201 Exam With Confidence Using Practice Dumps

Option B, Action Plan Template Assignment, is correct. In Salesforce Life Sciences Cloud Key Account Management, strategic planning uses goal definitions and action plan templates to standardize account-planning execution. A Goal Definition represents the reusable strategic goal blueprint, such as “Secure Formulary Access.” An Action Plan Template defines the repeatable tactical tasks that should be generated when that goal is added to an account plan. The object that connects these two pieces is ActionPlanTemplateAssignment. Salesforce’s Life Sciences Cloud Developer Guide describes ActionPlanTemplateAssignment as the object to which the action plan template is associated, including examples such as a problem definition, goal definition, or care plan template. This directly matches the scenario: the action plan template must be associated with the goal definition so that importing the predefined strategic goal can generate the related tactical action plan.

Option A is not correct because “Action Plan Template Goal” is not the standard object identified in the Salesforce Life Sciences Cloud data model for this association. Option C is also incorrect because an Action Plan Template Participant would relate to participants, not the relationship between a goal definition and an action plan template. Salesforce’s Key Account Management Account Plan data model also includes Action Plan Template Assignment, Action Plan Template, Action Plan Template Item, and Goal Definition as part of the standard account-planning architecture.

Therefore, the correct object for linking the tactical action plan template to the reusable strategic goal definition is Action Plan Template Assignment.

=========

Option B is correct because Salesforce Life Sciences Activity Plans use weighted goals to measure activities differently based on business importance. Salesforce Help for creating Activity Plans states that, to track weighted goals, administrators create Provider Activity Goal Measure records to define weights, select Weighted Goal in the Type field, and assign a value in Activity Weight Value. This directly supports the requirement to measure high-impact activities differently from standard activities.

Activity Plans are designed to transform provider interaction strategies into actionable goals and targets for field representatives. When certain activities with specific HCPs are more strategically important, weighted goals allow those activities to contribute differently to plan performance. This is more precise than simply counting every activity equally.

Option A is incorrect because “High Impact Goal” is not the documented Type value for this configuration. The Salesforce Help wording identifies “Weighted Goal” as the Type value used for weighted measurement. Option C is also not correct because the documented field is Activity Weight Value, not Activity Impact. Even if a percentage-based concept sounds plausible, the standard configuration step is to set the Provider Activity Goal Measure Type to Weighted Goal and enter the weight value. Therefore, the consultant should select Weighted Goal for the Type field.

=========

Option A is correct because Account Summarization uses cross-object graphs to determine which related objects and relationships are included in generated summaries. Salesforce Life Sciences Account Summarization setup resources reference creating a cross-object graph for Account Summarization and assigning cross-object graphs to an org or profile. This supports persona-specific summary behavior because a graph can be configured with the additional custom objects and then assigned specifically to the KAM profile.

The requirement says the new information must be used only for the new KAM persona. That means the consultant should avoid changing the default or shared provider summary mapping used by other personas. By creating a separate cross-object graph from the template, adding the two custom insight and market-intelligence objects, and assigning that graph only to the KAM profile, the consultant isolates the new summary structure to the intended users.

Option B is not the best answer because globally updating Provider Summary Objects mapping could affect more than the KAM persona if the mapping is shared. Option C is also not the best answer because the key Account Summarization configuration pattern documented by Salesforce is graph creation and graph assignment to an org or profile. Therefore, the correct configuration is to create a new cross-object graph and assign it to the KAM profile.

=========