Pass the Salesforce Marketing Cloud Consultant CRT-550 Questions and answers with ExamsMirror

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 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 )

—

_Send Data Views are built-in system tables in Marketing Cloud that capture detailed tracking data across multiple channels including Email, SMS, and Push. They can be queried via SQL Query Activities to extract insights about sends, clicks, opens, bounces, and more.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Views in Marketing Cloud

→ "_Send Data Views provide detailed tracking data for sends across all messaging channels, including Email, Mobile, and Push. Query these views for advanced reporting."

—

When disconnecting and reconnecting instances in a Multi-Org setup, it’s mandatory to first remove all user mappings, attribute mappings, and tracking subscriptions associated with the sandbox. This is necessary to cleanly connect the new (production) instance without conflicts.

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Disconnect and Reconnect Marketing Cloud Connect Accounts→ "Before connecting a new Salesforce org to Marketing Cloud, remove existing user mappings, attribute mappings, and tracking subscriptions associated with the current org."

Source: Marketing Cloud Multi-Org Setup Guide→ "In a Multi-Org configuration, disconnecting an org requires removing all dependent mappings and synchronized objects before connecting a new Salesforce org."

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

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

Comprehensive and Detailed Explanation:

The correct answer is D — Build rules before uploading the respective content.

Best practice is to define dynamic content rules first (e.g., “Points < 1000: Content A; Points 1000–5000: Content B”) before building and uploading the content blocks.

This makes setting up Dynamic Content Blocks in Content Builder easier and more structured.

❌ Why others are wrong:

A: Custom Lists are older Email Studio concepts, not relevant to dynamic content best practices in Content Builder.

B: Standardizing field names is good practice, but not directly tied to dynamic content rule building.

C: Synchronized DEs are for Salesforce CRM data, which is not mentioned here.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Dynamic Content Setup:

"Create rules for dynamic content before associating the respective content assets to ensure correct audience targeting within the email template."

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

—

✅ Comprehensive and Detailed Explanation: An Auto-Suppression List ensures that Marketing Cloud automatically suppresses email sends to customers who have opted out, without manual effort. It is the most efficient and reliable tool to prevent emails being sent to customers who have opted-out — especially during data migrations or imports.

❌ Why Other Options Are Incorrect:

A: Exclusion Scripts are used for dynamic in-send exclusions but are complex and not suitable for static opt-out enforcement.

C: Suppression Lists are manual and need to be selected during each send — riskier.

D: Exclusion Lists are built at the send definition level, not automatically across all sends.

Exact Extract: Salesforce Help: Auto-Suppression Lists

"Auto-Suppression Lists automatically exclude subscribers from email sends across all send types in Marketing Cloud."

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