Als-Con-201 Exam Questions & Answers

Option C is correct because the requirement is product-specific and should be configured through Product Discussion Settings, not through a generic page-layout or Visit validation rule. Salesforce's Life Sciences Cloud Visit Management data model includes Provider Visit Product Discussion as the object that represents products discussed during a visit, including key details about the product brand, therapeutic area, and related information. Salesforce also documents ProviderVisitProdDiscussion as representing additional notes or information about products discussed during a healthcare provider visit.

The question asks for a configuration that applies when a specific product, such as Immunexis, is discussed. Enabling Require Discussion in Product Discussion Settings for the product record is the most targeted standard configuration because it ties the requirement to that product's visit discussion behavior.

Option A is not the best answer because a custom validation rule on Visit would have to inspect related product-discussion records and could become complex or unreliable for mobile visit submission behavior. Option B is also insufficient because making a Comments field required on the page layout would apply based on the layout, not specifically when Immunexis is discussed. It also would not necessarily enforce product-specific discussion requirements across all relevant visit submission paths. Therefore, the consultant should enable Require Discussion in Product Discussion Settings for the Immunexis product record.

Option A is correct because this is a mobile rendering limitation, not a data or filter issue. Salesforce documentation for reports and dashboards on mobile describes differences and limitations between desktop and the Salesforce mobile app. When a dashboard component appears on desktop but not in the mobile app, the consultant should first check mobile dashboard support and component compatibility rather than assuming that the report data is missing.

The question states that the funnel charts appear on desktop, which strongly indicates that the underlying reports and reporting periods are valid. If the data were missing for the selected reporting period, the chart would fail or show no data consistently, not only on mobile. Option C is therefore not a good fit. Option B is also incorrect because dashboard filters can affect what data is shown, but they do not make an unsupported chart type render in the mobile app.

Salesforce Help also discusses making dashboards available in mobile workflows and notes that mobile dashboard behavior depends on how dashboards are embedded and rendered in the Salesforce mobile app. For this scenario, the consultant should recommend replacing the funnel chart with a mobile-supported visualization or providing an alternate dashboard component for mobile users. Therefore, the correct answer is that funnel charts are not supported in the mobile app.

Option B is correct because the Healthcare Provider object contains provider-specific Life Sciences attributes, including whether the provider is designated as a speaker for engagement. Salesforce's Life Sciences Cloud Developer Guide for the HealthcareProvider object states that the object and its fields are used by Account Management and Segmentation, and the search result for the same Salesforce object documentation identifies a field that indicates whether the provider is designated as a speaker for engagement, with a default value of false. This directly matches the question's requirement to identify whether a physician is flagged as a speaker.

Option A, Board Certification, is incorrect because board certification stores credential or certification information about a provider. It may help qualify the provider professionally, but it does not represent the commercial engagement flag that identifies whether the provider is a speaker. Option C, Person Account, is also not the best answer. In Life Sciences Cloud, physicians are commonly represented through Person Accounts, but the speaker designation is stored in the Healthcare Provider data model, not as a generic Person Account-only attribute.

Therefore, when the consultant needs to identify whether a physician is flagged as a speaker in Agentforce Life Sciences for Customer Engagement, the correct object to reference is Healthcare Provider.

The correct answer is C because Salesforce Life Sciences Sample Inventory Management is intended to provide a unified view of sample-related inventory activity. Salesforce documentation describes Sample Inventory Management as providing a unified view of transactions, shipments, inventory counts, and assigned batches, helping users stay on top of items requiring attention. This directly matches the requirement for reps to monitor batch assignments, received inventory, disbursements, transfers, and returns from one experience rather than navigating across multiple object tabs.

To make that experience available in the Agentforce Life Sciences mobile app, the consultant should expose the Sample Inventory Management dashboard through the user's navigation configuration. Adding it to Navigation Items ensures the field sales rep profile can access the dashboard from the mobile app. This is better than building a custom report type because the standard dashboard is purpose-built for Life Sciences sample inventory workflows and already aligns with the sample inventory data model and operations.

Option A is not the best answer because a custom report chart would be less functional than the standard inventory dashboard and would not provide the operational interface reps need. Option B is also incomplete. The Inventory Operations Timeline is useful for viewing transaction history, and Salesforce describes it as an overview of transactions and product requests in chronological order, but it does not provide the full dashboard experience for assigned batches, inventory counts, shipments, and operational status.

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.