Salesforce Als-Con-201 Exam Dumps

Option A is correct because Salesforce Life Sciences Account Summarization uses field history tracking to include the latest changes for configured fields. Salesforce Help states that, to get summaries of the latest changes in a record, history tracking must be enabled for the fields configured in the Account Summarization template. This directly matches the issue: the summaries include related data, but recent updates to specific HCP Account fields are missing. The consultant must enable history tracking for the relevant fields so Agentforce can use those tracked changes when generating the account summary.

Feed tracking is not the best answer because Chatter feed tracking is primarily used to publish field changes to the record feed for collaboration and visibility. It does not satisfy the specific Account Summarization requirement documented by Salesforce. Field Audit Trail is also not correct for this scenario. Field Audit Trail is a Salesforce Shield capability used for long-term retention and audit-policy management of field history data, but the Account Summarization setup requirement is specifically field history tracking for the fields included in the template. Salesforce's Account Summarization Data Setup documentation also confirms that the Provider Summary Lightning App Builder component can be configured to enable history tracking for fields included in the information summary.

Therefore, the consultant should enable history tracking for the Account fields configured in the Account Summarization template.

=========

The correct answer is B because the requirement is product-specific consent tracking. Salesforce's Life Sciences Consent Management data model is designed for capturing and managing HCP consent and communication preferences. The model includes objects such as Communication Subscription, Communication Subscription Consent, Contact Point Consent, and Life Science Marketable Product, which together support consent management across communication channels and products.

When a field sales rep captures whether an HCP agrees to receive communications for a specific product, the consent must be tied both to the communication/contact point consent and to the relevant Life Sciences Marketable Product. A Life Sciences Marketable Product Consent record provides that product-level association, allowing the organization to track consent preferences for a particular product rather than only a general channel or subscription.

Option A is incorrect because Data Use Purpose represents the purpose for using data, such as marketing or communication, but it does not by itself create a product-specific consent relationship between an HCP's contact point and a marketable product. Option C is also incorrect because adding a custom lookup to Communication Subscription Consent would be unnecessary and less aligned with the standard Life Sciences consent model. The best-practice configuration is to use the standard product-consent relationship by creating a Life Sciences Marketable Product Consent record linked to the relevant Contact Point Consent and product.

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 B because the requirement is to enable the Life Sciences visit and calendar setting that surfaces best-time recommendations for planning. Salesforce Help for Life Sciences Calendar states that users can schedule visits and other events while using best time recommendations. Salesforce also provides guidance for configuring filters to find best visit times, explaining that users can filter accounts by a healthcare professional's preferred engagement time to plan and schedule visits more effectively.

The key phrase in the question is that the feature must be enabled in Visit/Calendar settings. ''Best Time Settings'' is the configuration area that supports the optimization. Once enabled, the system can use historical engagement patterns and preferred engagement timing to help reps plan visits when HCPs are more likely to be available or receptive.

Option A is close in meaning, but ''Set up Provider Best Time'' describes the capability more generally rather than the setting in Visit/Calendar settings. Option C is incorrect because operating hours represent general availability windows for an account or location. Operating hours can help prevent scheduling at inappropriate times, but they do not provide intelligent recommendations based on historical engagement data. Therefore, the consultant should enable Best Time Settings.

=========

The correct answer is C because aligned account lists in Agentforce Life Sciences for Customer Engagement are configured through account list settings, where the consultant defines how the list appears to users in the mobile experience. Salesforce describes account management features in Life Sciences Cloud as enabling users to organize, prioritize, and focus on accounts through lists and filters in the Customer Engagement app. The account list configuration controls which fields appear to reps so they can quickly understand account context without opening every account record.

In this scenario, the business wants field sales reps to see the most relevant account information directly in the aligned account list. After creating the account list, the consultant should configure it as the Default list type and select up to four visible fields as columns. This gives reps a concise, mobile-friendly view of the most important account details.

Option A is incorrect because configuring the Search list affects search-result display behavior, not the aligned account list columns. It also refers to up to five account fields, which does not match the aligned account list column configuration described in the question. Option B is incorrect because assigning ownership to field sales reps does not define the visible columns in the list. Column configuration is an admin setup activity, not something resolved by record ownership. Therefore, the consultant should set the list type to Default and configure up to four visible fields.

=========