Salesforce Updated Marketing-Cloud-Consultant Exam Questions and Answers by alexandros

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 answers are B and D.

B — The Mobile Number field must be Text type in MobileConnect and include country code (e.g., +1 555-555-5555).

D — A Phone type field is necessary to validate and standardize mobile number formats inside MobileConnect.

Both fields are used for identifying recipients during MobileConnect sends.

❌ Why others are wrong:

A and C: Locale fields are used for language/country preferences, not required for MobileConnect message sending.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Data Extension Requirements:

"When sending SMS using MobileConnect, data extensions must include a Mobile Number field (Phone or Text type, with international country code)."

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

—

Comprehensive and Detailed Explanation:

The correct answer is B — Use the Transactional Messaging API.

Salesforce Marketing Cloud offers the Transactional Messaging API specifically for sending critical, real-time, event-triggered communications like account logins, security alerts, order confirmations, etc.

These messages are delivered independently of Marketing Cloud’s normal send queues, ensuring faster delivery.

Transactional API messages are meant for one-to-one, personalized communications requiring immediate sending.

❌ Why others are wrong:

A: Injecting into a Journey is slower compared to the Transactional API and not optimized for high-priority transactional messages.

C: Triggered Email Interactions are an older feature and do not provide the scalability or deliverability speed of the Transactional Messaging API.

D: User-Initiated Emails are typically used for larger batches, not for individual transactional notifications.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Transactional Messaging API Overview:

"The Transactional Messaging API sends timely, personalized, high-priority messages. These messages are initiated from a system event, such as a user logging in from a new IP address."

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

—

To accomplish the requirement of diverting contacts in a birthday journey based on whether they have redeemed a promotional code (stored in a separate transactional data extension), NTO needs to use a Decision Split Activity using both Contact and Journey Data .

Decision Split Activity : In Journey Builder, the Decision Split Activity evaluates conditions to direct contacts down different paths. It can compare attributes from the journey’s entry source (Journey Data) and related data extensions (Contact Data) linked via Contact Builder.

Journey Data : This refers to the data from the entry source data extension (e.g., the customer data extension used for the birthday journey, containing the customer number).

Contact Data : This refers to data from other data extensions related to the contact, such as the transactional data extension containing promo code redemption details, also linked by the customer number.

Attribute-to-Attribute Comparison : The requirement specifies comparing the customer number field between the journey source and transaction data extensions. This comparison is achieved by configuring the Decision Split to evaluate both Journey Data (from the entry source) and Contact Data (from the related transactional data extension).

Why this solution works:

The Decision Split Activity allows NTO to check if a customer number in the journey’s entry source matches a customer number in the transactional data extension where a promo code was redeemed. If a match exists, the contact can be diverted to a different path, avoiding reminder emails.

Using both Contact and Journey Data ensures the comparison spans the two data extensions, which is necessary since the transactional data is stored separately.

Why the other options are incorrect:

A. Einstein Split Activity : Einstein Splits use AI-driven predictions (e.g., likelihood to open or purchase) rather than direct attribute comparisons. They are not suitable for comparing specific fields like customer numbers across data extensions.

B. Decision Split Activity using only Contact Data : Using only Contact Data would limit the comparison to attributes in related data extensions, excluding the journey’s entry source data (Journey Data), which contains the customer number from the birthday journey. Both data sources are needed for the comparison.

D. Decision Split Activity using only Journey Data : Using only Journey Data would restrict the comparison to the entry source data extension, ignoring the transactional data extension where promo code redemption data is stored.

Exact Extract from Salesforce Documentation:

Journey Builder Decision Splits : "Decision Splits evaluate attributes from the entry event data (Journey Data) or related data extensions defined in Contact Builder (Contact Data). To compare fields across these datasets, configure the split to use both Contact Data and Journey Data." (Source: Salesforce Help - Journey Builder Decision Splits )

Contact and Journey Data : "Journey Data is dynamic and tied to a specific journey instance. Use Journey Data when evaluating data related to a specific event. Contact Data includes attributes from related data extensions linked via Contact Builder." (Source: Salesforce Help - Journey Data vs Contact Data )