Explanation:

B. A Care Plan must have a Coordinator as a member of the Care Team before a Care Plan Template can be applied.
This is true because Health Cloud requires a designated Care Coordinator to be assigned to a Care Team before applying templates, ensuring accountability in care management.

C. If the Problem and Goal objects use Private Sharing, Care Team Membership provides access to these objects.
This is true because Care Team membership grants implicit access to related care objects (like Problems and Goals) when they're set to private sharing mode, without needing additional sharing rules.

The other options are incorrect because:
A. Care Team Members are actually required (not optional) for a Care Plan to function properly in Health Cloud.
D. Communities are not required for external Care Team members - they can be added through other sharing methods like Person Accounts or external user licenses.

Explanation:

A. Install the Health Cloud Care Request Extensions unmanaged package ❌
This is outdated. Earlier pilots used unmanaged Care Request Extensions, but the supported setup today uses Utilization Management Extensions, not Care Request Extensions.

B. Assign PSLs to Salesforce Classic users ❌
UM is supported only in Lightning Experience. Assigning PSLs to Classic users won’t meet requirements.

C. Assign PSLs to Salesforce Lightning users ✅
To access UM features, users need:
Health Cloud Permission Set License
Health Cloud Platform Permission Set License
And then the Health Cloud Utilization Management Permission Set.
This is required for Lightning users (UM does not run in Classic).

D. Install the Utilization Management Extensions ✅
The UM package must be installed to enable features like authorizations, review processes, determinations, and appeals.
This is a key part of setup.

Reference:
Salesforce Help: Set Up Utilization Management
Steps include installing the Utilization Management Extensions and assigning Health Cloud + Platform PSLs to users in Lightning.

⚡ Exam Tip:
If you see Classic users in UM questions → wrong (UM is Lightning only).
If you see Care Request Extensions → outdated, correct answer is Utilization Management Extensions.

Explanation:

The Enhanced Timeline component automatically displays events from a predefined set of standard objects (like Task, Event, Case, etc.). However, for it to display events from a custom object (like the one tracking caregiver preferences), the administrator must explicitly configure it to include that custom object.
The process involves two key steps, both of which happen after the component is deployed to the page:
Add the custom object to the Timeline: Within the Timeline's configuration, there is a specific setting to select which objects' records should be displayed as events. The administrator must add the custom object to this list.
Add it to the Timeline component: This step is part of the configuration process where the administrator selects the specific objects, including the new custom object, to be included in the event sources for that instance of the Timeline component.
Therefore, even though the component is on the page, it will not show records from the custom object until this specific configuration is completed post-deployment.

Why the other options are incorrect:
A. Assign the users permissions to be able to view the Timeline before adding it to the Timeline component: While object-level permissions are crucial for users to see the underlying records, this is a prerequisite that should be handled before or during deployment, not after. The question specifically asks what to do post-deployment to make the custom object events visible. The issue is one of configuration, not permissioning in this context.
B. Add the Timeline component to the Patient Lightning page and activate the Timeline: The question states the administrator has already "added an Enhanced Timeline to an existing Patient Lightning page." This step is already complete. Furthermore, you don't "activate" the Timeline; you configure it.
C. Add the Timeline component to the Patient Lightning page and select the Timeline: Similar to option B, this suggests adding the component is a post-deployment step, but the scenario states this has already been done. The key missing step is configuring the component to include the custom object.

Reference: Salesforce Help: Add Objects to the Enhanced Timeline
This documentation details the process of adding standard and custom objects to the Timeline component through its configuration settings, which is a necessary step after the component is placed on the page.

Explanation:

In Salesforce Health Cloud, the Person Account model is the standard and recommended way to represent individual patients and members. A Person Account is a special type of account record that combines the fields of a standard Account and a standard Contact into a single record.

A. Configure Account: While a standard Account is part of the data model, it is typically used to represent organizations, such as hospitals or provider groups, in a B2B (Business-to-Business) context. It is not the ideal way to model an individual patient on its own because it lacks a separate, dedicated Contact record.
B. Leverage Contact-Contact: A Contact-Contact relationship is used to define relationships between individuals, such as a patient and their caregiver or family members. It is not the foundational object for modeling the patient themselves.
C. Configure Contact: A standard Contact is an individual who works for an organization (Account). In a B2B context, this works well. However, in a B2C (Business-to-Consumer) healthcare model where the patient is the primary "customer," a standalone Contact record is insufficient and not the recommended practice in Health Cloud. The Person Account is specifically designed for these B2C scenarios.

By using a Person Account, a consultant can create a unified, 360-degree view of the patient, including their personal demographics, medical history, and related information, all on a single record. This simplifies data management and provides a more intuitive user experience for care coordinators and other healthcare professionals.

Explanation:

To enable care coordinators at a provider organization to track a series of problems, goals, and interventions (PGIs) related to a patient’s care in a repeatable and efficient way within Salesforce Health Cloud, the consultant should recommend defining a PGI Library and care plan templates using the library. Here’s why:
D. Define a PGI Library and care plan templates using the library:
The PGI Library in Health Cloud allows administrators to create a centralized repository of standardized problems, goals, and interventions. By defining these in the PGI Library, care coordinators can efficiently create care plan templates that reference these predefined PGIs. These templates can then be applied to patients, ensuring consistency and repeatability in tracking PGIs across multiple patients. This approach reduces manual effort and ensures standardized care planning, aligning with the requirement for an efficient and repeatable process.

Why the other options are incorrect:
A. Configure an action plan template with tasks for each PGI:
While action plan templates can include tasks, they are primarily used for defining sequences of actions (e.g., scheduling or follow-ups) rather than specifically managing PGIs. This approach is less tailored to the structured tracking of problems, goals, and interventions compared to the PGI Library.
B. Coach the care coordinators to quickly create tasks using a checklist:
This manual approach relies on care coordinators to create tasks individually, which is not repeatable or efficient for managing PGIs across patients. It lacks the standardization and automation provided by the PGI Library and care plan templates.
C. Create care program templates and assign them to patients:
Care program templates in Health Cloud are used to manage broader care programs (e.g., chronic disease management programs) rather than the granular tracking of individual PGIs. They are not the best fit for this specific requirement.

Reference:
Salesforce Health Cloud documentation on the PGI Library and Care Plan Templates (Salesforce Help).
Health Cloud Accredited Professional exam resources, which cover care plan management and the use of the PGI Library for standardized care coordination.