The correct answer is A because Salesforce's Remote Engagement setup guidance for Life Sciences Cloud specifically identifies the Experience Cloud site as the place where language support is configured for remote engagement experiences. Salesforce Help for creating an Experience Cloud site for Remote Engagement states that, for language support, the administrator should select Components and drag the Language Selector component to the page. This directly supports the requirement for HCPs to review and accept terms and conditions in multiple languages when joining remote visits.
Remote Engagement involves an HCP-facing experience, not only a sales-rep mobile action. The terms and conditions are presented through the Experience Cloud site used for the remote session, so the language-selection capability must be available there. Adding the Language Selector lets the HCP choose the appropriate language in the site experience before reviewing the terms.
Option B is incorrect because configuring the Start Remote Session quick action may help reps launch or manage remote sessions, but it does not provide the HCP-facing multilingual site control required for terms and conditions. Option C is also incorrect because a survey can collect feedback or preferences, but it is not the Salesforce-recommended way to localize the terms-and-conditions experience. The correct configuration is to add the Language Selector component to the Experience Cloud site.
=========

Option A is correct because the requirement is specifically to allow field sales reps to add colleagues as CC recipients when sending emails from the Life Sciences Cloud mobile app. Salesforce Help for customizing and sending emails in Life Sciences Cloud states that users can send emails from the Life Sciences Cloud mobile app from areas such as the home page, visit and account records, the content library, and the presentation player. The same Salesforce Help result also states that users can add colleagues as CC recipients, depending on the Salesforce admin's configuration.
That wording directly matches the option "Add Colleagues as CC." The purpose of the setting is not simply to expose a generic CC field, but to enable the Life Sciences mobile email experience where reps can copy internal colleagues on compliant business communications.
Option B, "Add CC Recipients," is too generic and does not match the Life Sciences-specific setting name in the question. It describes the general email behavior but not the precise admin setting. Option C, "Enable CC Field Representative," is also not correct because it implies a setting focused on copying the field representative, rather than allowing the field representative to add colleagues as CC recipients.
Therefore, to let field sales reps CC colleagues from the Agentforce Life Sciences mobile app, the consultant should enable Add Colleagues as CC.
=========

Data Use Purpose is the correct answer. In Salesforce Life Sciences Cloud Consent Management, a Communication Subscription represents a specific subscription, such as a newsletter, and the consent model must also connect that subscription to the business purpose and relevant Life Sciences product. Salesforce's Life Sciences Help documentation specifically describes creating a Data Use Purpose record to associate a Life Sciences Marketable Product with a Communication Subscription. That directly matches the scenario: "Immunology Monthly" is the Communication Subscription, and "Immunexis" is the product record that must be linked for consent capture.
Engagement Channel Type is not correct because it represents the channel through which the HCP can be contacted, such as email, SMS, or other communication methods. It defines the communication channel, not the relationship between a subscription and a marketable product. Communication Subscription Consent is also not correct because it represents an individual customer's or HCP's consent preference for a subscription. In other words, that record is created or updated when the HCP opts in or opts out; it is not the setup record used to link the newsletter subscription to the product. Salesforce's Life Sciences standard object documentation also describes Communication Subscription Consent as representing a customer's consent to a communication subscription, reinforcing that it stores the HCP's consent outcome rather than the product-subscription configuration.
=========

Option A is correct because routines are the Life Sciences Cloud capability intended for reusable visit schedules and recurring route patterns. Salesforce Help describes Customer Engagement features as including the ability to optimize daily schedules by showing key events and applying predefined routines on the calendar. This directly matches the requirement: field sales reps repeatedly visit the same groups of accounts across weekly routes or multi-day coverage patterns and want to reuse those planned schedules instead of rebuilding visits every time.
Routines support practical field planning because a rep can save a predefined pattern of planned visits and apply it later when the same route or schedule is needed. This is different from simply grouping accounts.
Option B is not the best answer because account lists help reps organize, filter, and target groups of accounts, but they do not by themselves preserve a reusable multi-day visit schedule. Account lists can help with planning, but they are not the direct solution for saving and reapplying a planned route. Option C is also incorrect because Activity Plans define strategic goals, targets, and activity expectations across a period. They align engagement activity to business objectives, but they are not designed to save and reapply recurring visit schedules. Therefore, the consultant should recommend creating a routine that saves the predefined set of visits and applying that routine as needed.

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.