Pass the Salesforce Consultant Als-Con-201 Questions and answers with ExamsMirror

Option A is correct because Salesforce Help for setting up the Inquiry record page for Medical Inquiries explicitly states that, to view timeline details for inquiries, the consultant should drag the Timeline component to the page. The requirement in the question is to expose a chronological list of key events and changes associated with the inquiry. That is exactly the purpose of the Timeline component on the Medical Inquiries record page.

Salesforce also documents Enhanced Timeline for Life Sciences Cloud, explaining that the Enhanced Timeline component shows key events relating to a person or a record. This supports the use case of giving users a consolidated, chronological view of relevant inquiry activity, rather than requiring them to inspect multiple related lists or audit records separately.

Option B is not the best answer because field history tracking and the standard History component are used for field-level audit history, not the Life Sciences Medical Inquiries timeline experience. Option C is also incorrect because adding an Inquiry History related list would expose related records, but it would not provide the configured timeline component experience described in Salesforce’s Medical Inquiries setup documentation.

Therefore, the consultant must drag the Timeline component onto the Lightning record page and configure its component details for the Inquiry record page.

The correct answer is A because Salesforce Life Sciences Sample Inventory Management includes a process for fixing unresolved product disbursements. Salesforce Help for managing samples references Fix Unresolved Product Disbursements , and the same Sample Inventory Management area describes inventory operations such as transfers, returns, shipments, assigned batches, and product disbursements as part of the sample lifecycle.

The issue occurs because the rep physically received samples and handed them to an HCP before formally acknowledging the inventory in the system. To preserve inventory integrity, Salesforce cannot simply reduce inventory counts as if the stock were already confirmed in the rep’s available inventory. Instead, the system flags the Product Disbursement as unresolved. The rep must first acknowledge the inventory so the system recognizes the received stock, and then use the Resolve Disbursement quick action to complete the reconciliation and finalize the inventory count updates.

Option B is incorrect because the process does not require an admin to manually override an unresolved status in org-wide settings. This is an operational correction handled by the rep through the sample inventory workflow. Option C is also incorrect because forcing a Manual Adjustment would bypass the intended reconciliation process and could weaken auditability. The proper Life Sciences process is to acknowledge the inventory and then resolve the disbursement using the quick action.

=========

The correct answer is C because Salesforce Life Sciences Sample Inventory Management automatically adjusts the system count to match the actual count when an inventory-count discrepancy is recorded. Salesforce Help for Discrepancy Adjustments for Inventory Counts states that when a discrepancy is recorded in the inventory count, Sample Inventory Management adjusts the system count positively or negatively to match the actual count.

In this case, the physical count is 95 units, while the system balance is 100 units. The system must reflect the physical reality immediately for audit accuracy. Therefore, Life Sciences creates an adjustment transaction for the negative difference of 5 units so that the recorded inventory balance aligns with the counted quantity. This preserves the audit trail because the discrepancy is not silently overwritten; it is reconciled through an inventory adjustment transaction.

Option A is incorrect because a Product Request is used to request or replenish inventory, not to reconcile a counted discrepancy. The system should first record the loss or variance before any replenishment process is considered. Option B is also incorrect because locking the Product Item and triggering an assessment workflow is not the standard discrepancy reconciliation behavior described for inventory counts. The correct behavior is automatic generation of an adjustment transaction to reconcile the system balance with the physical count.

Option B, Action Plan Template Assignment, is correct. In Salesforce Life Sciences Cloud Key Account Management, strategic planning uses goal definitions and action plan templates to standardize account-planning execution. A Goal Definition represents the reusable strategic goal blueprint, such as “Secure Formulary Access.” An Action Plan Template defines the repeatable tactical tasks that should be generated when that goal is added to an account plan. The object that connects these two pieces is ActionPlanTemplateAssignment. Salesforce’s Life Sciences Cloud Developer Guide describes ActionPlanTemplateAssignment as the object to which the action plan template is associated, including examples such as a problem definition, goal definition, or care plan template. This directly matches the scenario: the action plan template must be associated with the goal definition so that importing the predefined strategic goal can generate the related tactical action plan.

Option A is not correct because “Action Plan Template Goal” is not the standard object identified in the Salesforce Life Sciences Cloud data model for this association. Option C is also incorrect because an Action Plan Template Participant would relate to participants, not the relationship between a goal definition and an action plan template. Salesforce’s Key Account Management Account Plan data model also includes Action Plan Template Assignment, Action Plan Template, Action Plan Template Item, and Goal Definition as part of the standard account-planning architecture.

Therefore, the correct object for linking the tactical action plan template to the reusable strategic goal definition is Action Plan Template Assignment.

=========

The correct answer is C: Perform audits of Inventory Count Assessment records user permission. In Life Sciences Cloud sample inventory management, Inventory Count Assessment records are used to support inventory count and audit processes. Salesforce documentation distinguishes between conducting or performing an audit and requesting an audit. The wording in the question asks which permission is needed for a user to conduct a self-audit of their inventory count. Because the action is to perform the audit, the required permission is the user permission that allows users to perform audits of Inventory Count Assessment records.

Option A is incorrect because the Life Sciences Field Sales Representative permission set alone should not be assumed to include every inventory audit capability by default. Salesforce Life Sciences sample inventory features use specific user permissions for different inventory audit actions, so the named permission is the safer and more precise answer. Option B is incorrect because “Request audits of multiple Inventory Count Assessment records” is related to submitting or requesting audits, especially peer-audit-style workflows, not personally conducting the self-audit. Salesforce Help notes that requesting a peer audit requires the Request Multiple Inventory Count Assessment Audits user permission, which confirms that request permission is separate from the permission to perform audits.

Therefore, for a self-audit where the user is actually conducting the audit activity, the correct permission is “Perform audits of Inventory Count Assessment records.”

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.

=========

The correct answer is C because Provider Account Territory Information is the standard object used to store provider-level territory information, including calculated territory-specific visit metrics. Salesforce Help states that the Account Address batch job creates Provider Account Territory Information records and calculates values such as year-to-date visits , next visit, and last visit. This directly matches the requirement to track the HCP’s Year-to-Date Visit Count separately by territory assignment.

The key detail is that the HCP is assigned to multiple territories. A single account-level field would not be sufficient because the visit count must be different depending on the territory relationship. Provider Account Territory Information supports this by storing data at the intersection of provider account and territory, allowing the same HCP to have separate calculated values for each assigned territory.

Option A, Provider Account Territory Summary , sounds plausible because it includes “summary,” but the Salesforce-documented batch process specifically creates Provider Account Territory Information records for territory-specific metrics. Option B, User Territory Affiliation Information , is not correct because the requirement is about an HCP’s territory-specific visit count, not user-territory affiliation data. Therefore, the consultant should use Provider Account Territory Information .

=========

Option C is correct because the requirement is strict enforcement. Salesforce Help for Sample Limit Template types states that when the enforcement type is Error, distributions are blocked after limits are met. This directly matches the legal requirement in the question: the field sales rep must be prevented from submitting the visit when the disbursement quantity exceeds the allowed limit.

A controlled substance requires a hard compliance stop rather than a soft business warning. Setting the Limit Enforcement Type to Error ensures that the rep receives an error message and must correct the sample quantity before continuing. This protects the company from noncompliant disbursements and supports controlled sampling governance.

Option A is incorrect because Warning is a soft-limit behavior. A warning may alert the rep that the limit has been exceeded, but it allows the rep to proceed. That does not meet the requirement to strictly prevent the transaction. Option B is also not the best answer because “Block” is not the documented Limit Enforcement Type in the sample-limit template options shown in Salesforce’s Life Sciences sample limit resources. The documented strict enforcement behavior is Error. Therefore, for controlled substances or any legally required hard stop, the consultant should configure the Sample Limit Template with Limit Enforcement Type set to Error.

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 Visit Management supports adding internal users as visitors to a visit. Salesforce Help for Add Internal Users as Visitors states that administrators can configure the visitors feature so field reps can record internal colleagues who participate in visits and automatically share visit data with them. This directly matches the requirement to include an MSL in the scheduled remote visit and track that person’s participation.

The MSL is not the primary HCP attendee and does not need a separate visit record. Instead, the MSL is an internal participant supporting the visit. Using the standard Add Visitors (Users) to a Visit action keeps the visit record intact while documenting the MSL as a participating internal user. It also supports better compliance, collaboration, and reporting because the MSL’s involvement is recorded against the actual visit.

Option A is incorrect because creating a separate Visit record would fragment the visit history and could cause duplicate or inconsistent reporting. Option B is incomplete because emailing the meeting link may help the MSL join the session, but it does not track the MSL’s participation in the Life Sciences Visit Management data model. The correct standard action is Add Visitors (Users) to a Visit .

=========