How should the fields be mapped to support identity resolution?

A customer has a Master Customer table from their CRM to ingest into Data Cloud. The table contains a name and primary email address, along with other personally Identifiable information (Pll).

How should the fields be mapped to support identity resolution?
A . Create a new custom object with fields that directly match the incoming table.
B . Map all fields to the Customer object.
C . Map name to the Individual object and email address to the Contact Phone Email object.
D . Map all fields to the Individual object, adding a custom field for the email address.

Answer: C

Explanation:

To support identity resolution in Data Cloud, the fields from the Master Customer table should be mapped to the standard data model objects that are designed for this purpose. The Individual object is used to store the name and other personally identifiable information (PII) of a customer, while the Contact Phone Email object is used to store the primary email address and other contact information of a customer. These objects are linked by a relationship field that indicates the contact information belongs to the individual. By mapping the fields to these objects, Data Cloud can use the identity resolution rules to match and reconcile the profiles from different sources based on the name and email address fields. The other options are not recommended because they either create a new custom object that is not part of the standard data model, or map all fields to the Customer object that is not intended for identity resolution, or map all fields to the Individual object that does not have a standard email address field.

Reference: Data Modeling Requirements for Identity Resolution, Create Unified Individual Profiles