Als-Con-201 Exam Dumps - Salesforce Consultant Questions and Answers

Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.

The key word in the question is “collaborate.” Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because “availability” typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user’s territories, and the named handler that most directly supports that requirement is the sharing handler.

Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.

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 .

=========

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 Presentation Page Product is the standard Life Sciences Cloud object that links presentation content to products. Salesforce’s Life Sciences Cloud Developer Guide states that PresentationPageProduct represents the link between a presentation page and a product, and may also include a connection to product guidance or product messages. This directly matches the requirement to link Immunexis to specific presentation pages or slide content so analytics can identify which products were detailed during visits.

Salesforce’s Intelligent Content data model also includes Presentation, Presentation Linked Page, Presentation Page, Presentation Page Product, Product2, Life Science Marketable Product, Provider Visit, and visit-detailing objects. This confirms that Presentation Page Product is part of the standard content and detailing analytics architecture for Life Sciences Customer Engagement.

Option A, Presentation Linked Page, is not the best answer because it links pages within presentation structure, but it does not specifically represent the product association. Option C, Product Media Link, is not the documented standard object for connecting Life Sciences presentation pages to products. Salesforce also provides a Presentation Page Product API resource for creating or updating product and guidance associations for a presentation page, reinforcing that this is the intended object.

Therefore, the consultant should use Presentation Page Product.

Option B is correct because Salesforce Life Sciences Cloud provides a standard Data Change Requests framework for governed master-data updates. The requirement is not simply to block a change or create a manual task; it is to route critical HCP data changes to a Data Steward for review before the change is applied. Salesforce’s Life Sciences Cloud Account Management documentation describes Data Change Requests as a capability used to validate data changes by objects and fields and configure data changes by profile and record type. That aligns directly with controlled governance over fields such as Medical License Number.

The specific configuration object in the question, LifeSciDataChgPersonaDef, represents the persona-based data-change configuration. Salesforce’s Developer Guide identifies LifeSciDataChgPersonaDef as part of Data Change Requests and includes the ChangeUpdateType picklist field. Setting ChangeUpdateType to DoNotApplyChangesImmediately means changes are not applied directly by the sales rep persona and can instead be managed through the data-change governance process.

Option A is not the best answer because a custom record-triggered flow would duplicate standard Life Sciences Cloud data-change governance and could create maintenance or compliance risk. Option C is also not ideal because a validation rule only blocks the update; it does not create the governed change-request process needed for Data Steward review. Salesforce’s Data Change Requests data model includes Life Science Data Change Definition, managed fields, record types, persona definitions, and Life Science Data Change Request, confirming this is the intended standard architecture.

=========

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.

Option C is correct because Life Sciences mobile offline behavior depends on metadata cache for page layouts, metadata definitions, and offline user interface configuration. Salesforce Help for customizing the Life Sciences Cloud mobile app states that the generated metadata cache includes object schemas and metadata definitions that the mobile app stores locally to support both online and offline modes. Salesforce Help for setting up the Life Sciences Cloud mobile app also identifies object metadata cache settings, application settings, profile-based configurations, and UI customizations as part of the mobile setup process.

This directly matches the issue. The reps completed a data sync, but data sync alone does not necessarily refresh page layout metadata or translation changes used by the offline mobile app. Since the consultant changed Account page layout configuration and translation files, the correct action is to regenerate the metadata cache for the relevant profiles so offline users receive the updated metadata package.

Option A is incorrect because resetting the Sync Processor job status addresses synchronization processing, not metadata or translation availability. Option B is also incorrect because Mobile Offline Briefcase filters control which records or data are available offline; they do not publish updated page layouts or translated labels. Therefore, the consultant should generate a new metadata cache for the affected profiles.

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.

=========

The correct answer is B because the deadlines and review windows for activity-plan adjustments are configured on the Activity Plan record, specifically in the review-related configuration. Salesforce Help for creating Activity Plans references fields such as Reviewer Plan Adjustment Start Date and Reviewer Plan Adjustment End Date , which define the date range in which the manager can review adjustment requests.

The scenario describes a plan-level governance requirement: field sales reps must submit proposed visit targets by a specific deadline, and adjustments above allowed thresholds must be reviewed. This belongs to the Activity Plan configuration because the plan defines the cycle, timing, targets, review process, and adjustment behavior for the territory or provider planning period. Configuring the Review Details section ensures that the plan controls when reps can submit changes and when managers can review them.

Option A is incorrect because Global Calculation Settings for a Provider Activity Measure Type would relate to how measures or calculations are evaluated, not the submission and manager-review deadline for a specific Activity Plan. Option C is also incorrect because a Goal Definition represents a reusable planning objective, but it does not control the operational review dates and adjustment thresholds for a specific West Coast Activity Plan. Therefore, the consultant should configure the deadlines and adjustment limits on the Activity Plan record within the Review Details section .

=========

Option B is correct because Salesforce Life Sciences Cloud Medical Insights uses Medical Insight and Medical Insight Account configuration to capture and surface qualitative observations from engagements. Salesforce Help states that admins configure Medical Insight and Medical Insight Account objects by customizing the record page layout and creating required field sets. This directly matches the requirement: MSLs need to record qualitative observations and make those insights visible in the related account and visit context.

Medical Insights are intended to record observations or insights from HCP engagements, while the related Medical Insight Account object supports association of those insights with relevant accounts. By configuring layouts and field sets, the consultant controls which insight fields are available to users and how the data appears in the Life Sciences user experience. This is a standard configuration approach rather than a custom development pattern.

Option A is incorrect because feed tracking supports collaboration and Chatter-style record-feed updates; it does not configure the Medical Insights data-entry and display model. Also, “Product Insight” is not the standard object referenced for this Life Sciences Medical Insights setup. Option C is incorrect because assessment task flows and Medical Inquiry metadata are separate capabilities. Medical Inquiries manage HCP questions and responses, while Medical Insights capture field observations. Therefore, the consultant should customize the Medical Insight page layout and create field sets on Medical Insight and Medical Insight Account objects.

=========