To handle duplicate data for customers who are both loan applicants and high net worth individuals, the consultant should ingest the data into two separate Data Lake Objects (DLOs) and map them to the Individual and Contact Point Email Data Model Objects (DMOs). Here’s why and how this works:
Understanding the Problem :
Customers may exist in both datasets (loan applicants and high net worth individuals), leading to potential duplication.
To avoid redundancy while maintaining data integrity, the data must be ingested and mapped carefully.
Why Two DLOs?
By ingesting the data into two DLOs, you can maintain separation between the two datasets while still leveraging shared attributes (e.g., email addresses).
Mapping both DLOs to the Individual and Contact Point Email DMOs ensures that identity resolution can consolidate duplicate records based on shared identifiers like email.
Steps to Implement This Solution :
Step 1: Create two DLOs—one for loan applicants and another for high net worth customers.
Step 2: Map both DLOs to the Individual DMO to consolidate customer profiles.
Step 3: Map the email fields from both DLOs to the Contact Point Email DMO to enable identity resolution based on email addresses.
Step 4: Configure identity resolution rules to merge duplicate records based on shared attributes like email.
Why Not Other Options?
A. Use a data transform to consolidate the data into one DLO: Consolidating into a single DLO before mapping would lose the distinction between the two datasets and make it harder to manage updates or changes.
C. Ingest the data into two DLOs and then map to two custom DMOs: Creating custom DMOs is unnecessary complexity when the standard Individual and Contact Point Email DMOs can handle this scenario.
D. Ingest the data into one DLO and then map to one custom DMO: Using a single DLO would result in data loss or confusion, as the distinction between loan applicants and high net worth customers would be lost.
By using two DLOs and mapping them to the standard DMOs, the consultant ensures clean data ingestion and effective identity resolution.
