Free Salesforce Als-Con-201 Practice Exam with Questions & Answers

Digital Verification is the correct answer because Salesforce Life Sciences resources describe it as the native capability used to manage electronic signatures in Salesforce and support an organization’s 21 CFR Part 11 compliance requirements. Salesforce Help states that Electronic Signatures can be set up using the Digital Verifications feature, allowing signatures to be managed in Salesforce instead of relying on a third-party application. It also references creating a “signature trail,” which is the key concept in this question: the signature is not just a stored image, but part of a controlled verification process tied to the signed record and signer context.

Field Audit Trail is not the best answer because it tracks field history and retention for data changes; it does not provide the electronic-signature process required for HCP sample acknowledgments. Adobe Sign is also not the best answer because the question asks for the Salesforce Life Sciences feature that generates the audit trail inside the Life Sciences process. The Salesforce Developer Guide also identifies Digital Verification standard objects as part of the electronic-signature data model, reinforcing that Digital Verification is the Life Sciences capability designed for this use case.

Option A, Provider Account Territory Summary, is the best answer because the requirement is to store summarized, territory-specific account metrics. The HCP belongs to more than one territory, and Cumulus Pharma must track Year-to-Date Visit Counts independently for each territory. Salesforce’s Life Sciences Account Management data model includes both Provider Account Territory Information and Provider Account Territory Summary as standard entities for managing healthcare provider and organization accounts, related profiles, and territory-specific information.

Provider Account Territory Summary is the object designed for summarized metrics at the provider-account-and-territory level. That makes it the appropriate place for values such as Year-to-Date Visit Counts, which are calculated or aggregated metrics rather than the raw alignment relationship itself.

Option C, Provider Account Territory Information, is related but not the best answer. Salesforce’s Developer Guide describes ProviderAcctTerritoryInfo as representing engagement data between an account and a user within an assigned territory, including items such as next provider visit date and preferred address. However, the question asks for territory-specific account metrics, not general engagement information between a user, account, and territory. Option B, Provider Account Territory Association, is also not correct because the issue is not simply associating an account to a territory. The HCP is already assigned to both territories. The need is to store independent summarized metrics for each territory. Therefore, Provider Account Territory Summary is the correct standard object.

=========

The correct answer is B because the business requirement says the system must block additional distributions once the sample limit is met. In Salesforce Life Sciences sample management, sample limits are used to control how many samples can be distributed to HCPs based on rules such as product, time period, and visit limits. Salesforce Help describes sample management features as supporting efficient and compliant handling and distribution of drug samples, while sample limits are part of the setup used to govern sample distribution.

The distinction between enforcement types is important. A Warning allows the rep to continue after being alerted. A Threshold is typically used to identify when a limit is nearing or reaching a defined point, but it does not satisfy the requirement to prevent excess sample distribution. An Error is the strictest enforcement behavior because it stops the transaction when the configured limit would be exceeded.

Here, Cumulus Pharma needs hard compliance enforcement: maximum 5 units per HCP per calendar year and maximum 2 units per visit. Since the system must prevent field sales reps from exceeding those values, the consultant should set the sample limit enforcement type to Error . This ensures the disbursement cannot proceed when the annual or per-visit limit has already been reached.

=========

Option A is correct because Life Sciences Workflow Management is designed to control what users can do at different stages of a Life Sciences process, including Medical Inquiries. Salesforce Help for configuring Life Sciences workflow paths states that admins define stage operation conditions that must be met to grant users access to operations. Salesforce also provides specific setup guidance for workflow stages used to manage Medical Inquiries, including adding actions to stage operations and configuring stage operation conditions.

This fits the requirement exactly. The access rules change depending on the Medical Inquiry’s stage: Draft, Assigned, Responded, Signed, or Submitted. Salesforce’s Inquiry object documentation confirms these inquiry statuses are standard values used in the Medical Inquiries process.

Option B is incorrect because criteria-based sharing rules on Case would not dynamically manage stage-specific CRUD behavior for the Life Sciences Inquiry workflow. Also, the question is about Medical Inquiries, not generic Case sharing. Option C is also incorrect because validation rules and dynamic page layouts can restrict or hide fields and actions, but they do not provide the standard stage-based security model required here. Therefore, the consultant should configure Stage Operations and Stage Operation Conditions within Life Sciences Workflow Management.

=========

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 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.

=========

The correct answer is B because the standard field that represents whether a received document is incoming or outgoing is Direction . Salesforce’s Life Sciences Cloud Developer Guide for the ReceivedDocument object lists direction values such as INCOMING — Incoming and OUTGOING — Outgoing , which directly matches the reporting requirement in the scenario.

The operations manager wants to analyze document volume based on whether consent forms are flowing into the organization from HCPs or being sent out to HCPs. That is a directional reporting requirement, not a document lifecycle or status requirement. Grouping the report by the Direction field allows the team to separate inbound consent forms from outbound documents using standard Salesforce data rather than creating a custom field or relying on interpretation.

Option A, Flow Type , is incorrect because the question is not asking about a business process type, document-processing flow, or automation path. It specifically asks for whether the document was incoming or outgoing. Option C, Document Status , is also incorrect because status would indicate where the document is in its lifecycle, such as received, processed, pending, or completed depending on configuration. Status does not define the direction of the document exchange. Therefore, the consultant should recommend grouping and filtering the report by the standard Direction field on Received Document.

=========

Option A is correct because Life Sciences Cloud Visit Management includes an Admin Console configuration called Map Visit Types to Accounts. This configuration is designed to associate the correct Visit record type with the relevant Account type. Salesforce Life Sciences setup resources reference Visit Management Admin Console tasks, including Configure Visit Settings, Activate Trigger Handlers, Schedule Visit Jobs, and Map Visit Types to Accounts. That mapping is the appropriate configuration when a company has separate visit processes for HCOs and HCPs.

In this scenario, Cumulus Pharma already has separate Account record types and separate Visit record types. The missing configuration is the relationship between those two sets of record types. Mapping Visit Types to Accounts ensures that, when a sales rep creates a visit from an HCO account, the HCO visit process is used, and when the rep creates a visit from an HCP account, the HCP visit process is used.

Option B is not the best answer because trigger handlers enable underlying Visit Management automation, but they do not define which Visit type is associated with each Account type. Option C is also incorrect because page layouts control what users see on record pages; they do not determine the visit process or Visit record type mapping. Therefore, the consultant should configure mappings in Map Visit Types to Accounts.

=========

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.

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.

=========