MENU
Northern Trail Outfitters wants a data model in Marketing Cloud which will prevent them from duplicating, or even triplicating, records.
How should the unique identifier of the data model be setup if the MobilePush and Email channels are used within the same account?
Suggested Answer: A
Get Premium Salesforce Certified Marketing Cloud Engagement Administrator (MCE-Admn-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
MI
Michel
11 months ago
B sounds like extra work, but might be necessary if C doesn't work.
RA
Raelene
11 months ago
Wait, can we really trust Marketing Cloud to tie records automatically?
LO
Lorita
12 months ago
A could lead to a mess with duplicates, not a fan.
EM
Emelda
12 months ago
Totally agree, C is the way to go!
WH
Whitley
1 year ago
C seems like the best option for avoiding duplicates.
CL
Clarence
1 year ago
I feel like option D might be a compromise, but I'm not sure if it's the best approach. We definitely need to ensure that the keys are managed properly across both channels.
MA
Marsha
1 year ago
I'm a bit confused about whether using a third-party system is necessary. I feel like Marketing Cloud should be able to handle duplicates on its own.
RE
Reyes
1 year ago
I think we practiced a question similar to this, and I recall that controlling the Contact Key values is crucial to avoid duplicates. Option C sounds right to me.
PU
Pura
1 year ago
I remember we discussed the importance of having a consistent identifier for cross-channel marketing, but I'm not sure if it's better to use auto-generated keys or control them ourselves.
DA
Danilo
1 year ago
I'm a bit confused by the difference between options C and D. Can someone clarify the pros and cons of each approach?
LO
Lon
1 year ago
Okay, I think I've got it. We need to strategically control the Contact Key values and use that to link the records across channels. Option C seems like the way to go.
AS
Asha
1 year ago
Hmm, I think the key here is to find a way to tie the records together across channels. Option C looks promising, but I'm not sure if that's the best approach.
SA
Sarah
1 year ago
This seems like a tricky question. I'm not sure if I fully understand the implications of using auto-generated keys versus strategically controlling the Contact Key values.
MA
Malissa
1 year ago
I heard Marketing Cloud has a 'Duplicate-o-matic' feature - you just toss all your contacts in and it spits out a single, coherent record. Easy peasy!
MA
Maryrose
1 year ago
Option E: Use a magic 8-ball to generate unique identifiers. It'll be just as reliable as those other options!
GI
Gilbert
1 year ago
Option E: Use a magic 8-ball to generate unique identifiers. It'll be just as reliable as those other options!
JE
Jess
1 year ago
C) Strategically control the Contact Key values and tie records together across channels using this key.
TA
Tashia
1 year ago
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
LA
Laura
1 year ago
Option B? Really? Relying on a third-party system to manage duplicates? That's just adding unnecessary complexity.
CA
Carin
1 year ago
Option D is intriguing. Controlling the Contact Key in Email but letting Marketing Cloud tie records in MobilePush could be a good compromise.
FR
Francine
1 year ago
I'm leaning towards Option A. Let Marketing Cloud handle the unique identifiers for each channel - sounds like the easiest solution.
PA
Paola
1 year ago
Definitely, it will prevent any duplicate records from being created.
CH
Chu
1 year ago
I agree, it's best to use the auto-generated keys for each channel.
DE
Devora
1 year ago
Yeah, that sounds like the simplest solution. Let the system do the work.
JA
Jamal
1 year ago
I think Option A is the way to go. Let Marketing Cloud handle it.
CA
Carman
1 year ago
Option C seems like the way to go. Controlling the Contact Key values and tying records across channels is the most strategic approach.
NE
Nelida
1 year ago
It's definitely important to have a solid data model in place to avoid issues with duplicate records.
RE
Reyes
1 year ago
I agree, having a consistent Contact Key across channels will help prevent duplication.
NO
Novella
1 year ago
Option C seems like the way to go. Controlling the Contact Key values and tying records across channels is the most strategic approach.
RI
Rikki
2 years ago
I prefer option C, strategically controlling the Contact Key values.
GE
Gearldine
2 years ago
I agree with Marshall, it seems like the most efficient option.
MA
Marshall
2 years ago
I think we should use the auto-generated keys for each channel.