MENU
Northern Trails Outfitters has a contact count of nearly 10 million records. They have noticed slower processing times when sending using Journey Builder.
Which two actions could they take to optimize Journey performance? (Choose 2 answers)
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
28 comments · newest first
KI
Kimbery
11 months ago
Not sure if D is really necessary, seems like overkill.
BU
Buddy
11 months ago
Definitely agree with A, it makes total sense!
PH
Phillip
12 months ago
Surprised they didn't mention optimizing data structure first!
VA
Vannessa
12 months ago
I think B could also help, not just A and D.
JO
Johanna
1 year ago
A and D are solid choices for optimizing performance.
LI
Lisbeth
1 year ago
I practiced a similar question, and I think option D could be a solid strategy to improve performance by using prefiltered data extensions.
OD
Odette
1 year ago
I feel like option C could be relevant too, especially if it helps with decision splits. But I’m not confident about it.
RO
Royal
1 year ago
I'm not entirely sure, but I remember something about using filters with Data Extensions in Journey Builder. Maybe option B is a good choice?
AS
Ashlyn
1 year ago
I think option A makes sense since doing segmentation in Automation Studio could reduce the load on Journey Builder.
ME
Mendy
1 year ago
Creating a prefiltered, sendable copy of data extensions for each journey instead of using the same entry source might be the way to go. That could help reduce the load on Journey Builder.
MO
Mollie
1 year ago
Using Data Extension Entry Sources with Filters applied to perform segmentation activities for Journey Builder seems like a good option. That could help streamline the process and improve performance.
DE
Devon
1 year ago
Okay, let's see. Performing large-scale segmentation in Automation Studio before admitting contacts into Journey Builder could help, but I'm not sure if that's the best approach here.
CL
Clorinda
1 year ago
Hmm, this looks like a tricky one. I'm going to need to think through the options carefully to make sure I choose the right actions to optimize Journey performance.
RE
Renato
1 year ago
Including data for decision splits in Attribute Groups in Contact Builder and using contact data rather than journey data could be an interesting approach. I'll need to look into that a bit more.
TR
Tracie
1 year ago
Hmm, I'm a bit unsure about this one. I know GDPR has specific requirements for data breaches, but I can't remember the exact steps. I'll have to think this through carefully.
LE
Leonor
1 year ago
Hmm, I'm a bit confused about the difference between a multicast address and a broadcast address. I'll need to think this through carefully before answering.
TA
Tamera
1 year ago
I'm not entirely sure, but didn't we say that muscular fatigue alone shouldn't automatically halt the test? That might be too cautious.
TA
Tashia
2 years ago
Haha, 10 million records? That's a lot of contacts to wrangle! I'd say B and D are the way to go - don't make Journey Builder do all the heavy lifting when you can offload it elsewhere.
TA
Talia
1 year ago
Haha, 10 million records? That's a lot of contacts to wrangle! I'd say B and D are the way to go - don't make Journey Builder do all the heavy lifting when you can offload it elsewhere.
JI
Jillian
2 years ago
D) Create a prefiltered, sendable copy of data extensions for each journey instead of using the same entry source.
JA
Janine
2 years ago
B) Use Data Extension Entry Sources with Filters applied to perform segmentation activities for Journey Builder.
AN
Anastacia
2 years ago
B and D are the obvious choices here. Anything to avoid clogging up Journey Builder with massive amounts of data. *whistles* I've seen some journeys get sluggish, let me tell you.
VI
Vicki
2 years ago
I'd go with B and D. Using Data Extension Entry Sources with Filters is a smart way to handle segmentation, and having a prefiltered copy of the data is just common sense.
EL
Elvera
2 years ago
A and D for sure. Doing the heavy lifting in Automation Studio and creating a dedicated data extension for each journey - that's the key to optimizing performance.
TR
Tran
2 years ago
Hmm, I think B and D are the way to go. Segmentation upfront in Automation Studio and using a prefiltered sendable copy to keep the journey efficient. Less data crunching in Journey Builder, the better!
NI
Nichelle
2 years ago
I believe option D could also be beneficial, creating prefiltered data extensions for each journey.
DA
Daniel
2 years ago
I agree with Rikki, segmenting contacts before entering Journey Builder is key.
RI
Rikki
2 years ago
I think option A and B could help optimize Journey performance.