Salesforce Certified Marketing Cloud Engagement Consultant (MCE-Con-201) Exam - Topic 1 Question 109 Discussion

Actual exam question for Salesforce's Salesforce Certified Marketing Cloud Engagement Consultant (MCE-Con-201) exam

Question #: 109
Topic #: 1

[All Salesforce Certified Marketing Cloud Engagement Consultant (MCE-Con-201) Questions]

Northern Trail Outfitters (NTO) is using Einstein Content Selection to populate its emails with personalized product images at send time. Tnese emails typically see high engagement, but because of the frequency of these emails, a customer could see the same image asset several times within a 2-week span.

How should NTO marketers ensure there's a limit to the number of timet a particular image asset can be chosen for a customer?

AAsk the content team to create more images in order to diversify the asset pool.

BSet a Fallback Asset.

CUtilize Einstein Engagement Frequency to send the emails less often.

DSet Fatigue Rules for the product Asset Classes.

Show Suggested Answer

Suggested Answer: A

by Leonora at Jun 11, 2025, 09:13 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Marketing Cloud Engagement Consultant (MCE-Con-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Barrie

2 months ago

C could reduce engagement, not sure that's the way to go.

upvoted 0 times

...

Adell

3 months ago

A would definitely help, but it takes time to create new assets.

upvoted 0 times

...

Eileen

3 months ago

Wait, can you really set fatigue rules? That sounds interesting!

upvoted 0 times

...

Mozell

3 months ago

I think B is a bit too limiting, though.

upvoted 0 times

...

Alease

3 months ago

D seems like the best option to avoid redundancy.

upvoted 0 times

...

Anika

3 months ago

I feel like using Einstein Engagement Frequency could help, but it might not directly address the image repetition issue.

upvoted 0 times

...

Selma

4 months ago

I practiced a similar question where we had to manage content fatigue. I think setting Fatigue Rules for Asset Classes is the best option here.

upvoted 0 times

...

Timmy

4 months ago

I'm not entirely sure, but I think creating more images might not solve the problem if customers still see the same ones too often.

upvoted 0 times

...

Janessa

4 months ago

I remember discussing how setting Fatigue Rules could help limit the frequency of the same image being shown. It seems like a solid approach.

upvoted 0 times

...

Thurman

4 months ago

I'm not totally sure about this one. Creating more images (A) could work, but that seems like a lot of extra work. And using a fallback asset (B) or sending emails less often (C) don't really address the core issue here. I think D is the best option, but I'm not 100% confident.

upvoted 0 times

...

Tarra

4 months ago

Okay, I've got it! The answer is clearly D - Set Fatigue Rules for the product Asset Classes. That will allow us to control the frequency that each image is displayed, which is exactly what the question is asking for.

upvoted 0 times

...

Arthur

5 months ago

Hmm, I'm a bit confused by the wording here. Is the goal to just prevent the same image from being shown multiple times in a 2-week period, or is there a specific limit we need to enforce? I'll have to re-read this carefully.

upvoted 0 times

...

Makeda

5 months ago

This seems like a straightforward question about managing image asset frequency in personalized emails. I think the key is to look for a solution that limits the number of times a specific image can be shown to a customer.

upvoted 0 times

...

Eveline

7 months ago

Haha, I can just imagine the marketing team at NTO being like, 'Let's just make more images! That'll fix it!' Nah, D is the way to go. Gotta use those fatigue rules to keep things fresh for the customers.

upvoted 0 times

Carmelina

5 months ago

D) Set Fatigue Rules for the product Asset Classes.

upvoted 0 times

...

Roslyn

7 months ago

A) Ask the content team to create more images in order to diversify the asset pool.

upvoted 0 times

...

Candida

7 months ago

D is definitely the right choice here. Fatigue rules are built for this exact scenario - preventing customers from seeing the same content over and over. Plus, it's a more elegant solution than just reducing email frequency.

upvoted 0 times

...

Narcisa

8 months ago

I disagree with A. Creating more images just seems like a bandaid solution. Why not just use the tools you have, like Einstein Engagement Frequency, to manage the frequency? B and C are also good options to consider.

upvoted 0 times

Luisa

7 months ago

Setting a Fallback Asset could also help in ensuring customers don't see the same image too often.

upvoted 0 times

...

Malcolm

7 months ago

I think using Einstein Engagement Frequency is a smart way to manage the frequency.

upvoted 0 times

...

Stefania

8 months ago

I believe utilizing Einstein Engagement Frequency could also help in reducing the frequency of emails.

upvoted 0 times

...

Ozell

8 months ago

I agree with Alethea, having a backup image in place is important.

upvoted 0 times

...

Florinda

8 months ago

Option D seems like the way to go. Fatigue rules can help control how often customers see the same image asset. That way, they won't get bored or feel like they're being spammed.

upvoted 0 times

Ahmad

7 months ago

It's important to keep the content fresh and engaging for customers. Fatigue rules can definitely help with that.

upvoted 0 times

...

Narcisa

7 months ago

I agree, setting fatigue rules for the product asset classes is a good way to manage customer engagement and prevent overexposure to the same images.

upvoted 0 times

...

Deane

7 months ago

Option D seems like the way to go. Fatigue rules can help control how often customers see the same image asset. That way, they won't get bored or feel like they're being spammed.

upvoted 0 times

...

Alethea

8 months ago

I think setting a Fallback Asset could be a good solution.

upvoted 0 times

...