About this exam
Als-Con-201 is the Salesforce exam Salesforce Certified Agentforce Life Sciences Consultant.
Paid practice material for this exam is not available yet, but you can try its free sample questions.
- Exam code
- Als-Con-201
- Vendor
- Salesforce
- Practice questions
- Not available yet
- Free sample questions
- 5
- Question bank last updated
- Not available yet
Try 2 sample questions
Taken from the free sample set for Als-Con-201.
Question 1
Choose 1 option.
Cumulus Pharma developed a custom “Engagement Metrics” Lightning web component to display
competitive analysis on Healthcare Provider (HCP) record pages. The component has been
successfully deployed, added to the Lightning page, and activated as the Org Default for both
Desktop and Phone. However, when a field sales rep logs in to the Agentforce Life Sciences mobile
app, they cannot see the new component.
Which action resolves this visibility issue?
- AOption A:
Navigate to the Trigger Handler Administration tab and activate the MobileSyncHandler.
- BOption B:
Instruct the user to uninstall and reinstall the mobile app to clear local storage.
- COption C:
Create a new cache under Metadata Cache in the Admin Console.
Show answer and explanation
Correct answer: C
The correct answer is C because the Life Sciences Cloud mobile app relies on metadata cache
configuration to make updated page metadata available in the mobile experience. Salesforce
documentation for customizing the Life Sciences Cloud mobile app statesthat administratorsshould
generate a new metadata cache whenever they update Lightning record pages, page layouts, object
or schema changes, new or modified feature settings, or related mobile configuration. The official
setup path also references the Life Sciences Commercial app, Admin Console, Mobile, and Object
Metadata Cache Configuration.
In this scenario, the Lightning web component was deployed and added correctly to the Lightning
page, and the page was activated as the Org Default for Desktop and Phone. That meansthe desktop
Lightning configuration is not the issue. The missing step is refreshing or creating the mobile
metadata cache so the Agentforce Life Sciences mobile app can recognize the updated Lightning
page structure and component metadata.
Option A is incorrect because activating a trigger handler is not the normal remedy for mobile page
metadata visibility. Trigger handlers relate to backend automation behavior, not rendering a newly
added component in the mobile UI. Option B is also not the best answer because reinstalling the app is a user-side workaround and does not addressthe administrator-controlled metadata cache. The
correct administrative action is to create a new metadata cache in the Admin Console.
Question 2
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 accountsummary 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?
- AOption A:
Create a new cross-object graph from a template, add the custom objects, and assign the new
graph to the KAM profile.
- BOption B:
Create mapping records in the Provider Summary Profile Mappings tab for the two custom objects and the KAM profile.
- COption C:
Update the Provider Summary Objects mapping to add the custom objects and their mapping to the KAM profile.
Show answer and explanation
Correct answer: B
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. Thisis 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.
See all 5 free sample questions