Explanation:

A. Fields
Field-level security (FLS) controls access to individual fields, but the question specifically references Leads, Contacts, and Person Accounts as whole entities → so it’s not just fields.

B. Records
Record-level security (sharing rules, role hierarchy) determines which records a user can see.
But the exam wording “enable data protection details for leads, contacts, person accounts” points to enabling them at the object level, not just record-by-record.

C. Tasks
Not relevant here. Tasks aren’t about data protection/privacy enforcement.

D. Objects ✅
In Health Cloud, when configuring Data Protection and Privacy, admins explicitly enable it for objects (e.g., Lead, Contact, Person Account).
This ensures the system tracks data use, consent, and privacy preferences for those entities.
Exactly matches the requirement.

Reference:
Salesforce Help: Enable Data Protection and Privacy for Health Cloud
“To maintain privacy, enable data protection details for objects such as Leads, Contacts, and Person Accounts during Health Cloud configuration.”

⚡ Exam Tip:
If the question mentions enable data protection details for Lead/Contact/Person Account → always answer Objects.
If it mentions masking or restricting specific fields → answer Fields.

Explanation:

Einstein Analytics Predictions, also known as Einstein Prediction Builder, is the Salesforce feature that allows administrators to build custom predictive models using their own data without a data scientist. 🧠
In the context of Health Cloud, this capability can be leveraged to:

Analyze historical patient data (e.g., demographics, appointment history, communication logs).
Identify patterns and factors that correlate with appointment attendance.
Generate a prediction score that highlights the likelihood of a patient attending a future appointment.

This prediction score can then be displayed directly on the appointment scheduling screen or patient record, allowing care coordinators to proactively reach out to patients who are at high risk of a no-show and offer them a more suitable time, or to highlight the best times to book.

Explanation:

Before installing the Health Cloud Claims unmanaged package, the Health Cloud managed package must already be installed and configured in the Salesforce org. The Claims package depends on foundational components provided by the managed package, including object definitions, permission structures, and platform services.
If the admin attempts to install the Claims package without the managed package in place, the installation will fail due to missing dependencies.

🛑 Why the other options are incorrect:
B. Health Cloud permission set license is missing: While PSLs are required for user access, they don’t block package installation.
C. Administrator is not registered in AppExchange: Registration isn’t a prerequisite for installing unmanaged packages via direct URL.
D. Administrator doesn’t have Health Cloud license: The admin’s license affects access, not installation capability.

📚 Reference:
Salesforce Help: Install the Claims Data Model
Salesforce Developer Docs: Health Cloud Package Installation

Explanation:

Health Cloud uses Custom Labels to manage user-facing text, such as the "Patient Card" header. This allows administrators to customize terminology without modifying code or configuration. The correct process is:
Navigate to Setup → Custom Labels.
Search for the relevant label (e.g., Patient_Card_Header).
Use the Local Overrides feature to create a language-specific translation, effectively renaming the label to "Member Card" for all users.

Why the Other Options Are Incorrect:
B. There is no "Patient Card Configuration" tab in Health Cloud Admin Home. Patient Card settings are managed via Custom Labels or component attributes, not a dedicated configuration page.
C. The "Patient Card" is not a standalone object; it is a Lightning Component whose label is controlled via Custom Labels, not object/field names.
D. While component attributes can be edited in Experience Builder or Lightning App Builder, the header label of the Patient Card is typically controlled by a Custom Label, not component attributes.
E. Health Cloud labels can be changed using Salesforce’s localization tools (e.g., Custom Labels, Translation Workbench). This is a standard customization feature.

Reference:
Salesforce Help:
Custom Labels for Health Cloud
Override Custom Labels with Local Translations
This aligns with the "Customization and Configuration" domain of the Health Cloud Accredited Professional (AP-211) exam.

Explanation:

To enable care managers at Bloomington Caregivers to call patients post-discharge, ask a series of questions, enter the responses into Salesforce Health Cloud, and automatically assign a personalized care plan based on those answers, the consultant should leverage the following two capabilities together:

A. Discovery Framework:
The Discovery Framework in Health Cloud allows for the creation of dynamic assessments and questionnaires that care managers can use to collect patient responses during post-discharge calls. It supports logic-based rules to analyze responses and trigger actions, such as assigning a personalized care plan based on the patient’s answers.
D. Salesforce Surveys:
This capability enables the design and delivery of surveys that care managers can use to record patient responses. When integrated with the Discovery Framework, survey responses can be processed to automatically generate or assign a personalized care plan in Health Cloud, streamlining the workflow and ensuring data-driven care plan assignments.

Why the other options are incorrect:
B. Integrated Care Management: While this feature supports care coordination and team-based care plan management, it does not directly handle the collection of patient responses or the automation of care plan assignments based on survey answers.
C. Care Programs: Care Programs in Health Cloud are used to manage broader treatment programs (e.g., for chronic conditions), but they are not specifically designed for collecting patient responses or dynamically assigning personalized care plans based on those responses.

How they work together:
The Discovery Framework provides the logic and rules to analyze patient responses and trigger care plan assignments, while Salesforce Surveys offers a user-friendly interface for care managers to input patient answers during calls. Together, they enable the automated, response-driven assignment of personalized care plans.

Reference:
Salesforce Health Cloud documentation on Discovery Framework and Salesforce Surveys integration (Salesforce Help).
Health Cloud Accredited Professional exam resources, which cover assessment tools and care plan automation.