Salesforce Updated Als-Con-201 Exam Questions and Answers by zayaan

The correct answer is C because field sales reps only need to view and consume Tableau Next metrics in the Life Sciences mobile app. Salesforce Help for Tableau Next in Life Sciences Cloud explains that Tableau Next integrates with Life Sciences Cloud to provide actionable insights and enhanced visualizations. Salesforce’s Tableau Next permission guidance also identifies Tableau Next Consumer as the permission set used for viewing Tableau Next content and interacting with metrics, while creator-level access is intended for users who create and manage Tableau Next assets.

In this scenario, the technical setup has already been completed: the metrics exist, the Tableau View component has been placed on the Mobile Home Page Lightning record page, and the mobile metadata cache has been refreshed. The remaining issue is an insufficient-privileges error, which indicates that the user lacks the Tableau Next permissions required to load and consume the metric. Assigning Tableau Next Consumer grants the field rep the appropriate access level without giving unnecessary authoring privileges.

Option A, Tableau Next Creator , is incorrect because field sales reps are not creating or administering metrics; they only need to consume them. Option B, CRM Analytics Plus User , is also incorrect because the requirement is specifically for Tableau Next metrics, not legacy CRM Analytics access. Therefore, the consultant should assign the Tableau Next Consumer permission set.

=========

Option B is correct because the requirement is specifically about making Consent Management data available in the Life Sciences mobile app. Salesforce Help for Consent Management states that admins must create object metadata cache configuration for supported Consent Management objects and generate a metadata cache so sales reps can view and update consent data. Salesforce also has a dedicated setup topic for creating Object Metadata Cache Configuration, which is accessed from the Life Sciences Commercial app Admin Console under Mobile.

This is important because the Life Sciences mobile app depends on generated metadata cache so that configured objects, fields, and layouts are available to field users on iPad and mobile workflows. Without the metadata cache for the Consent Management objects, reps may not be able to access or update consent preferences during visits, even if the consent model itself is configured correctly.

Option A is not the best answer because Subscription Filtering Fields help control filtering behavior for consent subscriptions, but they do not make the consent objects available in the mobile app. Option C is also incorrect because configuring a desktop Lightning record page does not satisfy the Life Sciences mobile app metadata requirement. Therefore, the consultant should create the object metadata cache configuration for Consent Management objects and generate the metadata cache.

=========

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 states that administrators should 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 means the 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 address the administrator-controlled metadata cache. The correct administrative action is to create a new metadata cache in the Admin Console.

=========

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.

=========