MENU
Northern Trail Outfitters (NTO) is creating a birthday journey and one of the requirements is to divert anyone who has redeemed the promotional code before reminder emails are sent on the 15th and 20th of each month. Their transactional information, which includes redeemed promo codes, Is housed in a separate data extension than the one used for Journey injection. NTO needs to use an attribute to attribute comparison on the customer number field in the Journey source and transaction data extensions.
Which activity would they use to accomplish this?
Suggested Answer: B
Get Premium MKT-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
JO
Jose
11 months ago
Sounds right, but I’m surprised they didn’t mention data blending!
DI
Diane
11 months ago
I’m pretty sure option A wouldn’t work here.
CU
Curtis
12 months ago
Wait, can they really compare those attributes like that?
EL
Ellen
12 months ago
Definitely agree, option D makes the most sense!
LO
Lorrine
1 year ago
I think they need option D for sure.
ST
Stephanie
1 year ago
I recall that Decision Splits are essential for this kind of logic, but I can't remember if Einstein Split would be necessary for a simple promo code check.
LA
Lavonna
1 year ago
I’m a bit confused about whether to use only Journey Data or include Contact Data too. I need to double-check the requirements for attribute comparisons.
PA
Paris
1 year ago
I think we practiced a similar question where we had to compare data from different extensions. I feel like using both Contact and Journey Data might be the right approach here.
RI
Rickie
1 year ago
I remember we discussed how Decision Splits can be used to segment audiences based on attributes, but I'm not sure if we need both data sources for this one.
AN
Annmarie
1 year ago
This looks straightforward to me. The requirement to divert anyone who has redeemed the promo code means we need to use the attribute to attribute comparison, so the Decision Split Activity using both Contact and Journey Data is the answer.
VI
Viola
1 year ago
I'm a bit confused on the difference between the Decision Split and Einstein Split activities. I'll need to double-check the capabilities of each to make sure I select the right one.
CA
Carri
1 year ago
Okay, let me think this through. We need to compare the customer number field between the two data extensions, so I'm guessing the Decision Split Activity using both Contact and Journey Data is the way to go.
BL
Blossom
1 year ago
This seems like a tricky one. I'll need to carefully review the details about the data extensions and the requirement to divert anyone who has redeemed the promo code.
LA
Lawana
1 year ago
I'm stumped on this one. Maybe the answer is to just send everyone a birthday cake and call it a day?
DO
Douglass
1 year ago
Sending a birthday cake to everyone might be a nice gesture, but using a Query activity is a more efficient way to achieve their goal.
AN
Anglea
1 year ago
Exactly. By using the Query activity, they can ensure that only those who haven't redeemed the promo code receive the reminder emails.
CL
Clement
1 year ago
That makes sense. They can then use the results of the Query to filter out those who have redeemed the promo code.
HE
Hester
1 year ago
They would use a Query activity to compare the customer number field in both data extensions.
FR
Freeman
1 year ago
Haha, I bet the promo code redemption is like a game of hide-and-seek. Gotta use all the data to find those sneaky redeemers!
KA
Kayleigh
1 year ago
Yikes, this one's tricky. I'm going to go with C. The Einstein Split Activity sounds like it could handle this kind of attribute comparison.
LA
Lavonne
1 year ago
I agree, the Einstein Split Activity seems like the best choice for this task.
CL
Clare
1 year ago
I'm not sure, maybe they could use the Decision Split Activity instead?
VI
Viola
1 year ago
I think you're right, the Einstein Split Activity does sound like it could handle this.
GA
Galen
2 years ago
I'm leaning towards B. Seems like we only need to look at the Journey Data since that's where the redeemed promo codes are stored.
SA
Santos
1 year ago
C. Update Contact Activity
MA
Maile
1 year ago
B. Data Extract Activity
VI
Virgie
1 year ago
A. Query Activity
TA
Tammara
2 years ago
I'm not sure, but I think Einstein Split Activity could also be a good choice for this task.
KA
Katina
2 years ago
Hmm, I think the answer is D. Using both Contact and Journey Data makes the most sense to check if the promo code has been redeemed before.
KI
Kimberlie
1 year ago
Yes, that way they can accurately divert anyone who has already redeemed the promotional code.
AR
Arlyne
2 years ago
I agree, using both Contact and Journey Data would be the best way to ensure the promo code has not been redeemed before.
MA
Marica
2 years ago
I agree with Freeman, using both Contact and Journey Data would be the best option for this scenario.
FR
Freeman
2 years ago
I think they should use Decision Split Activity using both Contact and Journey Data.