Cumulus Financial wants its service reps to view all cases associated with a Unified Individual on a contact record. Which feature should a Data 360 Consultant consider for this use case?
The identity logic is about linking source profiles safely, then choosing the best surviving values for the unified profile. Related List Enrichment is appropriate because identity resolution needs reliable match inputs, qualified identifiers, and controlled reconciliation. It is not just deduplication; it is a rules-driven process that connects source records into a trusted unified profile. The distractors fall short because they either move the problem into the wrong system, add needless duplication, ignore Data 360 object relationships, or rely on a feature built for a different lifecycle stage. In a real implementation, those choices usually create brittle pipelines, stale data, security exposure, or segments that look correct on paper but fail when activated. Thinking like an architect, the selected option places the logic where Data 360 can govern it and reuse it reliably. This is the nuance exam questions often test: the platform capability must match both the technical layer and the business timing requirement, not just sound related to data.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit