A data architect creates two XDM schemas: Schema A and Schema B. What are the three requirements for defining a schema relationship so that Schema A references Schema B for multi-entity…

Question

Options

• ASchema A must belong to the same schema class as Schema B.
• BSchema A and Schema B must have a relationship defined between them.
• CSchema A and Schema B must each have a primary identity.
• DBoth schemas should have the same fields marked as identities.
• ESchema A and Schema B must each be enabled for Real-Time Customer Profile.

• A
  11% (4)
• B
  84% (32)
• D
  5% (2)

Explanation

Defining a schema relationship for multi-entity segmentation in Adobe Experience Platform requires three things working together: a declared relationship between the schemas (B), a primary identity on each schema so AEP knows how to join them (C), and both schemas enabled for Real-Time Customer Profile so their data participates in segmentation (E). Without any one of these three, the platform either can't find the link, can't resolve the entities, or can't use the data in segment definitions.

Why the distractors are wrong:

• A is wrong because schemas in a relationship do not need to share the same class - in fact, cross-class relationships (e.g., Profile class referencing a custom lookup class) are the whole point of multi-entity segmentation.
• D is wrong because the two schemas do not need identical identity fields - Schema A simply needs a field that references Schema B's primary identity; they can have completely different identity namespaces.

Memory tip: Think "RPP" - Relationship declared, Primary identity on each, Profile-enabled on both. If any "P" is missing, the segment can't see or join the data.

No community discussion yet for this question.