A data architect is building an XDM Experience Event Schema for loading event data from the Adobe Experience Platform (AEP) Web SDK. The data is intended to be used in the Real-Time customer profile…

Question

Options

• ANo, a field on the schema will automatically be marked.
• BYes, the architect will select a field from the schema and mark it as primary.
• CNo, the primary identity will already be in the identity map.
• DYes, the architect will select the identity map and mark it as primary.

• A
  16% (7)
• B
  9% (4)
• C
  73% (32)
• D
  2% (1)

Explanation

When using the AEP Web SDK with XDM Experience Event schemas, the identity map (identityMap) is automatically included in the schema and populated by the Web SDK itself. It stores both ambiguous identities (e.g., ECID for anonymous visitors) and authenticated identities simultaneously - meaning the primary identity already exists within the identity map without any manual configuration by the architect.

Why the distractors are wrong:

• A is wrong because no individual schema field is silently auto-marked as primary - it is specifically the identity map that handles this, not a generic automatic field selection.
• B is wrong because the architect does NOT need to manually pick a field and designate it as primary; that workflow applies to XDM Individual Profile schemas, not Experience Events used with the Web SDK.
• D is wrong because you don't "mark the identity map as primary" - the identity map inherently contains the primary identity; it is not itself flagged as a primary field in the schema editor.

Memory tip: Think of it this way - Web SDK = Identity Map already packed. The SDK ships identities into the map automatically (ECID for ambiguous, authenticated ID when available), so there is nothing left for the architect to manually designate.

No community discussion yet for this question.