Pass the Salesforce Marketing Cloud Consultant Marketing-Cloud-Consultant Questions and answers with CertsForce

The best solution for fast, transactional emails like password resets is the Transactional Messaging API.

It is optimized for speed (near real-time delivery).

It supports notification of status via response payloads and optional callbacks.

Triggered Send Definitions are older and not as real-time or robust. Journey-based API entry methods (C and D) introduce unnecessary delays for critical transactional messaging.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Developer Guide – Transactional Messaging API Overview

→ "Transactional Messaging API provides fast, secure sending of transactional messages like order confirmations or password resets, with near real-time delivery."

Source: Salesforce Help – Transactional Messaging vs. Triggered Sends

→ "Transactional Messaging APIs are designed to deliver messages as quickly as possible, whereas classic Triggered Sends and API Event Journeys are better suited for marketing campaigns."

—

Comprehensive and Detailed Explanation:

The correct answer is C — Create a Journey with a Salesforce Campaign entry source and an Email Activity.

Salesforce Campaign Entry Source automatically injects Contacts or Leads into a Journey when they are added to a Campaign in Sales Cloud.

It’s the best method for triggering welcome or loyalty messages in near real-time, based on Campaign Membership.

❌ Why others are wrong:

A: Query and automation adds delay and isn’t real-time.

B: Content Builder Send Flow is for manual sends, not dynamic Journey entry.

D: Salesforce Data Entry Sources are broader and not directly tied to Campaign Membership.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder Salesforce Campaign Entry Source:

"The Salesforce Campaign Entry Source allows contacts or leads added to a campaign in Salesforce CRM to automatically enter a Journey in Marketing Cloud."

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

—

The correct answer is A , because:

In MobileConnect and Journey Builder SMS activities, phone number normalization ensures that mobile numbers are automatically formatted to include the appropriate country code (such as "+1" for the United States) based on a selected default country.

If the phone numbers coming from Salesforce (or any source) do not include a country code, enabling "Normalize Phone Number" in the Journey settings corrects this by automatically appending the country code according to the selected settings.

Salesforce official documentation states:

" Normalize Phone Number ensures that phone numbers missing a country code are automatically formatted based on a selected default country. This improves message deliverability in SMS activities within Journey Builder."

(Source: Salesforce Help - MobileConnect and Journey SMS Send Configuration)

✅ In this case:

Without normalization, SMS providers expect numbers in E.164 format (which requires the country code, e.g., +1 for US numbers).

If the number is missing the "+1", the message fails to send.

Enabling Normalize Phone Number in the Journey SMS settings fixes the issue without needing to reformat Salesforce records manually.

Why the other options are incorrect:

❌ B. Format the phone field in Salesforce as +1[phonenumber] :

While correct formatting helps, it requires manual mass update of existing records and doesn't automatically handle new ones, making it inefficient.

❌ C. Select 'US' as the sending country in SMS activity :

Selecting the sending country affects short code usage , not the normalization of incoming phone numbers.

❌ D. Configure the phone field in Salesforce as US locale :

Locale settings don't automatically add a "+1" country code to phone numbers; normalization is still needed.

Reference Extract from Salesforce MobileConnect documentation:

"Use Normalize Phone Number to correct phone number formatting errors for Journey Builder SMS sends. Automatically prepends country codes based on the specified country when absent."

(Source: Salesforce Marketing Cloud MobileConnect User Guide)

Thus, the correct answer is A .

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 — Build rules before uploading the respective content.

Best practice is to define dynamic content rules first (e.g., “Points < 1000: Content A; Points 1000–5000: Content B”) before building and uploading the content blocks.

This makes setting up Dynamic Content Blocks in Content Builder easier and more structured.

❌ Why others are wrong:

A: Custom Lists are older Email Studio concepts, not relevant to dynamic content best practices in Content Builder.

B: Standardizing field names is good practice, but not directly tied to dynamic content rule building.

C: Synchronized DEs are for Salesforce CRM data, which is not mentioned here.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Dynamic Content Setup:

"Create rules for dynamic content before associating the respective content assets to ensure correct audience targeting within the email template."

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

—

Comprehensive and Detailed Explanation:

The correct answer is C — Use Synchronized Data Extensions on the Case Object with a Boolean filter on the Contact Me field.

With Marketing Cloud Connect, the Case object can be synchronized into Marketing Cloud.

You can apply filters based on fields like "Contact Me = True" directly within Journey Builder or Automation Studio without manually importing reports.

❌ Why others are wrong:

A: Journey Builder doesn't handle direct data imports from Service Cloud.

B: Manual imports and Filter Activities are unnecessary when synchronized data is available.

D: Import Wizard processes are manual and not scalable for ongoing automated campaigns.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Synchronized Data Extensions:

"Synchronized Data Extensions allow you to bring Salesforce object data (such as Cases) into Marketing Cloud for use in segmentation, filtering, and journeys without manual imports."

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

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

Comprehensive and Detailed Explanation:

The correct answer is B — Contact ID.

When sending from Salesforce CRM using Marketing Cloud Connect and a Report, the Contact ID (or Lead ID if working with leads) must be included.

Marketing Cloud Connect uses the Contact ID as the unique identifier to associate the subscriber with the correct record in Salesforce.

Without the Contact ID, Marketing Cloud cannot perform the send correctly.

❌ Why others are wrong:

A: Individual ID is related to Salesforce's Individual Object for GDPR compliance, not standard send flows.

C: CampaignMember ID is used in Campaign context, not for newsletter signup or basic contact sends.

D: External ID is a custom field — not required or recognized by the Send Flow.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Marketing Cloud Connect Send from Salesforce:

"When sending using a Report from Salesforce CRM to Marketing Cloud, include the Contact ID or Lead ID in the report. Marketing Cloud uses this ID to map the subscriber and ensure accurate sending."

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

Since immediate ingestion is not required and there are potentially thousands of records per minute, the most efficient and scalable method is to aggregate the data in a daily export file and then import it via Automation Studio from the SFTP location.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Best Practices for Large Data Imports

→ "For high-volume data collection scenarios where real-time processing is not required, use daily bulk file imports through SFTP and schedule Automation Studio activities."

Source: Salesforce Help – Automation Studio Import Activities

→ "Use Automation Studio Import Activities to bring in large amounts of data from Enhanced FTP locations on a scheduled basis."

—

Comprehensive and Detailed Explanation:

The correct answer is B — Use an info capture message template to capture the response.

Info Capture templates are designed specifically to collect information via SMS (like survey responses, open text feedback, or registrations).

MobileConnect automatically writes the captured information to a selected Data Extension when using this template type.

❌ Why others are wrong:

A: Text-response messages are simple replies and do not auto-capture or save open-ended feedback to Data Extensions.

C: Outbound templates are designed for sending messages, not capturing replies.

D: Vote/survey templates are for fixed response options (e.g., 1 for Yes, 2 for No) — not open-ended text.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Info Capture Template:

"Use an Info Capture message template to collect and store SMS responses in a designated data extension."

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

—