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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce MKT-101 Exam - Topic 3 Question 43 Discussion

Actual exam question for Salesforce's MKT-101 exam
Question #: 43
Topic #: 3
[All MKT-101 Questions]

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)

Show Suggested Answer Hide Answer
Suggested Answer: B

by Chauncey at Apr 19, 2024, 06:53 PM

Limited Time Offer

25%

Off

Get Premium MKT-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Kimbery
5 months ago
Not sure if D is really necessary, seems like overkill.
upvoted 0 times
...
Buddy
5 months ago
Definitely agree with A, it makes total sense!
upvoted 0 times
...
Phillip
5 months ago
Surprised they didn't mention optimizing data structure first!
upvoted 0 times
...
Vannessa
5 months ago
I think B could also help, not just A and D.
upvoted 0 times
...
Johanna
6 months ago
A and D are solid choices for optimizing performance.
upvoted 0 times
...
Lisbeth
6 months ago
I practiced a similar question, and I think option D could be a solid strategy to improve performance by using prefiltered data extensions.
upvoted 0 times
...
Odette
6 months ago
I feel like option C could be relevant too, especially if it helps with decision splits. But I’m not confident about it.
upvoted 0 times
...
Royal
6 months 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?
upvoted 0 times
...
Ashlyn
6 months ago
I think option A makes sense since doing segmentation in Automation Studio could reduce the load on Journey Builder.
upvoted 0 times
...
Mendy
6 months 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.
upvoted 0 times
...
Mollie
6 months 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.
upvoted 0 times
...
Devon
6 months 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.
upvoted 0 times
...
Clorinda
6 months 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.
upvoted 0 times
...
Renato
7 months 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.
upvoted 0 times
...
Tracie
7 months 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.
upvoted 0 times
...
Leonor
7 months 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.
upvoted 0 times
...
Tamera
7 months 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.
upvoted 0 times
...
Tashia
12 months 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.
upvoted 0 times
Talia
11 months 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.
upvoted 0 times
...
Jillian
12 months ago
D) Create a prefiltered, sendable copy of data extensions for each journey instead of using the same entry source.
upvoted 0 times
...
Janine
12 months ago
B) Use Data Extension Entry Sources with Filters applied to perform segmentation activities for Journey Builder.
upvoted 0 times
...
...
Anastacia
12 months 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.
upvoted 0 times
...
Vicki
12 months 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.
upvoted 0 times
...
Elvera
1 year 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.
upvoted 0 times
...
Tran
1 year 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!
upvoted 0 times
...
Nichelle
1 year ago
I believe option D could also be beneficial, creating prefiltered data extensions for each journey.
upvoted 0 times
...
Daniel
1 year ago
I agree with Rikki, segmenting contacts before entering Journey Builder is key.
upvoted 0 times
...
Rikki
1 year ago
I think option A and B could help optimize Journey performance.
upvoted 0 times
...

Save Cancel