Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce CRT-250 Exam - Topic 1 Question 63 Discussion

Posted by Marica on Feb 09, 2025 at 03:15 AM

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: B

Get Premium CRT-250 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
33 comments · newest first
NI
Nida 11 months ago
B sounds risky, relying on a third-party for duplicates isn't ideal.
IN
Inocencia 11 months ago
Wait, can we really trust Marketing Cloud to handle duplicates automatically?
ER
Eric 12 months ago
Not sure about that, using auto-generated keys could work too.
FR
Frankie 12 months ago
I totally agree, controlling Contact Key values is essential!
ST
Stephen 1 year ago
Option C seems like the best way to manage unique identifiers.
LA
Latosha 1 year ago
I vaguely recall something about letting Marketing Cloud handle some of the linking automatically. Option D sounds familiar, but I’m not confident it’s the best approach.
PH
Phil 1 year ago
I practiced a similar question where we had to manage Contact Keys. I think controlling them strategically, like in option C, is crucial for linking records.
RE
Reuben 1 year ago
I'm not entirely sure, but I feel like using auto-generated keys could lead to issues with duplicates. Maybe option A isn't the best?
AL
Allene 1 year ago
I remember we discussed how important it is to have a consistent identifier across channels to avoid duplicates. I think option C might be the right choice.
JO
Johnetta 1 year ago
I'm leaning towards Option C. Strategically controlling the Contact Key values seems like the most robust solution to the problem.
CA
Camellia 1 year ago
Option A seems too simple. I don't think relying on auto-generated keys is a reliable way to prevent duplicates across multiple channels.
LE
Lenna 1 year ago
I'm a bit confused by the difference between options C and D. I'll need to review the details more closely.
AR
Ardella 1 year ago
Option C looks like the best approach to me. Controlling the Contact Key values and tying records across channels is key to preventing duplicates.
LA
Lashawn 1 year ago
This seems like a tricky question. I'll need to think carefully about the implications of each option.
NA
Naomi 1 year ago
Option D makes sense if you want to keep things simple on the Email side, but I'm not sure letting Marketing Cloud handle the tie-ups from MobilePush is the best idea. Gotta keep control of that data, you know?
TH
Theodora 1 year ago
Haha, I bet the marketing team is just hoping to avoid a repeat of that one time they had a hundred copies of the same customer in their database. Talk about a headache!
AN
Andra 1 year ago
↳ replying to Theodora
I know right! That must have been a nightmare to clean up. Hopefully they figure out a good solution this time around.
BR
Britt 1 year ago
↳ replying to Theodora
Yeah, that would definitely save them a lot of trouble in the long run.
LA
Laquita 1 year ago
↳ replying to Theodora
C) Strategically control the Contact Key values and tie records together across channels using this key.
AD
Adolph 1 year ago
↳ replying to Theodora
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
DA
Daniel 1 year ago
↳ replying to Theodora
C) Strategically control the Contact Key values and tie records together across channels using this key.
RI
Richelle 1 year ago
↳ replying to Theodora
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
WA
Walton 2 years ago
I'm not sure I agree with Junita. Using the auto-generated keys from Marketing Cloud (Option A) might be more straightforward and less prone to human error.
AR
Arlean 1 year ago
↳ replying to Walton
I see your point, but I still think Option A is the safer choice to prevent duplicates.
RE
Renea 1 year ago
↳ replying to Walton
But wouldn't it be better to strategically control the Contact Key values across channels (Option C)?
JU
Julio 1 year ago
↳ replying to Walton
I think using the auto-generated keys from Marketing Cloud (Option A) is a good idea.
JU
Junita 2 years ago
Option C seems like the way to go. Controlling the Contact Key values and tying records across channels is the best approach to prevent duplication.
ET
Ettie 1 year ago
↳ replying to Junita
C) Strategically control the Contact Key values and tie records together across channels using this key.
RI
Ricarda 1 year ago
↳ replying to Junita
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
PA
Patrick 2 years ago
↳ replying to Junita
C) Strategically control the Contact Key values and tie records together across channels using this key.
QU
Quentin 2 years ago
I prefer option C, strategically controlling the Contact Key values.
TR
Trinidad 2 years ago
I agree with Hassie, it seems like the most efficient option.
HA
Hassie 2 years ago
I think we should use the auto-generated keys for each channel.
0/2000 characters

Save Cancel