A consultant notices that two profiles have collapsed due to shared identities. What is the best way for the consultant to determine the specific dataset or batch responsible for the collapsed…

Question

Options

• ABrowse the datasets enabled for profile using query service until they find the batch that caused
• BUse the identity graph viewer using the shared identity namespace and value, and locate the
• CLook up the profile using the shared identity namespace and value, and identify the dataset and
• DManually inspect individual profiles for shared identity links

• A
  9% (3)
• B
  86% (30)
• C
  3% (1)
• D
  3% (1)

Explanation

Option B is correct because the Identity Graph Viewer in Adobe Experience Platform is purpose-built for tracing identity linkages. By entering the shared identity namespace and value, a consultant can visually inspect the full identity graph and directly identify which dataset and batch introduced the link that caused the profile collapse - it exposes the exact provenance of each identity edge.

Why the distractors fail:

• A - Browsing datasets via Query Service is exploratory and unstructured; it has no native mechanism to surface which batch caused a specific identity merge, making it tedious and unreliable.
• C - Looking up the profile shows unified profile data but does not expose the identity graph layer where dataset/batch lineage for each identity link is visible; profile view and graph view are distinct tools.
• D - Manual inspection of individual profiles is both inefficient and blind to the underlying graph structure - you can see that identities are shared, but not where the link originated.

Memory tip: When profiles collapse, think graph - the Identity Graph Viewer is the only tool that shows the edges (links) between identities along with their originating dataset and batch, making it the forensic starting point for any collapse investigation.

No community discussion yet for this question.