New Year Sale 2026! 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

Actual exam question for Salesforce's CRT-250 exam
Question #: 63
Topic #: 1
[All CRT-250 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Nida
3 months ago
B sounds risky, relying on a third-party for duplicates isn't ideal.
upvoted 0 times
...
Inocencia
3 months ago
Wait, can we really trust Marketing Cloud to handle duplicates automatically?
upvoted 0 times
...
Eric
3 months ago
Not sure about that, using auto-generated keys could work too.
upvoted 0 times
...
Frankie
4 months ago
I totally agree, controlling Contact Key values is essential!
upvoted 0 times
...
Stephen
4 months ago
Option C seems like the best way to manage unique identifiers.
upvoted 0 times
...
Latosha
4 months 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.
upvoted 0 times
...
Phil
4 months 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.
upvoted 0 times
...
Reuben
4 months 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?
upvoted 0 times
...
Allene
5 months 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.
upvoted 0 times
...
Johnetta
5 months ago
I'm leaning towards Option C. Strategically controlling the Contact Key values seems like the most robust solution to the problem.
upvoted 0 times
...
Camellia
5 months 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.
upvoted 0 times
...
Lenna
5 months ago
I'm a bit confused by the difference between options C and D. I'll need to review the details more closely.
upvoted 0 times
...
Ardella
5 months 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.
upvoted 0 times
...
Lashawn
5 months ago
This seems like a tricky question. I'll need to think carefully about the implications of each option.
upvoted 0 times
...
Naomi
10 months 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?
upvoted 0 times
...
Theodora
10 months 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!
upvoted 0 times
Andra
9 months ago
I know right! That must have been a nightmare to clean up. Hopefully they figure out a good solution this time around.
upvoted 0 times
...
Britt
9 months ago
Yeah, that would definitely save them a lot of trouble in the long run.
upvoted 0 times
...
Laquita
9 months ago
C) Strategically control the Contact Key values and tie records together across channels using this key.
upvoted 0 times
...
Adolph
9 months ago
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
upvoted 0 times
...
Daniel
9 months ago
C) Strategically control the Contact Key values and tie records together across channels using this key.
upvoted 0 times
...
Richelle
9 months ago
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
upvoted 0 times
...
...
Walton
10 months 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.
upvoted 0 times
Arlean
9 months ago
I see your point, but I still think Option A is the safer choice to prevent duplicates.
upvoted 0 times
...
Renea
9 months ago
But wouldn't it be better to strategically control the Contact Key values across channels (Option C)?
upvoted 0 times
...
Julio
9 months ago
I think using the auto-generated keys from Marketing Cloud (Option A) is a good idea.
upvoted 0 times
...
...
Junita
10 months 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.
upvoted 0 times
Ettie
8 months ago
C) Strategically control the Contact Key values and tie records together across channels using this key.
upvoted 0 times
...
Ricarda
9 months ago
A) Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
upvoted 0 times
...
Patrick
10 months ago
C) Strategically control the Contact Key values and tie records together across channels using this key.
upvoted 0 times
...
...
Quentin
11 months ago
I prefer option C, strategically controlling the Contact Key values.
upvoted 0 times
...
Trinidad
11 months ago
I agree with Hassie, it seems like the most efficient option.
upvoted 0 times
...
Hassie
11 months ago
I think we should use the auto-generated keys for each channel.
upvoted 0 times
...

Save Cancel