A data engineer has configured a new dataset for Adobe Experience Platform which is enabled for Profile. The new source uses an individual profile-based schema with its primary identity as Email…

Question

Options

• A75 profile fragments ingested successfully and 25 profile fragments failed to ingest
• BThe identity graph collapsed 25 of the profile fragments into the existing 75 profile fragments
• C25 of the profile fragments had repeated Primary Identity values
• DThe dataset schema used was not compatible with the ingestion workflow

• B
  15% (3)
• C
  80% (16)
• D
  5% (1)

Explanation

Option C is correct because in Adobe Experience Platform, the primary identity field (Email in this case) acts as the unique key for profile fragment creation - if 25 incoming records carried email addresses that duplicated other records in the same batch, AEP deduplicates them rather than creating redundant fragments, yielding only 75 distinct entries instead of 100.

Why the distractors are wrong:

• A is ruled out by the question itself, which explicitly states no errors occurred - failed ingestion always surfaces errors.
• B confuses identity graph linking (stitching profiles across different namespaces) with simple deduplication; identity graph collapse merges different identities into one node, which is a separate mechanism and doesn't explain the fragment count drop described here.
• D is eliminated for the same reason as A - an incompatible schema would produce ingestion errors, not silent record loss.

Memory tip: Think of the primary identity as a database primary key - inserting two rows with the same key doesn't create two rows, it just updates one. Duplicate emails in = fewer unique fragments out, zero errors generated.

No community discussion yet for this question.