Free Practice Questions for Salesforce Marketing-Cloud-Consultant Exam

You would:

Use Salesforce Data Entry to identify the Contacts and Leads in scope.

Use SQL Query Activity to evaluate who has not opened five emails based on Data Views.

Use Task Activity to create Salesforce tasks automatically.

This path matches Option A exactly.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Activities in Journey Builder

→ "Salesforce Activities, including Task creation, can be used to automate CRM record updates from Marketing Cloud."

Source: Salesforce Marketing Cloud Connect Guide – SQL Query Activities

→ "SQL Query Activities allow filtering and evaluation of marketing engagement data (such as opens and clicks) stored in Data Views."

—

A File Drop Automation triggers automatically when a file is placed in a specified SFTP folder, allowing immediate processing. After importing the data, a SQL Query can segment the data based on specific criteria, preparing it for entry into a journey. ​

✅ Comprehensive and Detailed Explanation: The Blockout Window in MobileConnect prevents SMS messages from being sent during specified hours, automatically holding messages for delivery until after the blockout period or discarding them based on configuration. It directly addresses the need to prevent delivery during nighttime hours.

❌ Why Other Options Are Incorrect:

A and B: These are manual data management activities, not real-time or dynamic enough for Journey-based sends.

C: Journey Goals relate to achieving a Journey outcome, not message send timing.

Exact Extract: Salesforce Help: MobileConnect Blockout Windows

"Use Blockout Windows to prevent SMS message delivery during certain times. Blocked messages can be discarded or queued for later delivery."

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

Comprehensive and Detailed Explanation:

The correct answer is D — Use a Data Extension Entry Source with an applied filter based on recent member activity.

Using a Data Extension Entry Source allows direct filtering based on attributes like “recent activity” at the time of journey configuration.

This method efficiently filters at entry without requiring separate automation processes or manual queries.

❌ Why others are wrong:

A: Import Activity would require manual or scheduled imports; unnecessary here.

B: Query Activity creates additional complexity; Journey Builder filtering is more efficient.

C: Contact Data Entry Source is used when leveraging Attribute Groups, but it’s more complex than necessary for simple recent activity checks.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder Entry Sources:

"A Data Extension Entry Source can include filter criteria to ensure only qualifying contacts enter the journey without requiring pre-segmentation."

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

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

—

✅ 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 A — Data Filters.

Data Filters provide a drag-and-drop, no-code way to segment audiences based on profile attributes or behavior.

They allow marketing users without SQL or AMPscript knowledge to build audiences directly in Email Studio.

❌ Why others are wrong:

B: Attribute Groups are used for mapping relationships between data, not for audience segmentation.

C: Publication Lists manage opt-in/out preferences, not audience segmentation.

D: Query Activities require SQL coding, which the team lacks experience with.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Filters Overview:

"Data Filters allow users to segment data extensions based on attribute values and behavior using a simple drag-and-drop interface, without the need for coding."

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

—

The correct answers are A, C, and D , because:

When planning the number of Business Units (BUs) for a Marketing Cloud Enterprise 2.0 account, Salesforce recommends evaluating organizational structure and data/content needs carefully. 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 are A , C , and D .

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 .

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.