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

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:

This is a classic transactional use case involving multiple channels: if the password reset email fails to send, the system must fallback to SMS delivery.

The best-practice solution is to:

Use a Transactional Send API for password reset emails.

Use the Event Notification Service (ENS) to monitor delivery or bounce events in near real-time.

Based on failure status, trigger an API call to initiate an SMS message.

D is the only option that uses Salesforce’s native ENS and API infrastructure for near real-time failure handling, which meets the requirement for “timely delivery.”

❌ Why Other Options Are Incorrect:

A. The Not Sent data extract is not real-time and is typically processed in batch — not suited for password resets that require instant fallback.

B. Engagement Splits (e.g., link clicked) are not ideal for determining whether an email was delivered or not. Plus, password resets don’t rely on email clicks — they’re more about deliverability.

C. API responses for triggered email sends do not reflect actual delivery success or failure — they only reflect submission status. You need ENS to monitor actual send results.

Exact Extracts from Salesforce Documentation:

Salesforce Event Notification Service (ENS): "ENS sends near-real-time email delivery, bounce, or click events to external systems so you can monitor transactional sends and take automated actions (e.g., triggering an SMS)."

— Source: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/ens-overview.html

Transactional Email via API: "Use the Transactional Messaging API to send password resets or other 1-to-1 emails. Integrate with Event Notification Service to determine the outcome of each message."

— Source: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/sendTransactionalEmail.html

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

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 Explanation:

In Salesforce Marketing Cloud, applying a Retention Policy to a data extension helps manage data storage by automatically deleting records after a specified period.​

Option B: By deleting data older than twelve months, NTO ensures that only relevant data remains. Subsequently, configuring a Retention Policy via Contact Builder will automate the deletion of records beyond the desired retention period moving forward.​

Option D: Creating a new data extension with a predefined Retention Policy is a proactive approach. This ensures that only data within the desired retention period is stored, and it avoids potential issues with applying retention policies to existing data extensions that have exceeded certain thresholds.​

Journey Data is the data that is captured at the time of entry into the journey — it’s a snapshot of the specific data related to that specific interaction (such as the specific tent purchased).

Because customers can have multiple tent purchases, you need to make decisions based on the data specific to that journey entry (not the general contact record), which is Journey Data.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Journey Builder Decision Splits

→ "Use Journey Data to evaluate information captured at the time a contact entered the journey, ideal for handling multiple purchases or time-specific entries."

Source: Salesforce Help – Journey Data vs Contact Data

→ "Journey Data is dynamic and tied to a specific journey instance. Use Journey Data when evaluating data related to a specific event or purchase."

—

The correct personalization string to provide a "View as Webpage" link in an email is %%view_email_url%%. When this string is placed inside the href attribute of a hyperlink, Marketing Cloud automatically generates a URL to a hosted version of the email content.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Personalization Strings

→ "%%view_email_url%% – This personalization string inserts a link to view the email as a webpage. Typically used for the 'View Online' functionality in email templates."

Source: Salesforce Marketing Cloud Email Studio Guide

→ "Use %%view_email_url%% within your hyperlink to allow recipients to view the message as a webpage."

The most common cause for not seeing or syncing Sales Cloud objects in Contact Builder after a successful connection is incorrect permission settings. Both the Salesforce CRM user and the Marketing Cloud API User must have specific permissions (like API Enabled, Modify All Data, View All Data, and Marketing Cloud Connected App permissions).

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect User Permissions

→ "Ensure that the Salesforce user and Marketing Cloud API user have the correct permissions to sync data objects and access CRM data from Contact Builder."

Source: Marketing Cloud Connect Implementation Guide

→ "Proper object permissions and field-level access are required for synchronized CRM objects to appear in Contact Builder."

—

The correct answer is B, because:

Salesforce Marketing Cloud uses a Sender Authentication Package (SAP) to establish proper authentication (including setting up DNS entries for SPF, DKIM, and DMARC) for email sending domains.

When NTO wants to send emails from a new domain (comms.nto.com.au), they would need a new SAP to configure authentication correctly for that domain — this ensures deliverability, maintains sender reputation, and complies with anti-spam regulations.

Salesforce official documentation specifies:

"Sender Authentication Package (SAP) includes branding the sending domain, setting up dedicated IP addresses, and configuring authentication protocols like SPF, DKIM, and DMARC.

If you want to send emails from a different domain, you must purchase an additional SAP to configure and authenticate the new sending domain."

(Source: Salesforce Marketing Cloud Sender Authentication Package Guide)

Important SAP Components:

Custom domain for sending (branded domain).

Authenticated email setup (SPF/DKIM/DMARC).

Private tracking domain.

Dedicated subdomain.

Why the other options are incorrect:

❌ A. An additional IP address:

A new IP is not required just because you have a new domain. IPs are more about volume and reputation needs, not domain setup itself.

❌ C. An additional private domain:

A private domain refers to a tracking domain used for link redirection, not sending domain authentication itself.

❌ D. Register the new domain in Setup > From Address Management:

From Address Management is for allowing or restricting sender addresses but does not authenticate the domain for sending.

Additional Salesforce extract:

"When sending from a new domain that is not covered under an existing SAP, you must purchase and implement a new Sender Authentication Package to maintain deliverability and compliance standards."

(Source: Salesforce Marketing Cloud Deliverability Best Practices)

Thus, B is the correct and required action.

Comprehensive and Detailed Explanation:

The correct answer is B — Journey Builder.

Journey Builder is ideal for multi-step campaigns like sending a follow-up or reminder after the original message.

To send at the subscriber's optimized send time (OST), Journey Builder supports Einstein Send Time Optimization (STO).

A reminder email can be scheduled exactly 3 days after the initial send with dynamic optimization for each subscriber.

❌ Why others are wrong:

A: Interaction Builder is not used for sending emails; it's part of Interaction Studio (Personalization).

C: Automation Studio can schedule emails but does not support STO or simple "wait 3 days then send" logic easily.

D: Combining Automation Studio and Journey Builder unnecessarily complicates the setup.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder Overview:

"Journey Builder is designed for sending messages based on time-based or behavioral events, including sending follow-ups at optimized times using Einstein Send Time Optimization."

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

—

To filter records entering a journey based on an updated status field (“shipped”), the marketer should use:

An Entry Source Filter to limit which contacts actually enter the journey at the point of entry (e.g., only those whose order status is 'shipped' today).

An SQL Query to preprocess or segment records within a Data Extension before injecting them into the journey.

Filter Activity is used inside Automation Studio (not at the journey entry point), and Decision Splits occur after entry — not before.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Entry Source Filters

→ "An entry source filter defines criteria that records must meet before entering a journey."

Source: Salesforce Help – SQL Query Activities

→ "Use SQL Query Activities to select, transform, and filter data from one or more data extensions."

—