A retail company needs to integrate data from its CRM and e-commerce platform to build a unified customer profile. The CRM uses email as the primary identifier, while the e-commerce platform uses phon

Question

Options

• AUse a single namespace and ignore secondary identifiers.
• BCreate separate schemas for each data source without linking identities.
• CConfigure identity namespaces for email and phone and link them in the Identity Graph.
• DEnable only deterministic identity resolution with phone numbers as the primary field.

• A
  7% (2)
• B
  3% (1)
• C
  76% (22)
• D
  14% (4)

Explanation

C is correct because Adobe Real-Time CDP uses the Identity Graph to stitch together records from different systems by mapping each identifier type to its own namespace (e.g., Email, Phone). Linking email and phone namespaces allows the platform to recognize that a CRM record and an e-commerce record belong to the same real-world customer, forming a unified profile.

Why the distractors fail:

• A - Using a single namespace discards the semantic meaning of different identifiers and prevents accurate cross-system matching.
• B - Keeping schemas separate with no identity linkage defeats the entire purpose of RT-CDP; profiles remain siloed and never unify.
• D - Restricting resolution to only deterministic phone-number matching ignores the CRM's email-based records entirely, leaving half the data unlinked.

Memory tip: Think of identity namespaces as "passport types" (email passport, phone passport) and the Identity Graph as the border agent who checks all your passports and confirms you're one person - C is the only answer that lets the agent do its job.

No community discussion yet for this question.