A data architect is configuring an XDM data model to onboard customer data to the Real-Time Customer Profile. Which three items should the data architect keep in mind when defining identities for the

Question

Options

• AA schema must use an identity Map for ingesting identities.
• BA schema must have one primary identity and one other person identity.
• CA schema's identity field(s) should have values unique to a single customer profile.
• DField(s) intended to be used for identity service must be of type string.
• EA schema must have a single primary identity in order for the schema to be enabled for use in the

• A
  12% (5)
• B
  7% (3)
• C
  80% (33)

Explanation

When configuring identities for Real-Time Customer Profile in AEP, three rules are non-negotiable: identity values must uniquely identify a single person (C) - using non-unique values like a shared household email would incorrectly merge profiles; all identity fields must be of type string (D), even if the value looks numeric (e.g., a loyalty number stored as "12345"); and a schema must have exactly one primary identity (E) designated before it can be enabled for Real-Time Customer Profile at all.

A is wrong because an Identity Map is one way to carry identities but is not required - identity fields can be marked directly on standard schema fields without using an Identity Map.

B is wrong because a schema requires only a single primary identity; there is no rule mandating a second "person identity." You can have multiple secondary identities or none beyond the primary.

Memory tip - "SUP": identities must be a String type, Unique per customer, and the schema needs a Primary identity. If all three SUP conditions are met, the schema is profile-ready.

No community discussion yet for this question.