Question 1
Choose 1
Northern Trail Outfitters has ingested customer profile data and related email engagement data from two separate marketing systems. Both systems use the same customer identifier. Which feature should a Data 360 Consultant implement to ensure that engagement records are accurately associated with the correct source profile and avoid misinterpretation of the related engagement data?
Correct answer:
D. Fully Qualified Keys
Explanation:
When data from multiple sources shares the same customer identifier, Data 360 can misinterpret related records because it cannot distinguish which source system a record originated from. Fully Qualified Keys (FQKs) solve this by combining the source key with a key qualifier (such as the source system name), creating a unique identifier that preserves source lineage. This ensures engagement records are correctly associated with the profile from the same source system, preventing data misattribution during harmonization and queries.
Correct Option:
D. Fully Qualified Keys.
FQKs append a source-specific qualifier to primary and foreign key fields in Data Lake Objects (DLOs), creating a composite unique identifier. When multiple DLOs map to the same DMO field (e.g., Individual ID), FQKs allow Data 360 to distinguish records by their source origin. This prevents the platform from incorrectly assuming that identical raw ID values from different systems represent the same entity, thereby ensuring engagement records join to the correct source profile.
Incorrect Option:
A. Profile Unification Rules.
This is a general term for the identity resolution process that matches and merges records into unified profiles. It does not address the specific problem of distinguishing source-specific records during key mapping and joins.
B. Identity Resolution Reconciliation Rules.
These rules determine which attribute values (e.g., most frequent, most recent) appear on the unified profile after matching. They do not manage key uniqueness or prevent source-based key collisions.
C. Identity Resolution Match Rules.
Match rules define which fields are compared to identify records belonging to the same person. While essential for profile unification, they operate at a different stage and do not resolve the fundamental issue of identical raw IDs from different sources being mapped to the same DMO field.
Reference:
Salesforce Help: Best Practices for Fully Qualified Keys; Trailhead: Learn About Fully Qualified Keys.
When data from multiple sources shares the same customer identifier, Data 360 can misinterpret related records because it cannot distinguish which source system a record originated from. Fully Qualified Keys (FQKs) solve this by combining the source key with a key qualifier (such as the source system name), creating a unique identifier that preserves source lineage. This ensures engagement records are correctly associated with the profile from the same source system, preventing data misattribution during harmonization and queries.
Correct Option:
D. Fully Qualified Keys.
FQKs append a source-specific qualifier to primary and foreign key fields in Data Lake Objects (DLOs), creating a composite unique identifier. When multiple DLOs map to the same DMO field (e.g., Individual ID), FQKs allow Data 360 to distinguish records by their source origin. This prevents the platform from incorrectly assuming that identical raw ID values from different systems represent the same entity, thereby ensuring engagement records join to the correct source profile.
Incorrect Option:
A. Profile Unification Rules.
This is a general term for the identity resolution process that matches and merges records into unified profiles. It does not address the specific problem of distinguishing source-specific records during key mapping and joins.
B. Identity Resolution Reconciliation Rules.
These rules determine which attribute values (e.g., most frequent, most recent) appear on the unified profile after matching. They do not manage key uniqueness or prevent source-based key collisions.
C. Identity Resolution Match Rules.
Match rules define which fields are compared to identify records belonging to the same person. While essential for profile unification, they operate at a different stage and do not resolve the fundamental issue of identical raw IDs from different sources being mapped to the same DMO field.
Reference:
Salesforce Help: Best Practices for Fully Qualified Keys; Trailhead: Learn About Fully Qualified Keys.