In which two ways can a Data Architect ensure PHI/PII data visibility is minimized during the migration of Patient Data from an existing Service Cloud org to a new HC org? (Choose 2)

In which two ways can a Data Architect ensure PHI/PII data visibility is minimized during the migration of Patient Data from an existing Service Cloud org to a new HC org? (Choose 2)
A . Use Salesforce Data Masking when moving data to a Sandbox.
B . Use Data Templates to exclude PHI/PII data from being added to Partial Copy Sandboxes
C . Export Data to a spreadsheet to remove PHI before importing it into a Sandbox
D . Ensure Sandboxes have
E . Platform Shield enabled.

Answer: A, B

Explanation:

According to the Health Cloud Data Model Developer Guide, two ways that a data architect can ensure PHI/PII data visibility is minimized during the migration of patient data from an existing

Service Cloud org to a new Health Cloud org are:

Use Salesforce Data Masking when moving data to a sandbox. Data Masking is a tool that helps you protect sensitive data in sandboxes by masking it with anonymized values.

Use Data Templates to exclude PHI/PII data from being added to partial copy sandboxes. Data Templates are files that specify which objects and fields to include or exclude when creating a partial copy sandbox. Exporting data to a spreadsheet to remove PHI before importing it into a sandbox is not a recommended way, as it can introduce errors and security risks. Ensuring sandboxes have Platform Shield enabled is not a valid way, as Platform Shield is not a feature of sandboxes. Platform Shield is a product that allows encryption of data at rest in production orgs.