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

To enable sending emails from a new domain (comms.nto.com.au) for Australian customers without impacting deliverability, Northern Trail Outfitters (NTO) must implement an additional Sender Authentication Package (SAP).

Sender Authentication Package (SAP): An SAP is a Marketing Cloud feature that authenticates a custom sending domain (e.g., comms.nto.com.au) to ensure emails are sent from a verified domain, improving deliverability and brand trust. It includes:

DomainKeys Identified Mail (DKIM): Signs emails to verify the sender’s identity.

Sender Policy Framework (SPF): Validates the sender’s IP address.

Domain-based Message Authentication, Reporting, and Conformance (DMARC): Enforces authentication policies to prevent spoofing.

Why it’s needed:

Using a new domain without proper authentication risks emails being marked as spam or rejected by email providers, impacting deliverability.

An SAP ensures that the new domain (comms.nto.com.au) is fully authenticated and aligned with email best practices, maintaining NTO’s sender reputation.

Implementation: NTO must purchase an additional SAP for the new domain, configure DNS records (DKIM, SPF, DMARC), and associate the domain with their Marketing Cloud account.

Why the other options are incorrect:

B. An additional IP address: A new IP address is not required for sending from a new domain. IPs are tied to the sending infrastructure, not the domain. Using a new domain with an existing IP is standard practice, provided the domain is authenticated via SAP.

C. An additional private domain: A private domain in Marketing Cloud is used for link wrapping and image hosting, not for sending emails. It does not address sender authentication or deliverability for the From address.

D. Register the new domain in Setup’s From Address Management: While registering the domain in From Address Management is a step in configuring the sending domain, it alone does not provide the full authentication (DKIM, SPF, DMARC) required to maintain deliverability. An SAP is needed to complete the setup.

Exact Extract from Salesforce Documentation:

Sender Authentication Package: "A Sender Authentication Package (SAP) authenticates a custom domain for sending emails, ensuring compliance with SPF, DKIM, and DMARC standards to maximize deliverability and protect your brand reputation."(Source: Salesforce Help - Sender Authentication Package)

Domain Setup for Deliverability: "To send emails from a new domain without impacting deliverability, configure a Sender Authentication Package to authenticate the domain and update DNS records for SPF, DKIM, and DMARC."(Source: Salesforce Help - Email Deliverability Best Practices)

Comprehensive and Detailed Explanation:

The correct answer is A — Event Notification Service (ENS).

ENS allows real-time event delivery for important email metrics like Sent, Delivered, Not Sent, Bounced, Opened, and Clicked.

It uses an HTTP callback mechanism to push notifications to an external system within seconds of the event happening.

❌ Why others are wrong:

B: Platform Events API is for Salesforce Core, not directly tied to Marketing Cloud events.

C: Data View Exports happen on a schedule, not real-time.

D: Data Retrieves pull data but require manual or automated fetching — not event-driven.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Event Notification Service Overview:

"Use Event Notification Service (ENS) to receive near-real-time notifications for message events like Sent, Not Sent, Delivered, etc., delivered to a designated endpoint."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc-transactional-api-event-notifications.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is C — Use Synchronized Data Extensions on the Case Object with a Boolean filter on the Contact Me field.

With Marketing Cloud Connect, the Case object can be synchronized into Marketing Cloud.

You can apply filters based on fields like "Contact Me = True" directly within Journey Builder or Automation Studio without manually importing reports.

❌ Why others are wrong:

A: Journey Builder doesn't handle direct data imports from Service Cloud.

B: Manual imports and Filter Activities are unnecessary when synchronized data is available.

D: Import Wizard processes are manual and not scalable for ongoing automated campaigns.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Synchronized Data Extensions:

"Synchronized Data Extensions allow you to bring Salesforce object data (such as Cases) into Marketing Cloud for use in segmentation, filtering, and journeys without manual imports."

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

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:

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 )

—

Comprehensive and Detailed Explanation:

The correct answer is B — Use Tracking Extract, File Transfer, and Import activities from Automation Studio to inject the subscribers into a data extension used as an Entry Source by Journey Builder.

Tracking Extract Activity allows the extraction of bounced or held subscribers’ data (bounce reasons like "Held").

File Transfer Activity moves the extracted file into the Import directory.

Import Activity loads the file into a Data Extension, which can then be used as the entry source for a re-engagement journey via SMS.

❌ Why others are wrong:

A: SQL Query only works if the data is already in a Data Extension; Held status bounce data typically resides in Tracking Extracts.

C: CloudPages Entry Source is incorrect — you want an automated process for SMS.

D: API Event would require custom API calls, but there's no mention of development resources.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract Activity:

"Use a Tracking Extract Activity to pull tracking data, such as bounces or held status, into a file that can be imported into a data extension for use in journeys or reports."

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

—

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 )

—

This requirement involves:

File Drop Automation to start automatically when the web analytics file arrives.

Import File Activity to bring the file into Marketing Cloud.

Verification Activity to check that the file is not empty before continuing.

Query Activity for file one (web analytics + customer reference join) and file two (5-day delay DE usage).

Then Data Extension Entry to push qualified customers into the journey.

This matches the flow outlined in Option B exactly.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – File Drop Automations

→ "Use a File Drop automation to trigger an automation when a file is dropped on your Enhanced FTP server."

Source: Salesforce Help – Verification Activity

→ "The Verification Activity checks conditions before continuing an automation. For example, you can verify if a data extension has at least one record."

Source: Salesforce Help – Automation Studio Activities

→ "Query Activities allow you to join, filter, and transform data between data extensions before sending contacts into Journeys."

The best solution is to use a Triggered Send linked to a Triggered Send Data Extension. The developer can configure the API to insert data into the TSDE, and Marketing Cloud automatically sends the appropriate email without further developer involvement. Creative changes can be managed easily through Content Builder by marketers.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Triggered Sends

→ "Triggered Sends enable near real-time email sending when an action occurs, using Triggered Send Data Extensions to personalize emails dynamically."

Source: Salesforce Developer Documentation – TriggeredSendDefinition

→ "Triggered Sends can be managed independently of API calls, allowing marketing teams to control email creative updates."

—

A Multi-Step Journey in Journey Builder is best suited to handle dynamic behaviors like:

Sending a series of emails.

Evaluating engagement (opens, clicks).

Removing subscribers from the journey if engagement criteria are met.

Data Extension/Automation entry source allows for automated injection of contacts based on updated records (like non-engagers).

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Journey Builder Multi-Step Journeys

→ "Multi-Step Journeys allow you to send multiple communications, wait for engagement, and adjust the journey path based on subscriber behavior."

—