Free MCE-CON-201 Practice Test Questions and Answers (2026)

Guide Template Language (GTL) is the most appropriate tool for this task. GTL is a powerful templating language within Salesforce Marketing Cloud specifically designed to handle and render data from JSON sources, such as an API response. It includes the HTTPGet() function, which can call the external weather API at send time. GTL's syntax then allows for easy, native parsing of the returned JSON data and direct rendering of the personalized weather information within the email content, fulfilling both requirements of the request.

A. Node.JS: Node.js is a server-side JavaScript runtime environment. It is not a scripting language that can be embedded directly within a Marketing Cloud email to parse and display content.

B. Apex: Apex is the proprietary programming language for the core Salesforce platform (e.g., Sales Cloud). It does not execute within the context of a Marketing Cloud email for personalization.

C. SSJS: While Server-Side JavaScript (SSJS) can make HTTP requests to an API and parse JSON, GTL is the more specialized and streamlined tool for both parsing and displaying the data within the email template itself.

1. Salesforce Developer Documentation, Guide Template Language, "Data Functions": This document details the HTTPGet() function. It states, "Use this function to retrieve content from a specified URL at send time... You can use Guide to parse the returned JSON..." This directly confirms GTL's capability to fetch, parse, and display API data. (See the section on HTTPGet(1,2,3,4)).

2. Salesforce Developer Documentation, Guide Template Language, "Use Cases": The documentation provides examples of using GTL to parse JSON data sources. The "JSON Data Source" use case explicitly shows how to iterate through a JSON array and access its properties for display, which is the core requirement of the question.

3. Salesforce Developer Documentation, "Introduction to Programmatic Languages": This guide distinguishes the roles of different languages in Marketing Cloud. It positions GTL for "creating personalized, data-driven messages" and handling "JSON data," while positioning SSJS for more complex backend logic and Apex as part of the core Salesforce platform, not Marketing Cloud email scripting.

An Auto-Suppression List is the ideal solution because it is designed for automated, persistent exclusion across multiple sends. The customer can create an auto-suppression list, populate it daily using their SQL query activity in an automation, and then assign this list to specific Sender Profiles. Any future email send that uses one of the assigned Sender Profiles will automatically exclude all email addresses on that list without requiring any manual intervention on individual sends. This directly meets the requirement for automated exclusion based on sender profiles.

A. A publication list is used for managing subscriber preferences for different communication types (e.g., newsletters) and is not designed for automated, sender-profile-based suppression.

B. An exclusion data extension must be manually selected for each individual email send or journey activity; it does not provide automated suppression for all future sends.

D. A suppression list, like an exclusion data extension, is applied manually at the time of send and is not automatically associated with sender profiles for future sends.

1. Salesforce Help. (2023). Auto-Suppression Lists. Salesforce, Inc. Retrieved from https://help.salesforce.com/s/articleView?id=sf.mcesautosuppressionlists.htm&type=5. This document explicitly states, "Use an auto-suppression list to prevent subscribers on the list from receiving emails from your account sent using a specific sender profile."

2. Salesforce Help. (2023). Create an Auto-Suppression List. Salesforce, Inc. Retrieved from https://help.salesforce.com/s/articleView?id=sf.mcescreateanautosuppressionlist.htm&type=5. This guide details the process of creating the list and associating it with sender profiles and send classifications.

The most efficient and scalable method is to use Marketing Cloud Connect's Synchronized Data Extensions. This feature allows for the near real-time replication of Salesforce object data into Marketing Cloud. During the configuration of the synchronization for the Case object, a filter can be applied directly. By setting a boolean filter for the "Contact Me" checkbox field to equal True, only the relevant records will be brought into Marketing Cloud. This approach is automated, ensures data accuracy, and is purpose-built for integrating filtered Salesforce data for marketing campaigns.

A. Journey Builder is an orchestration tool for customer journeys, not a primary tool for bulk data import and segmentation.

B. While possible, importing all cases and then filtering in Automation Studio is less efficient than filtering the data at the source during synchronization.

D. Using the Import Wizard with a Salesforce Report is a manual, point-in-time process and is not suitable for an automated, recurring campaign.

1. Salesforce Help, Marketing Cloud Connect > Synchronized Data Sources. This documentation states, "Use Synchronized Data Sources to bring your Sales Cloud and Service Cloud data into the Marketing Cloud... To limit the data that is synchronized, apply a filter."

2. Salesforce Help, Synchronize a Salesforce Object. This guide details the setup process, including Step 4: "To sync a subset of records, select a boolean field and a value to use for filtering." This directly corresponds to the solution of filtering on the "Contact Me" checkbox field.

To initiate a journey when a new contact is created for a specific account, the Salesforce Data Entry Source in Journey Builder is the correct tool. This entry source should be configured to listen for the creation of records on the Contact object. Filter criteria can then be applied to ensure that only contacts belonging to the 'select accounts' are injected into the journey, precisely matching the B2B customer's requirement for targeted, account-based journey initiation.

A. The trigger event is the creation of a Contact, not a Lead. Using the Lead object would not capture the intended audience for this journey.

C. The journey is initiated by the creation of a Contact record. While related to an Account, the triggering event does not occur on the Account object itself.

D. A "Welcome Email Configuration" is not a standard Journey Builder entry source or a feature of Marketing Cloud Connect for initiating complex journeys.

1. Salesforce Help, Journey Builder, "Salesforce Data Entry Source". This document explains, "Use the Salesforce Data entry source in Journey Builder to admit Salesforce contacts, leads, users, or person accounts from a Sales Cloud or Service Cloud org into a journey." It details configuring the entry source based on the creation or update of an object record, directly supporting the use of the Contact object as the trigger.

The unsubscribe the customer performed was stored against the subscriber whose Subscriber Key was the email address used in the automation send. Marketing Cloud Connect, however, always uses ContactID/LeadID as the Subscriber Key. Because an unsubscribe is keyed only to the specific Subscriber Key value, the ContactID subscriber remained mailable, so the MCC send reached the customer even though the same email address had been unsubscribed the week before.

A. Marketing-Cloud-Connect send permissions in Salesforce do not influence how an unsubscribe is applied.

B. Email Opt-Out is recorded regardless of where the send originated; it is Subscriber-Key specific.

D. Page-layout changes do not affect Marketing Cloud’s internal unsubscribe status.

1. Salesforce, “Marketing Cloud Connect Implementation Guide”, Subscriber Key and Unsubscribe Management, pp. 45-48 (Spring ‘24).

2. Salesforce, “Subscriber Key Best Practices”, Help Doc ID 000335924, section “Effect of differing Subscriber Keys on unsubscribe behavior”, ¶3-4.

3. Salesforce, “CAN-SPAM Compliance in Marketing Cloud”, Help Doc ID 000255676, §“How Unsubscribes are Stored”.

The scenario requires a message to be sent as fast as possible in response to a specific event (API call from a system detecting a new IP login) and must contain personalized, sensitive data. The Transactional Messaging API is designed specifically for this use case. It provides a high-throughput, low-latency, REST API for sending critical, non-promotional messages like security alerts, password resets, and order confirmations. It bypasses standard marketing queues to ensure near-instantaneous delivery, which is crucial for the described security-sensitive communication.

A. Journeys are designed for marketing automation paths and have inherent processing delays (typically 1-5 minutes), making them too slow for time-sensitive transactional alerts.

C. Triggered Emails are a legacy feature in Email Studio. While they are event-driven, the Transactional Messaging API is the modern, more performant, and recommended solution for this requirement.

D. User-Initiated Emails are manual sends executed by a user from within the Marketing Cloud interface and are not suitable for automated, real-time triggers.

1. Salesforce Developer Documentation, Marketing Cloud APIs, "Transactional Messaging API". The documentation states, "Use the Transactional Messaging REST API to send time-sensitive, non-promotional messages, such as password-reset emails and shipping-confirmation messages."

2. Salesforce Help, Journey Builder, "Events". The documentation on Journey Builder events implies a processing time that is not instantaneous, contrasting with the purpose of a transactional API.

3. Salesforce Help, Email Studio, "Triggered Emails". This documentation describes the older functionality, which has been largely superseded by Journey Builder and the Transactional Messaging API for modern use cases.

Before building a segment, marketers must define “engagement”—for example, opens in the last 90 days or clicks in the last 30 days. This criterion determines which subscribers qualify for the discount and drives the query or filter logic used to generate the audience. Deciding offer content, timing, or sender does not influence the mechanics of segmentation; engagement definition does.

A – Offer content is creative, unrelated to how audience is selected.

B – Send timing affects scheduling, not audience generation rules.

C – From-name impacts brand recognition, not who is placed in the audience.

1. Salesforce Marketing Cloud: “Email Segmentation Best Practices”, Marketing Cloud Engagement Guide, section “Define Engagement Metrics Before You Segment.”

2. Salesforce Trailhead: “Segment Your Audience”, Marketing Cloud Engagement for Advertisers module, unit ‘Determine who is engaged’.

Deployment Manager is the designated Marketing Cloud application for migrating configurations between different Marketing Cloud accounts or Business Units. It allows users to create a "snapshot" of items like journeys, data extensions, attribute groups, and automations from a source account and deploy them to a target account. This functionality directly addresses the need to move configurations across development, UAT, and production environments, significantly speeding up the process and reducing manual effort and errors.

A. Configuration Manager: This is not a standard Salesforce Marketing Cloud product. The correct tool for this purpose is named Deployment Manager.

B. Change Sets: Change Sets are a tool used for migrating metadata between connected Salesforce CRM orgs (e.g., Sales Cloud, Service Cloud), not between Marketing Cloud accounts.

D. Ant Migration Tool: The Ant Migration Tool is a command-line utility for moving metadata between a local directory and a Salesforce CRM org, not for Marketing Cloud assets.

1. Salesforce Help, Marketing Cloud, Deployment Manager, "Use Deployment Manager to copy the design of a journey, data extension, attribute group, or automation from one Marketing Cloud business unit to another."

2. Salesforce Help, Marketing Cloud, Deployment Manager Use Cases, "Move Journeys from a Sandbox to a Production Account. Create a journey in a test or sandbox account, then deploy it to your production account."

Because the Appointment object lacks a direct contact relationship, the cleanest pattern is to let Salesforce CRM fire a Process Builder flow that calls the Marketing Cloud API Event. The API Event delivers ContactKey plus appointment attributes to Journey Builder; any journey can then use a Send Email activity followed by a Salesforce Update Activity to set the Confirmation Sent checkbox. This respects real-time notification, permits nightly status changes, and avoids schema limitations of the Salesforce Data entry source.

A – Salesforce Data Entry requires a Contact-centric relationship and cannot start from an unrelated custom object without additional customization.

C – Data Extension entry + Automation adds latency and lacks a native path to update CRM records in real time.

D – Salesforce Send is batch-oriented; SSJS updates are custom code and do not scale for per-record confirmation.

1. Salesforce Help, “API Event Entry Source in Journey Builder”, 2024-01-05, §‘Use with Process Builder’.

2. Marketing Cloud Connect Guide, “Salesforce Activities—Supported Entry Sources”, p. 9 (shows Update Contact works with any entry type).

3. Trailhead Module “Journey Builder Advanced”, Unit ‘Using API Events’, 2023, Steps 2–4.

Einstein Content Selection supports Asset Fatigue rules, letting marketers specify how many times an individual asset can be shown to the same contact in a given time window. Applying fatigue rules to the product Asset Class prevents a customer from repeatedly receiving the same image within two weeks.

A. More images doesn’t guarantee repetition control.

B. Fallback assets display only when no eligible asset exists; they don’t limit frequency.

C. Engagement Frequency governs message volume, not per-asset exposure limits.

1. Salesforce Help, “Einstein Content Selection – Asset Fatigue,” section “Configure Fatigue Rules” (2023).

2. Salesforce Release Notes, Summer ’23, “Enhance Content Personalization with Asset Fatigue Settings,” p. 302.