A marketer is loading both first and last name from two sources (Loyalty and CRM). At activation time, the marketer would like to use the first name from their Loyalty schema and a last name from…

Question

Options

• AYes, by configuring a merge policy to use dataset precedence setting Loyalty first and CRM
• BNo, this cannot be done because merge policies cannot merge record-based datasets together
• CNo, this cannot be done because merge policies cannot pick and choose fields from various
• DYes, by configuring a merge policy to use field precedence setting first name from Loyalty and last

• A
  2% (1)
• B
  10% (4)
• C
  80% (33)
• D
  7% (3)

Explanation

Option C is correct because Adobe Experience Platform merge policies operate at the dataset level - they determine which dataset "wins" overall, not which individual fields to pull from specific sources. There is no native mechanism in AEP merge policies to selectively map a single field (e.g., first name) from one dataset and a different field (e.g., last name) from another.

Why the distractors are wrong:

• A is wrong because dataset precedence sets Loyalty first, which means Loyalty's values win for all conflicting fields - not just first name. You can't use this to selectively grab last name from CRM.
• B is wrong because the premise is false - merge policies absolutely can merge record-based datasets; that's their core purpose.
• D is wrong because AEP merge policies do not have a "field precedence" configuration that lets you manually assign individual fields to specific source datasets. This feature does not exist.

Memory tip: Think of merge policies as picking a winning team, not individual players. You can rank which dataset wins overall (dataset precedence) or let recency decide (timestamp order), but you can never hand-select field-by-field from different sources.

No community discussion yet for this question.