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

Comprehensive and Detailed Explanation:

The correct answer is D — Contact Data using Synchronized Data Sources.

Synchronized Data Sources (via Marketing Cloud Connect) bring Salesforce CRM data into Marketing Cloud in near real-time (every 15 minutes minimum sync).

Contact Data allows access to the latest information related to the contact during the Journey for Decision Splits and personalization.

This setup ensures journeys react dynamically to CRM updates without waiting for a separate file import.

❌ Why others are wrong:

A: Journey Data is static — it does not update after the contact enters the journey unless using Contact Data.

B: Profile Attributes are old data model elements, not suitable for connected real-time CRM data.

C: CRM Report Import is batch-based and not truly near real-time.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Synchronized Data Sources Overview:

"Synchronized Data Sources allow Marketing Cloud to access near real-time CRM data, synchronized automatically at intervals (minimum every 15 minutes). You can use Synchronized Data with Contact Data in journeys and decision splits."

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

—

The Sender Authentication Package (SAP) includes private domain branding, dedicated IP address, and Reply Mail Management. It is ideal for brands that send at scale (like 500,000 emails monthly) and need consistent branding for deliverability and trust.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Sender Authentication Package Overview

→ "The SAP provides domain branding, dedicated IP addresses, and improved deliverability. It is recommended for customers with high volume sends who want to maintain consistent brand recognition."

Source: Salesforce Marketing Cloud Implementation Guide

→ "Brands expecting to send more than 250,000 emails per month and prioritizing branding should strongly consider SAP."

To properly log values, the AMPscript variable names must match the field names in the Send Log (A).

Additionally, Send Logging must be configured and enabled during the send setup to ensure data is captured into the log (C).

Simply linking a Send Log to an Attribute Group (B) is irrelevant to Send Logging. WriteToLog() (D) is used mainly for server-side debug logging, not for populating Send Logs.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Send Logging Overview

→ "To log values to the Send Log, AMPscript variable names must exactly match the corresponding field names in the log, and logging must be enabled during the send process."

Source: Salesforce Help – AMPscript Functions (WriteToLog)

→ "WriteToLog() is primarily used for troubleshooting and development, not for writing data to the Send Log."

—

Comprehensive and Detailed Explanation:

The correct answer is B — Request SSH key authentication to be enabled for the FTP user and create an SSH Key in Key Management.

SSH Key authentication allows secure, passwordless connection to the Enhanced FTP server.

It eliminates the need for password rotation, thus avoiding manual updates every 90 days while still maintaining security.

SSH keys are managed within Marketing Cloud’s Key Management.

❌ Why others are wrong:

A: SAML SSO is for user login to Salesforce/Marketing Cloud apps, not for FTP authentication.

C: ‘Exclude FTP Users from Password Expiration’ is not available for standard Enhanced FTP users (it’s only for system user accounts under certain conditions).

D: SFTP is already in place through Enhanced FTP; the issue is not switching protocols but eliminating password dependency.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Enhanced FTP Authentication:

"To avoid password expiration impacting file transfers, request SSH Key Authentication to be enabled for the Enhanced FTP user. SSH keys allow passwordless authentication for secure automation."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_enhanced_ftp.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.

Einstein Engagement Frequency analyzes subscriber engagement and determines optimal send frequencies. By querying the Einstein Engagement Frequency data extension, you can identify subscribers who have received emails within the past 14 days and exclude them from the current send, ensuring compliance with the desired frequency cap. ​ CloudKettle

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

—

✅ Comprehensive and Detailed Explanation: A Send Log captures detailed send-time information such as which email was sent, to which address, and when. You can customize a Send Log to record additional fields like email address, subscriber key, campaign name, etc. This meets the requirement for tracking exactly which email address received which email .

❌ Why Other Options Are Incorrect:

A: The Recent Email Send Report shows aggregate send information but doesn't track individual addresses dynamically.

B: Data Views store general event tracking (open, click) but not direct customizable fields like Send Log does.

D: Tracking Extracts provide bulk tracking data but are not customizable for specific needs like this.

Exact Extract: Salesforce Help: Send Logs Overview

"Send Logs record information about the subscribers you send messages to, and allow you to track what content was sent to each subscriber."

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