Free Practice Questions for Salesforce Marketing-Cloud-Consultant Exam

✅ Comprehensive and Detailed Explanation: An Auto-Suppression List is specifically designed to automatically exclude specific email addresses or Subscriber Keys from being sent emails in Marketing Cloud. In this case, since the list of competitors' email addresses is static and curated, populating an Auto-Suppression List with these known addresses ensures that no emails are sent to them without requiring manual intervention.

❌ Why Other Options Are Incorrect:

A: Using Subscriber Keys would require guaranteed mapping, but email address is the direct data available here.

B: Queries require manual maintenance and are not an automatic suppression mechanism.

C: Exclusion Lists typically apply to one send definition or journey; Auto-Suppression Lists apply globally across all sends.

Exact Extract: Salesforce Help: Auto-Suppression Lists

"An auto-suppression list prevents email sends to specific subscribers globally, based on Subscriber Key or Email Address."

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

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 )

For a simple segmentation strategy, using a List model combined with Groups (filtered or random) is the easiest approach. Lists are simpler than Data Extensions, require less setup, and Groups allow basic segmentation directly in Email Studio or Journey Builder for Single Send Journeys.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Lists and Groups Overview

→ "Lists are ideal for marketers who need simple audience management. Groups (filtered or random) can be used for segmentation without advanced data modeling."

Source: Salesforce Help – Single Send Journeys

→ "Use Single Send Journeys with Groups to deliver a quick, straightforward email send without complex segmentation logic."

—

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

—

In Marketing Cloud, using Email Address as the Subscriber Key can lead to issues with tracking subscriber preferences, especially when integrating with Salesforce via Marketing Cloud Connect. If the previous send (from the external system) used Email Address as the Subscriber Key, it might not have correctly updated the subscriber's status in the All Subscribers list. Consequently, when MCC sent the email, it treated the subscriber as active, resulting in the email being sent despite the prior unsubscribe. ​

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 )

—

When using Marketing Cloud Connect, sending from Email Studio requires that sends use Data Extensions placed inside the "Salesforce Data Extensions" folder. This folder ensures proper syncing of tracking data back to Sales Cloud.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Data Extensions

→ "For sends intended to sync tracking data back to Sales Cloud, you must place the Sendable Data Extensions into the Salesforce Data Extensions folder."

Source: Salesforce Marketing Cloud Connect Implementation Guide

→ "Data Extensions used for Salesforce-connected sends must be stored under Salesforce Data Extensions."

—

Comprehensive and Detailed Explanation:

The correct answer is B — Salesforce Data Entry Source on the Contact Object.

The Salesforce Data Entry Source allows you to trigger journeys based on new or updated Salesforce records.

Since you are trying to trigger based on new contacts (and Contacts are tied to Accounts in B2B), you would configure the journey to listen for Contact creation or update events.

❌ Why others are wrong:

A: Salesforce Campaign Entry Source is tied to Campaign Members, not Contacts.

C: Salesforce Data Entry Source on Account Object isn’t typically used to drive Contact-specific Journeys — Contacts should be the focus.

D: Welcome Email Configuration is not relevant for Journey Builder — it’s for basic email sends.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Salesforce Data Entry Source:

"Use Salesforce Data Entry Sources to start a journey when records on standard or custom Salesforce objects like Contacts, Leads, or Opportunities are created or updated."

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

—