Marketing-Cloud-Consultant Exam Dumps - Salesforce Marketing Cloud Consultant Questions and Answers

The correct answer is B , because:

In Salesforce Marketing Cloud, Reply Mail Management (RMM) processes replies to email messages and can automatically take action — such as unsubscribing a user — when specific unsubscribe keywords are detected.

Salesforce official documentation states:

" Reply Mail Management uses filtered keywords to identify unsubscribe requests. You must configure these keywords manually. If users reply with phrases not included in the filtered keyword list, they won't be unsubscribed automatically. "

(Source: Salesforce Marketing Cloud Reply Mail Management Overview)

Thus, if phrases like "take me off your list" or "opt out" are not yet added to the filtered keyword list, RMM will not recognize them as unsubscribe requests, and no action (unsubscribe) will be taken.

✅ To correct this:

You must add custom phrases such as "take me off your list" and "opt out" to the Filtered Keywords list in RMM settings.

Why the other options are wrong:

❌ A. Ensure the DNS Record Redirect is correctly configured :

DNS redirection issues affect reply routing, not keyword detection.

❌ C. Ensure the two phrases are added to the "Filtered Keywords" data extension :

There is no "Filtered Keywords" data extension. It’s a configuration inside RMM settings, not a data extension.

❌ D. Ensure "Common Misspellings" is selected as one of the Reply Filters :

"Common Misspellings" handles typos but won't automatically detect entirely new phrases unless those phrases are explicitly added.

Further reference:

"Customizing the filtered keywords list improves unsubscribe recognition. Without these custom keywords, subscriber responses will not trigger the intended actions."

(Source: Salesforce Marketing Cloud Admin Guide - Reply Mail Management Configuration)

Thus, B is the correct solution.

✅ Comprehensive and Detailed Explanation:

A (Use Data Designer in Contact Builder) is necessary because relationships must be created between data extensions in Contact Builder for Journey Builder to access and evaluate cross-data attributes.

B (Utilize Entry Data on a Decision Split) is required because Decision Splits use Entry Data or Contact Data attributes (made available via the relationships created).

❌ Why Others Are Incorrect:

C : Data Relationships in Email Studio are for segmentation and sends, not Decision Splits in Journey Builder.

D : Automation Studio updates are irrelevant to Decision Splits in real-time journey flows.

Exact Extract:

Salesforce Help: Data Designer - Contact Builder

"Use Data Designer in Contact Builder to define relationships between data extensions. These relationships allow Journey Builder to evaluate contact data across multiple extensions when using activities such as Decision Splits."

Salesforce Help: Journey Builder Decision Split

"Decision Splits evaluate attributes from the entry event data or related data extensions defined in Contact Builder."

════════════════════════════════════════════

A Verification Activity in Automation Studio checks the number of records in a data extension before proceeding. If the number exceeds a specified threshold (e.g., 2500 contacts), the automation can be halted, preventing the send. ​

Synchronized Data Extensions via Marketing Cloud Connect allow syncing Salesforce objects (such as Leads, Contacts) into Marketing Cloud at near real-time speeds (approximately every 15–30 minutes). To filter only customers with consent selected, they can configure a Filtered Data Extension based on the synchronized object.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Synchronized Data Sources Overview → "Synchronized Data Sources allow you to automatically sync Salesforce object data into Marketing Cloud. The sync interval can be configured up to every 15 minutes."

Source: Marketing Cloud Connect Implementation Guide → "To target a subset of synchronized records, configure Filtered Data Extensions based on specific criteria, such as opt-in status or custom fields."

—

✅ Comprehensive and Detailed Explanation: An Auto-Suppression List is specifically designed to automatically exclude specific email addresses or Subscriber Keys from being sent emails in Marketing Cloud. In this case, since the list of competitors' email addresses is static and curated, populating an Auto-Suppression List with these known addresses ensures that no emails are sent to them without requiring manual intervention.

❌ Why Other Options Are Incorrect:

A: Using Subscriber Keys would require guaranteed mapping, but email address is the direct data available here.

B: Queries require manual maintenance and are not an automatic suppression mechanism.

C: Exclusion Lists typically apply to one send definition or journey; Auto-Suppression Lists apply globally across all sends.

Exact Extract: Salesforce Help: Auto-Suppression Lists

"An auto-suppression list prevents email sends to specific subscribers globally, based on Subscriber Key or Email Address."

════════════════════════════════════════════

✅ Comprehensive and Detailed Explanation: A Send Log captures detailed send-time information such as which email was sent, to which address, and when. You can customize a Send Log to record additional fields like email address, subscriber key, campaign name, etc. This meets the requirement for tracking exactly which email address received which email .

❌ Why Other Options Are Incorrect:

A: The Recent Email Send Report shows aggregate send information but doesn't track individual addresses dynamically.

B: Data Views store general event tracking (open, click) but not direct customizable fields like Send Log does.

D: Tracking Extracts provide bulk tracking data but are not customizable for specific needs like this.

Exact Extract: Salesforce Help: Send Logs Overview

"Send Logs record information about the subscribers you send messages to, and allow you to track what content was sent to each subscriber."

════════════════════════════════════════════

Comprehensive and Detailed Explanation:

The correct answer is D — Journey Builder multi-step journey with an API entry event and a decision split.

API Entry Event: Order system triggers a real-time entry into the Journey when the order is ready.

Decision Split: Based on customer's communication preference (SMS or Email), the journey will send the appropriate message.

❌ Why others are wrong:

A: MobileConnect Outbound Message can't dynamically decide fallback channel inside AMPscript easily.

B: Transactional Send Journeys are typically for single email sends, not channel preference branching.

C: Automation Studio is time-based, not ideal for real-time order notifications and dynamic preference handling.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder API Entry Event:

"API Event Entry allows external systems to trigger customer journeys in real-time, optionally combined with Decision Splits to deliver different channel communications based on customer attributes."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_jb_api_event_source.htm )

When a new user registers through the mobile app, and the ContactKey isn't immediately set, the MobilePush SDK assigns a temporary identifier (a GUID) to the device. This results in the creation of a new Contact in Marketing Cloud. Once the user's information is synced from Sales Cloud and the ContactKey is established, the device can be correctly associated. However, until this association occurs, the system treats the device as belonging to a separate, anonymous contact. ​

Comprehensive and Detailed Explanation:

The correct answer is D — Contact Builder Attribute Groups.

Contact Builder Attribute Groups allow you to combine multiple Data Extensions (e.g., purchases and loyalty membership) into one relational view.

Then you can easily query and filter based on conditions like "purchase date in last 6 months AND not a loyalty member."

❌ Why others are wrong:

A: Behavioral Triggers are related to real-time actions like website behavior, not cross-data queries.

B: Advertising Studio is for paid advertising, not internal audience segmentation.

C: Customer Data Platform (CDP) would be overkill unless NTO had an enterprise-wide CDP already (which isn’t mentioned).

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Contact Builder Attribute Groups Overview:

"Use Attribute Groups to define and model relationships between data extensions and organize contact attributes to create targeted audiences."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_cb_attribute_groups.htm )

—

Salesforce Campaigns are the best way for Sales Cloud users to manually create a segment of Leads and Contacts. Through Marketing Cloud Connect, Salesforce Campaigns can be used directly as an audience source in the Content Builder Send Flow, allowing quick selection and targeting without custom queries.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect and Salesforce Campaigns

→ "Salesforce Campaigns can be used as an audience for sending emails from Marketing Cloud. Campaign Members (Leads and Contacts) can be targeted directly."

Source: Salesforce Help – Send Flow and Salesforce Data

→ "When sending an email using Content Builder’s Send Flow, users can select Salesforce Campaigns as the audience source if Marketing Cloud Connect is enabled."