The correct answer is D , because:
In Salesforce Marketing Cloud's Journey Builder , a Decision Split Activity allows marketers to direct contacts down different paths based on defined attributes.
When comparing data from the entry source (Journey Data) and from additional data extensions (Contact Data or Event Data Extensions like a Transaction DE), you must configure the Decision Split to reference both Contact and Journey Data .
Salesforce documentation explains:
" Journey Data is information captured at the moment of journey entry (i.e., the fields from the entry event data extension).
Contact Data is information related to the contact stored outside the entry event, often in other data extensions linked to the Contact model.
To compare fields across these datasets inside a Decision Split, you must configure the split to use both Contact Data and Journey Data ."
(Source: Salesforce Help - Journey Builder Decision Splits Overview)
Specifically, for NTO:
Journey Data would be the birthday journey source Data Extension.
Contact Data would be the external Transaction DE containing promotional code redemption information.
Key actions required:
Use Decision Split Activity .
Configure the decision split to evaluate both Contact Data and Journey Data .
Compare the Customer Number fields between both datasets to determine if a promotion was redeemed.
Why the other options are incorrect:
❌ A. Decision Split Activity using only Contact Data :
❌ B. Decision Split Activity using only Journey Data :
❌ C. Einstein Split Activity :
Einstein Split uses AI to predict engagement (like open or click probability), not field comparison across datasets.
Additional official extract for clarity:
"When building decision splits that rely on both entry data and external profile attributes, ensure to select the appropriate source (Contact Data and Journey Data) to create accurate comparisons."
(Source: Salesforce Marketing Cloud Journey Builder User Guide)
Thus, the correct answer is D .
