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 off-label control in the visit experience is tied to product detailing behavior. In life sciences commercial engagement, product detailing governs what products, messages, indications, and approved content can be discussed or shown during a visit. Salesforce Trailhead describes Life Sciences Cloud content visibility as being filtered by territory, product assignment, and account restrictions to prevent off-label or noncompliant sharing. This aligns most closely with Visit Settings > Product Detailing Settings, because that is the visit configuration area where product discussion and detailing behavior is controlled.
The question asks where the consultant should configure whether reps are allowed to discuss products for unapproved indications. That is not a generic compliance switch; it is a visit-detailing control connected to product and indication behavior in the field engagement workflow. Product Detailing Settings are therefore the correct place to enforce whether off-label discussion is permitted, warned, or restricted according to company policy.
Option A is incorrect because "Compliance Settings > Off-Label Validation" is not the standard configuration path presented in the available options for the Life Sciences visit experience. Option C is also incorrect because Restricted Products would control whether products are available or restricted, but the scenario is specifically about discussion of unapproved indications during product detailing. Therefore, the consultant should use Visit Settings > Product Detailing Settings.
=========

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 Today's Pace is tied to the Activity Plan's calculation behavior, not the home page component itself. Salesforce describes Activity Plans as a way to establish a strategic activity plan and define activity goals for sales representatives over a specific period. Salesforce's Life Sciences Activity Plans developer guidance also describes Activity Plans as allowing administrators to define goals for specific employees, including targeted accounts, plan-cycle duration, activity types, and progress tracking.
When the business wants Today's Pace calculated based on working days, that logic should be defined where the activity plan is created and governed. Selecting Working Days in the Today's Pace Calculation Type field ensures the pacing metric uses working-day logic for the plan instead of simply counting all calendar days. This is the correct place to configure the calculation because Today's Pace reflects plan progress against the plan timeline.
Option B is incorrect because editing the home page component only controls presentation. A component can display the metric, but it should not be the source of the calculation rules for the underlying Activity Plan. Option C is also not the best answer because the requirement is not a broad global enablement setting; it asks how to calculate Today's Pace for the relevant Activity Plan. Therefore, the consultant should configure the calculation type directly on the Activity Plan by selecting Working Days.

The correct answer is B because the requirement is about making a Samples option appear in the Life Sciences mobile app sidebar, not about adding a related list to a Salesforce desktop page. Salesforce Help for setting up the Life Sciences Cloud mobile app specifically includes tasks for configuring the Visit Engagement Page and the Sidebar Menu. Salesforce also states that mobile app configuration changes are handled through the Life Sciences Commercial app's Admin Console and mobile configuration areas, with metadata cache used to sync configuration to the mobile device.
The Samples tab is part of the mobile visit engagement experience. Enabling the relevant Samples sidebar setting in Mobile App Settings makes the Samples entry available in the sidebar so reps can record sample disbursements during a visit. This is the correct configuration approach because it controls the mobile navigation and visit sidebar behavior.
Option A is incorrect because adding the Product Disbursements related list affects a record page layout, but it does not create the mobile sidebar tab required by the field sales team. Option C is also incorrect because simply placing a Lightning web component on the Visit Lightning record page does not necessarily add a Samples entry to the Life Sciences mobile sidebar menu. The consultant should enable the Samples sidebar setting in Mobile App Settings.
=========