MENU
Choose 1 option.
Cumulus Pharma uses Agentforce Account Summary to access the latest and most relevant account information before each Healthcare Provider (HCP) interaction. The company is onboarding a new persona for its Key Account Managers (KAMs). The provider account summary generated for this new persona needs information from two additional custom objects that store insights and market intelligence.
Which configuration ensures the new information is used only while generating the provider summary for this new persona?
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.
=========