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 8 Question 27 Discussion

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

A Marketing Cloud admin is configuring the Marketing Cloud data model for the first time. Journey Builder with of messages being sent to customers, based on if there has been an order or not. There are two existing data model Orders:

- Customers contains information about subscribers including Email Address, First Name, Last name.

- Orders contains information about the orders and includes the unique identifier of the customer

In which two ways should the admin configure Data Designer to allow this data to be used within a Journey?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Junita
3 months ago
I disagree with B, it complicates things unnecessarily.
upvoted 0 times
...
Elina
3 months ago
A is a must, but C is the way to go for orders.
upvoted 0 times
...
Tamie
4 months ago
Surprised that linking by Email Address (D) is even an option!
upvoted 0 times
...
Katheryn
4 months ago
I think B is a better choice. Many-to-Many seems more flexible.
upvoted 0 times
...
Elouise
4 months ago
Definitely A and C! Makes the most sense.
upvoted 0 times
...
Ernest
4 months ago
I vaguely recall that a One-to-Many relationship is common for Orders to Customers, since one customer can have multiple orders. That might be the right choice here.
upvoted 0 times
...
Jolene
4 months ago
Linking with Email Address seems off to me; I remember it being more about unique identifiers like Customer ID. But I could be wrong.
upvoted 0 times
...
Glendora
5 months ago
I think we practiced a similar question where linking the Orders to Customers using Customer ID was crucial. I feel like that’s definitely one of the answers.
upvoted 0 times
...
Anabel
5 months ago
I remember we discussed the importance of linking data extensions correctly, but I'm not sure if it should be a One-to-Many or Many-to-Many relationship for Orders and Customers.
upvoted 0 times
...
Jodi
5 months ago
I'm a little confused by the options here. I know the business case needs to cover the financial side, but I'm not sure if the list of suppliers or the informal recommendation are relevant. I'll have to review my notes to make sure I'm answering this correctly.
upvoted 0 times
...
Joesph
5 months ago
This looks straightforward enough. I'll just select the range, click Remove Duplicates, and let Excel handle the rest. Shouldn't take too long to knock this one out.
upvoted 0 times
...
Lynelle
5 months ago
Okay, I think I've got this. The -p3 option tells patch to look up to 3 lines of context before or after the declared line in the original file when trying to find a match. That makes sense to me as a way to handle small differences in the files.
upvoted 0 times
...
Edelmira
9 months ago
This is a classic case of 'when in doubt, choose the most specific option'. A One-to-Many relationship is the way to go here. Gotta love these data modeling questions - they really keep you on your toes!
upvoted 0 times
Lelia
8 months ago
Perfect, that should allow us to use the data within a Journey effectively.
upvoted 0 times
...
Marjory
8 months ago
And we should also link the Orders data extension to the Customers data extension using a One-to-Many relationship.
upvoted 0 times
...
Bobbie
8 months ago
That makes sense. It's important to set up the data model correctly for the Journey Builder to work effectively.
upvoted 0 times
...
Sherman
8 months ago
Agreed, that sounds like the most specific option.
upvoted 0 times
...
Rhea
8 months ago
I agree, and we should also link the Orders data extension to the Customers data extension using a One-to-Many relationship.
upvoted 0 times
...
Sylvie
9 months ago
I think we should link the Customers data extension to the data model using Customer ID.
upvoted 0 times
...
Lauran
9 months ago
I think we should link the Customers data extension to the data model using Customer ID.
upvoted 0 times
...
...
Clement
10 months ago
Hmm, I'm a bit confused. Isn't a Many-to-Many relationship usually used when you have a junction table connecting two other tables? I don't think that's the case here. Definitely going with option C!
upvoted 0 times
Macy
8 months ago
Let's go with option C then. It seems like the most logical choice for this scenario.
upvoted 0 times
...
Maryann
9 months ago
Yeah, I agree. That way we can link the Orders data to the Customers data easily.
upvoted 0 times
...
Bettina
9 months ago
I think option C makes sense. It's a one-to-many relationship between Orders and Customers.
upvoted 0 times
...
...
Krystina
10 months ago
I'm between options A and D. Linking the Customers data extension to the data model using either Customer ID or Email Address should work, right? I'm not sure why the other options would be necessary.
upvoted 0 times
Lelia
8 months ago
Yeah, I agree. As long as we link the Customers data extension to the data model, we should be able to use the data in the Journey Builder.
upvoted 0 times
...
Isadora
8 months ago
I think both options A and D would work. They both seem like valid ways to configure the data model.
upvoted 0 times
...
Krystina
8 months ago
D) Link the Customers data extension to the data model using Email Address
upvoted 0 times
...
Lezlie
8 months ago
A) Link the Customers data extension to the data model using Customer ID
upvoted 0 times
...
Myong
9 months ago
Yeah, I agree. It's important to choose the right way to link the data for the Journey Builder.
upvoted 0 times
...
Corinne
9 months ago
I think both options A and D could work. It depends on how the data is structured.
upvoted 0 times
...
Kirk
10 months ago
D) Link the Customers data extension to the data model using Email Address
upvoted 0 times
...
Mica
10 months ago
A) Link the Customers data extension to the data model using Customer ID
upvoted 0 times
...
...
Janine
10 months ago
I think option C is the correct answer here. We need to link the Orders data extension to the Customers data extension using a One-to-Many relationship since a customer can have multiple orders, but each order is associated with only one customer.
upvoted 0 times
...
Lorenza
10 months ago
But what about linking Orders data extension to Customers data extension using a One-to-Many relationship? Wouldn't that also work?
upvoted 0 times
...
Princess
10 months ago
I agree with Janna. It makes sense to use Customer ID for linking the data.
upvoted 0 times
...
Janna
11 months ago
I think the admin should link Customers data extension to the data model using Customer ID.
upvoted 0 times
...
Carli
11 months ago
I think we should also link Orders data extension to Customers data extension using a One-to-Many relationship.
upvoted 0 times
...
Lili
11 months ago
I agree with Luis, that way we can easily identify the unique customers.
upvoted 0 times
...
Luis
11 months ago
I think we should link Customers data extension to the data model using Customer ID.
upvoted 0 times
...

Save Cancel