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

Comprehensive and Detailed Explanation:

The correct answer is D — Create and send to a sendable data extension containing those needed fields using a query activity.

Pre-populating a single sendable data extension with all necessary personalization fields eliminates the need for real-time lookups during sending.

It dramatically speeds up send processing because personalization is sourced directly from the send context.

❌ Why others are wrong:

A: Profile attributes are outdated and limited for handling many fields from multiple sources.

B: Send throttling slows down sends to control delivery rate — it doesn’t speed it up.

C: Lookup functions cause real-time database queries during send time, slowing down large sends.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Personalization and Send Performance:

"To improve send performance, include all required personalization attributes in the send context (Data Extension) rather than relying on AMPscript Lookups at send time."

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

—

In Marketing Cloud, if multiple BUs need access to the same data (like Product Information), the best practice is to store and manage the data extension in the top-level (Parent) BU and share it with the Child BUs using Shared Data Extensions.

This avoids duplication, ensures consistency, and simplifies data management.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Shared Data Extensions

→ "Shared Data Extensions enable parent business units to share data extensions with one or more child business units for consistent access and management."

—

Since the marketing team has very little coding experience, the most appropriate solution is to use an Import Activity to automatically pull files from an SFTP location into the Auto-Suppression List. This is a low-code, easy-to-manage approach and highly recommended by Salesforce for handling suppression management in Automation Studio.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Import Activity in Automation Studio

→ "An Import Activity in Automation Studio allows users to import data into a data extension or list from a file in an FTP location. This method supports minimal coding experience and is suitable for Auto-Suppression List management."

Source: Salesforce Help – Auto-Suppression Lists

→ "Auto-Suppression lists automatically exclude addresses from email sends. They can be managed via Import Activities in Automation Studio."

—

Since the marketer has little coding experience, creating Data Relationships (via Contact Builder) and enabling segmentation using Data Filters is the best approach. Data Filters are a marketer-friendly, drag-and-drop tool that allow segmentation without the need for SQL or scripting.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Filters

→ "Data Filters allow non-technical users to segment data extensions using an intuitive interface without needing SQL or scripting knowledge."

Source: Salesforce Help – Data Relationships in Contact Builder

→ "Data Relationships connect Data Extensions and enable users to create filters based on joined data without writing code."

—

Comprehensive and Detailed Explanation:

The correct answer is C — Data Extract with the Tracking Extract type > File Transfer from Safehouse > File Transfer unzip > Import File.

Tracking Extract Activity pulls detailed email event data, including 'Not Sent' events, into a compressed file (.zip).

You need a File Transfer Activity to move the file from the Safehouse and unzip it.

After unzipping, Import Activity loads the extracted data into a Data Extension where queries can run.

❌ Why others are wrong:

A and B: Data Extension Extract type is for DE records, not tracking events like Not Sent.

D: Data Factory Utility is not part of the standard Automation Studio activities for these operations.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract and Automation Studio:

"Use Tracking Extract to retrieve event-level data, including Not Sent events, then use a File Transfer Activity to unzip and import the extracted data for analysis or reporting."

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

—

The correct answer is D, because:

In Salesforce Marketing Cloud, to capture unsubscribe statuses across all Business Units (BUs) in an Enterprise 2.0 account, the system data view _BusinessUnitUnsubscribes must be used.

_BusinessUnitUnsubscribes provides unsubscribe event data across all business units, showing which subscriber unsubscribed, in which BU, and when — making it ideal for consolidated enterprise-level reporting or synchronization to external systems like a CRM.

Official Salesforce documentation states:

"_BusinessUnitUnsubscribes: Returns a record for each unsubscribe event, per business unit, providing a view of the unsubscribe status at a BU level. This view is used primarily in Enterprise 2.0 accounts to track unsubscribe activity across multiple business units."

(Source: Salesforce Marketing Cloud Official Data Views Documentation)

Key Points from Documentation:

_Subscribers (Option B) gives general subscriber data (status like Active, Bounced, Held), but does not track individual unsubscribe events per BU.

_Unsubscribe (Option C) focuses on unsubscribes but not separated by Business Unit context (which is needed here).

_Complaint (Option A) tracks email complaints, not unsubscribes.

Reference Extract:

"_BusinessUnitUnsubscribes includes SubscriberKey, BusinessUnitID, JobID, ListID, BatchID, EventDate, and EventType (Unsubscribe) for each event where a subscriber opts out of communication at the business unit level."

(Source: Salesforce Marketing Cloud SQL Data Views Guide)

Thus, D (_BusinessUnitUnsubscribes) is the correct choice for syncing unsubscribe data consolidated across all business units to an external CRM.

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 )

—

The best method is:

Use an Engagement Split in Journey A to identify engagement.

Use Update Contact Activity to update a Boolean field in a Data Extension based on the engagement result.

Later, query this updated engagement Data Extension to inject subscribers into Journey B based on their behavior.

This avoids relying directly on querying system data views and enables near-real-time, easy-to-manage segmentation.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Update Contact Activity in Journey Builder

→ "Use Update Contact Activity to update attribute values for contacts during a journey based on behaviors such as engagement."

Source: Salesforce Help – Journey Builder Engagement Split

→ "Engagement Split evaluates engagement (open, click) and can trigger updates to data for further automation."

—

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 .

BuildRowSetFromJSON() is an AMPscript function specifically designed to parse JSON payloads into usable row sets inside emails. This allows marketers to iterate through JSON objects easily and display order details dynamically in triggered transactional emails.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – AMPscript BuildRowSetFromJSON() Function

→ "BuildRowSetFromJSON parses a JSON string and creates a rowset suitable for use in AMPscript loops."

Source: Salesforce Help – Formatting JSON in Emails

→ "Use BuildRowSetFromJSON to extract and format dynamic data from JSON payloads in triggered transactional sends."

—