Master Salesforce Als-Con-201: Agentforce Life Sciences Consultant Exam Prep

Correct : A

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.

=========

Correct : A

Option A is correct because the Medical Inquiries record page setup depends on configuring the Inquiry Question Answer related-list experience with the correct field set. Salesforce Help for setting up the Inquiry record page for Medical Inquiries instructs admins to add tabs and Lightning components to the Inquiry page. It also specifically references the ''Inquiry Question Answer'' tab and requires the field set name for the Inquiry Question Answer field set. That means the field set must exist before the consultant can properly configure the Medical Inquiries record page component.

This requirement fits the business process described in the question. Field sales reps create and submit medical inquiry requests, and MSLs respond to the inquiry questions. The Inquiry Question Answer object supports the question-and-answer details used by the record page component, so the field set determines which fields appear to users when viewing or entering inquiry responses.

Option B is not the best answer because a support process is typically associated with Case status handling. While medical inquiries may be operationally similar to case management, the Salesforce Life Sciences setup step in this question is specifically about the Medical Inquiries record page. Option C is also not correct because syncing statuses between Case and Medical Inquiries is not identified as the prerequisite for configuring the page. Therefore, the consultant should first create the required field set for the Inquiry Question Answer object.

=========

Correct : A

Option A is correct because Account Summarization uses cross-object graphs to determine which related objects and relationships are included in generated summaries. Salesforce Life Sciences Account Summarization setup resources reference creating a cross-object graph for Account Summarization and assigning cross-object graphs to an org or profile. This supports persona-specific summary behavior because a graph can be configured with the additional custom objects and then assigned specifically to the KAM profile.

The requirement says the new information must be used only for the new KAM persona. That means the consultant should avoid changing the default or shared provider summary mapping used by other personas. By creating a separate cross-object graph from the template, adding the two custom insight and market-intelligence objects, and assigning that graph only to the KAM profile, the consultant isolates the new summary structure to the intended users.

Option B is not the best answer because globally updating Provider Summary Objects mapping could affect more than the KAM persona if the mapping is shared. Option C is also not the best answer because the key Account Summarization configuration pattern documented by Salesforce is graph creation and graph assignment to an org or profile. Therefore, the correct configuration is to create a new cross-object graph and assign it to the KAM profile.

=========

Correct : B

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.

=========

Correct : C

The correct answer is C because Salesforce Life Sciences synchronization management guidance specifically positions Simulation Mode as the tool used to proactively identify and fix potential synchronization problems before they affect end users. Salesforce describes synchronization management as a way to ensure efficient synchronization by resolving errors quickly and using Simulation Mode to find potential problems before they impact users.

In this scenario, sales users are unable to view recently created records offline in the Agentforce Life Sciences mobile app because synchronization transactions have failed. Offline mobile availability depends on successful synchronization between Salesforce and the mobile app. A consultant should therefore recommend testing synchronization behavior in Simulation Mode, because it helps validate whether records, transactions, and configuration changes will synchronize successfully before users rely on them in the field.

Option A is not the best answer because Event Monitoring Logs are broader Salesforce security and activity logs; they are not the recommended Life Sciences-specific mechanism for proactively identifying synchronization transaction failures in the offline mobile synchronization process. Option B is also incorrect because warning emails notify users or administrators after certain conditions occur, but they do not test synchronization transactions or identify potential sync failures before users are affected. Simulation Mode is the most targeted and preventive administrative tool for this issue.