Marketing-Cloud-Consultant Salesforce Certified Marketing Cloud ConsultantSFMCExam (SP25) Free Practice Exam Questions (2025 Updated)

Triggered Sends from Salesforce CRM are processed via Apex Jobs. When they fail, the first step in diagnosing the issue is to review the Apex Jobs in Salesforce Setup to check for errors such as authentication failures, invalid data, or configuration issues.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Monitor Triggered Sends via Apex Jobs

→ "Triggered Sends initiated from Salesforce appear as Apex Jobs in Salesforce Setup. Review Apex Job logs to troubleshoot failures."

Source: Salesforce Marketing Cloud Connect Troubleshooting Guide

→ "For Salesforce-triggered sends, monitoring Apex Jobs provides immediate insight into errors or authentication issues."

Comprehensive and Detailed Explanation:

The correct answer is A — Check the "Include Replies as Attachments" box in RMM settings.

In the RMM configuration settings, you can set inbound emails to be auto-forwarded and attach the original reply as a file.

This method ensures the Customer Success team can review the full original customer message without parsing dynamic fields or personalization strings.

❌Why others are wrong:

B: There are no RMM dynamic content blocks for rendering reply bodies.

C: Querying the RMM data view would require custom queries and complex setups, which is unnecessary for simple forwarding.

D: RMM personalization strings are used in response handling templates, not for forwarding attachments.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Reply Mail Management Overview:

"Use the Include Replies as Attachments option to attach customer replies when forwarding messages to designated addresses. This feature ensures that the original message body is included."

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

—

Comprehensive and Detailed Explanation:

The correct answer is B — Use Tracking Extract, File Transfer, and Import activities from Automation Studio to inject the subscribers into a data extension used as an Entry Source by Journey Builder.

Tracking Extract Activity allows the extraction of bounced or held subscribers’ data (bounce reasons like "Held").

File Transfer Activity moves the extracted file into the Import directory.

Import Activity loads the file into a Data Extension, which can then be used as the entry source for a re-engagement journey via SMS.

❌Why others are wrong:

A: SQL Query only works if the data is already in a Data Extension; Held status bounce data typically resides in Tracking Extracts.

C: CloudPages Entry Source is incorrect — you want an automated process for SMS.

D: API Event would require custom API calls, but there's no mention of development resources.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract Activity:

"Use a Tracking Extract Activity to pull tracking data, such as bounces or held status, into a file that can be imported into a data extension for use in journeys or reports."

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

—

✅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."

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

In Marketing Cloud's Automation Studio, when configuring a File Drop Automation, the system automatically detects and uses the file that triggers the automation.The Import File Activity within this automation doesn't require a specific filename; instead, it processes the file that initiated the automation.Therefore, there's no need to set a dynamic file naming pattern or check additional options.​

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."

✅Comprehensive and Detailed Explanation:

B (Publication List)allows subscribers to opt down or up in terms of subscription types. Customers indicating product interests and preferred messaging frequency would fit into Publication List management.

C (Auto-Suppression List)can exclude certain groups or preferences at the message send level automatically, especially if customers opt-down or unsubscribe partially.

❌Why Others Are Incorrect:

A: Suppression Lists are manually managed and aren't dynamically tied to preferences.

D: Domain Exclusion blocks entire domains (e.g., gmail.com) — not individual preference management.

Exact Extract:

Salesforce Help:Publication Lists Overview

"Publication lists manage opt-ins and opt-outs at a more granular level, allowing customers to control which messages they want to receive."

Salesforce Help:Auto-Suppression Lists

"Auto-suppression lists automatically prevent messages from being sent to specific subscribers based on business rules and preferences."

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

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

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 )

—

You would:

Use an Engagement Split in Journey A to track who engaged (opened or clicked).

After the Engagement Split, capture the engagement decision (typically Boolean) into an attribute or Data Extension.

Then use Automation Studio to query the JourneyActivity data views for those who engaged and inject them into Journey B.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Engagement Split Activity

→ "The Engagement Split activity evaluates contacts based on interactions with an email activity, such as opens or clicks."

Source: Salesforce Help – Journey Activity and Data Views

→ "Query JourneyActivity Data Views to retrieve information about contact flow and outcomes, including engagement split results."

—

Comprehensive and Detailed Explanation:

The correct answer is C — An external system to receive and confirm callback and subscriptions.

Marketing Cloud’s Transactional Messaging API supports Event Notification Service (ENS), where an external endpoint (callback URL) can subscribe to event notifications like “Not Sent.”

You need an external system capable of receiving real-time POST messages (JSON format) from Marketing Cloud and sending 2xx HTTP status responses to confirm receipt.

❌Why others are wrong:

A: There is no "Not Sent Notification activity" inside Transactional Journeys — it’s API-based event notifications.

B and D: Datorama and Interaction Studio are analytics and personalization tools, not real-time event handling systems.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Transactional Messaging Event Notification Service:

"An external system must be configured to subscribe to notifications and must be capable of responding to callbacks with an HTTP 2xx status. Event types include Sent, Delivered, Not Sent, etc."

(Source:https://help.salesforce.com/s/articleView?id=sf.mc-transactional-api-event-notifications.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is A — Set up and pull data from a SendLog Archive Data Extension.

To keep SendLogs manageable, best practice is to archive older data periodically to a different data extension.

This allows marketers to pull data for analysis without affecting the live SendLog performance.

Queries can then target the Archive DE based on email address for troubleshooting.

❌Why others are wrong:

B: Filtering on a massive SendLog DE without archiving is inefficient and slow.

C: Data Views (_Sent, _Subscriber) only store general send tracking data, not full SendLog personalization snapshots.

D: Tracking Extracts are for broader system tracking (sent, opens, clicks), not detailed troubleshooting with personalization.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — SendLog Management Best Practices:

"To maintain optimal performance, implement archiving for SendLog data by moving old records to archive Data Extensions at regular intervals."

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

—

The correct answers areA, C, and D, because:

When planning the number ofBusiness Units (BUs)for a Marketing Cloud Enterprise 2.0 account, Salesforce recommends evaluatingorganizational structureanddata/content needscarefully. Business Units help segment marketing assets, contacts, and campaigns, often aligned to brands, regions, or departments.

According to Salesforce official documentation:

"When considering the number of Business Units needed, important factors include:

Number of brands, products, or regions that require separate marketing efforts.

Requirements to separate data and content between business units (for security, branding, or operational independence).

The need for dedicated development or test environments within Marketing Cloud."

(Source: Salesforce Marketing Cloud Implementation Guide – Business Unit Planning)

Let's break it down:

✅A. Number of brands/geographies which NTO operates

Different brands or regions often need separate BUs to manage independent marketing strategies, content, and contacts.

✅C. If testing/development business unit(s) are required

It’s a best practice to have separate BUs for development and testing purposes to avoid interfering with live sends.

✅D. If data/content needs to be segregated between brands/geographies

When different teams or brands should not have access to each other's customer data or assets, separate BUs ensure proper data governance and security.

Why the other options are incorrect:

❌B. Number of Sales Cloud sandboxes:

The number of Sales Cloud sandboxes is irrelevant to how many BUs you need. BUs are for organizational segmentation, not related to sandbox environments.

❌E. Number of Marketing Cloud users:

User count affects licensing and access management but does not drive the number of BUs needed.

Additional official note from Salesforce:

"Use Business Units to separate marketing activities by division, brand, or region. Business Units are not determined by the number of users or CRM sandboxes."

(Source: Salesforce Help - Enterprise Account Structure Overview)

Thus, the correct choices areA,C, andD.

For large volumes (one million records) and complex segmentation (10+ fields), the best approach is to use Automation Studio to query Synchronized Data Extensions and build a filtered Salesforce Data Extension. Then, use that Data Extension for sending in Email Studio.

Sending directly to a Salesforce Report is not recommended for high volumes or complex segmentation.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Synchronized Data Extensions Best Practices

→ "For high-volume sends and complex segmentation, use Automation Studio to query synchronized data and populate Salesforce Data Extensions."

Source: Salesforce Help – Email Studio Sending Best Practices

→ "Perform complex segmentation prior to sending by preparing Data Extensions, especially for high-volume email sends."

—

The correct personalization string to provide a "View as Webpage" link in an email is %%view_email_url%%. When this string is placed inside the href attribute of a hyperlink, Marketing Cloud automatically generates a URL to a hosted version of the email content.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Personalization Strings

→ "%%view_email_url%% – This personalization string inserts a link to view the email as a webpage. Typically used for the 'View Online' functionality in email templates."

Source: Salesforce Marketing Cloud Email Studio Guide

→ "Use %%view_email_url%% within your hyperlink to allow recipients to view the message as a webpage."

Because of the complex relationships (multiple objects and property matches), it's best to use Automation Studio to:

Query and flatten the relational data into a single personalized Data Extension.

Then use Journey Builder to send based on that prepared data.

This approach avoids heavy personalization scripting inside emails (which would reduce performance) and makes the sends more efficient.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Journey Data Preparation Best Practices

→ "For complex relationships and personalization requirements, prepare the data with Automation Studio before injecting into Journey Builder."

Source: Salesforce Help – Personalization in Journey Emails

→ "Avoid heavy personalization logic inside the email. Prepare the personalization using query activities beforehand to ensure send performance."

Comprehensive and Detailed Explanation:

Correct answers are A and D.

A — In Mobile Studio, Filtered Lists can be created using MobilePush Demographics attributes (device platform, app version, opt-in status, etc.).

D — In Contact Builder, you can create a Filtered Data Extension based on records existing in the MobilePush Demographics Attribute Group.

Both allow segmentation of registered Mobile Push users without manual queries.

❌Why others are wrong:

B: Automation Studio queries on _MobilePushDemographics are possible, but it’s not the standard business-user-friendly method.

C: Journey Builder should use properly segmented sources, not mass targeting.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobilePush Demographics Segmentation:

"MobilePush users can be segmented based on demographic attributes available through MobilePush Demographics in Contact Builder or Mobile Studio Filtered Lists."

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

—

Fatigue Rules in Einstein Content Selection allow marketers to limit how many times a specific asset can be shown to a customer over a defined time frame. This ensures better asset variety and prevents customers from seeing the same content repeatedly.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Einstein Content Selection Fatigue Rules

→ "Fatigue rules allow you to set restrictions on how often an asset or class of assets appears to an individual over a specific timeframe, improving engagement and reducing redundancy."

—

When disconnecting and reconnecting instances in a Multi-Org setup, it’s mandatory to first remove all user mappings, attribute mappings, and tracking subscriptions associated with the sandbox. This is necessary to cleanly connect the new (production) instance without conflicts.

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Disconnect and Reconnect Marketing Cloud Connect Accounts→ "Before connecting a new Salesforce org to Marketing Cloud, remove existing user mappings, attribute mappings, and tracking subscriptions associated with the current org."

Source: Marketing Cloud Multi-Org Setup Guide→ "In a Multi-Org configuration, disconnecting an org requires removing all dependent mappings and synchronized objects before connecting a new Salesforce org."

The most native, no-code solution would be using an Engagement Split in Journey Builder to capture customer responses (positive or negative) and, for negative responses, trigger a Case Activity to automatically create a Case record in Service Cloud.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Activities in Journey Builder

→ "Use Case Activity in Journey Builder to create a Case record in Salesforce based on customer behavior within the journey."

Source: Salesforce Help – Journey Builder Engagement Splits

→ "Engagement Split evaluates a contact’s interaction and directs them down a different path in the Journey based on their engagement."

—

—

—