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

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

Question #: 106
Topic #: 2

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

Northern Trail Outfitters is migrating from a legacy emailing tool to Marketing Cloud. As part of the migration, they have to go through a security review. Their data privacy team has made it clear that the data in the sandbox should never be mixed with data In production during testing cycles.

What recommendation would a consultant provide on the architecture to fulfill this requirement?

AImplement two separate Marketing Cloud instances.

BEnsure test sends are done from data extensions with attribute 'Is Testing1.

CCreate one or more additional business units for testing.

DUse Subscriber Filter per business unit to filter production from test data.

Show Suggested Answer

Suggested Answer: D

To send SMS and push notifications together with emails as part of a new customer onboarding journey, Northern Trail Outfitters should use a GUID or another generated ID for Contact Key. A Contact Key is a unique identifier for each contact in Marketing Cloud across different channels and platforms. A GUID or another generated ID is recommended as a Contact Key because it is persistent, consistent, and channel-agnostic. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm&type=5

by Colby at Mar 19, 2025, 02:38 PM

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

Josephine

2 months ago

B is a good idea, but it might not cover all scenarios.

upvoted 0 times

...

Rikki

3 months ago

I think C could work too, but not as foolproof as A.

upvoted 0 times

...

Dan

3 months ago

Wait, is it really necessary to have two instances? That sounds expensive!

upvoted 0 times

...

Evangelina

3 months ago

D sounds risky, I wouldn't trust filters to keep things separate.

upvoted 0 times

...

Gertude

3 months ago

A seems like the safest option for data separation.

upvoted 0 times

...

Vanesa

3 months ago

I feel like option B might not fully address the security review requirements. Just tagging data extensions as 'Is Testing' seems too simple.

upvoted 0 times

...

Arthur

4 months ago

I’m a bit confused about the Subscriber Filter option. Does it really prevent mixing data, or is it just a way to manage visibility?

upvoted 0 times

...

Louisa

4 months ago

I think option C sounds familiar from our practice questions. Creating additional business units could help with data segregation, right?

upvoted 0 times

...

Rueben

4 months ago

I remember we discussed the importance of keeping production and testing data separate, but I'm not sure if implementing two separate instances is necessary.

upvoted 0 times

...

Jackie

4 months ago

I'm feeling pretty confident about this one. The data privacy team has made it clear that the test and production data need to be kept separate, so the obvious solution is to create one or more additional business units for testing. That way, you can isolate the test data and ensure it doesn't get mixed with the production data.

upvoted 0 times

...

Tenesha

4 months ago

Okay, I've got this. The requirement is clear - the data in the sandbox should never be mixed with data in production during testing cycles. Based on that, I think the best option is to implement two separate Marketing Cloud instances, one for testing and one for production. That way, there's a clear separation between the two environments.

upvoted 0 times

...

Angelica

5 months ago

Hmm, I'm a bit unsure about this one. There are a few different options presented, and I'm not sure which one is the best recommendation. I'll need to think through the pros and cons of each approach.

upvoted 0 times

...

Becky

5 months ago

This seems like a straightforward question about keeping test and production data separate in Marketing Cloud. I think the key is to understand the options and choose the one that best fulfills the requirement.

upvoted 0 times

...

Marlon

9 months ago

I'm just hoping they don't accidentally send the test data to the CEO's inbox. That would be a true nightmare scenario!

upvoted 0 times

...

Stefanie

10 months ago

Test sends with the 'Is Testing' attribute - simple, yet effective. Gotta love it when the solution is right in front of you.

upvoted 0 times

...

Lynelle

10 months ago

Subscriber Filter? Sounds like a fancy way to sort out the good from the bad data. As long as it works, I'm on board!

upvoted 0 times

Dolores

8 months ago

Implementing two separate Marketing Cloud instances could be a solid solution as well.

upvoted 0 times

...

Alfred

8 months ago

I think creating separate business units for testing could also be a good option.

upvoted 0 times

...

Thersa

9 months ago

Yes, a Subscriber Filter can help keep production and test data separate.

upvoted 0 times

...

Nobuko

10 months ago

Using a separate business unit for testing is a clever way to stay organized. Just gotta remember which one is which, right?

upvoted 0 times

Fatima

9 months ago

D) Use Subscriber Filter per business unit to filter production from test data.

upvoted 0 times

...

Carol

9 months ago

Using separate business units definitely helps keep things organized.

upvoted 0 times

...

Adria

9 months ago

C) Create one or more additional business units for testing.

upvoted 0 times

...

Natalya

10 months ago

A) Implement two separate Marketing Cloud instances.

upvoted 0 times

...

Lashawn

11 months ago

I personally think option C) Create one or more additional business units for testing could also work well. It would provide a clear separation between test and production data.

upvoted 0 times

...