Free MCE-Con-201 sample questions

Correct answer: Scope by User

In a Multi-Org environment, 'Scope by User' is the configuration that respects the Salesforce user's data visibility rules when accessing Marketing Cloud Connect features. If a Marketing Cloud user is mapped to a Salesforce user in the European org, 'Scope by User' ensures they only see reports, sends, and data consistent with that Salesforce user's permissions, effectively segregating the view between regions.

Correct answer: Link Subscribers to Bookings in an Attribute Group with a One-to-Many relationship.

To support a journey based on transaction dates where a single contact has multiple records (bookings), the relationship in Contact Builder must be One-to-Many. This allows the journey engine to evaluate each booking record independently against the entry criteria (3 days before booking date).

Correct answer: REPLACE and CONCAT

The consultant should use nested REPLACE functions to strip out non-numeric characters (parentheses, dashes, dots, spaces) and then use CONCAT (or the '+' operator) to prepend the country code if it is missing. This ensures the data meets the strict E.164-like formatting requirements of MobileConnect.

Correct answers: The entry criteria involve complex cross-object logic involving more than two levels of object depth.; The campaign requires data from a custom object that has no direct relationship to the Contact or Lead object.

Salesforce Data Entry filters are limited in how deep they can traverse object relationships. For complex criteria involving multiple hops (e.g., Account -> Custom Obj A -> Custom Obj B), it is better to sync the data and use SQL to segment the audience precisely before injecting them into the journey.

Salesforce Data Entry Events generally require the source object to be related to a Who (Lead/Contact/User) or Person Account. If the data resides in a custom object with no direct link, syncing the data first and then using a scheduled automation or query to identify the audience is a necessary architectural pattern.

Correct answer: Risk: Blocking by ISPs due to lack of reputation. Mitigation: Implement an IP warming plan ramping up volume over 4+ weeks.

A new Dedicated IP has no sender reputation. Sending high volumes (2M) immediately looks like spam behavior to ISPs (Gmail, Yahoo, etc.) and will result in blocks or bulking. The standard mitigation is IP warming: starting with small volumes to highly engaged users and doubling volume every few days/weeks to build a positive reputation history. xychart-beta title "IP Warming Volume Strategy" x-axis [Week 1, Week 2, Week 3, Week 4] y-axis "Volume" 0 --> 500000 bar [50000, 100000, 250000, 500000]

Correct answer: Engagement Split

The Engagement Split activity is specifically designed to evaluate user interaction (Opens or Clicks) with a specific email sent previously in the same journey. It directs contacts down a 'Yes' path if they met the criteria (clicked) and a 'No' path if they didn't.