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

Comprehensive and Detailed Explanation:

The correct answer is D — Use a Data Extension Entry Source with an applied filter based on recent member activity.

Using a Data Extension Entry Source allows direct filtering based on attributes like “recent activity” at the time of journey configuration.

This method efficiently filters at entry without requiring separate automation processes or manual queries.

❌ Why others are wrong:

A: Import Activity would require manual or scheduled imports; unnecessary here.

B: Query Activity creates additional complexity; Journey Builder filtering is more efficient.

C: Contact Data Entry Source is used when leveraging Attribute Groups, but it’s more complex than necessary for simple recent activity checks.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder Entry Sources:

"A Data Extension Entry Source can include filter criteria to ensure only qualifying contacts enter the journey without requiring pre-segmentation."

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

The simplest and most efficient method to report on the number of Contacts is to schedule the built-in "Contacts Counts" Standard Report. This report summarizes the total number of Contacts and can be scheduled for automatic email delivery to stakeholders like the CMO.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Contact Count Standard Report

→ "The Contacts Counts report shows the number of Contacts in the account and can be scheduled to email automatically on a recurring basis."

Source: Salesforce Help – Standard Reports Overview

→ "Use Standard Reports like Contact Counts to quickly view and schedule basic statistics without needing custom queries or Automation Studio."

—

With a Sender Authentication Package (SAP) and dedicated IP address, maintaining a minimum volume (around 250,000 messages/month) is critical to building and maintaining a healthy sender reputation. If the volume drops too low, deliverability could be negatively affected.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Dedicated IP Warming and Maintenance

→ "To maintain a strong sending reputation on a dedicated IP address, customers should send a minimum of 250,000 emails per month."

Source: Salesforce Marketing Cloud Implementation Guide – Sender Authentication Package

→ "Dedicated IPs provided with SAP require consistent, high-volume sending for optimal performance."

—

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

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

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

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

Comprehensive and Detailed Explanation:

The correct answer is A — Disconnect / Refresh / Reconnect / Authenticate / Synchronize.

Before refreshing a Salesforce sandbox that is connected to Marketing Cloud, you must first Disconnect the integration. Otherwise, the link between MC and Salesforce could break.

Then, Refresh the Salesforce sandbox (refreshing rebuilds a copy of the production org).

After the refresh, you Reconnect Marketing Cloud to the refreshed Salesforce sandbox.

Authenticate again (OAuth) to ensure permissions and tokens are up-to-date.

Finally, Synchronize objects and data.

❌ Why others are wrong:

Other options either refresh before disconnecting or sync/authenticate in the wrong order, which could cause major connection errors.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Refresh Salesforce Sandbox with Marketing Cloud Connect:

"Disconnect Marketing Cloud from the Salesforce Sandbox before refreshing it. After refreshing, reconnect, authenticate, and synchronize your settings and data extensions."

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

—

When disconnecting an existing Salesforce org in a Multi-Org Marketing Cloud setup, you must manually remove all user mappings, attribute mappings, and tracking subscriptions tied to the original instance before connecting a new org. This ensures a clean reconnection without conflicts.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Multi-Org Setup for Marketing Cloud Connect

→ "Before disconnecting an org in a Multi-Org setup, manually remove user mappings, attribute mappings, and tracking subscriptions to prevent data conflicts."

—

Each File Drop Automation must monitor a unique directory, and that directory cannot be shared across multiple File Drop Automations (B).

The file trigger directory must be inside the import folder structure for Enhanced FTP (C).

Using an external FTP site is not supported for File Drop Automations — it must be Salesforce's Enhanced FTP. The limitation on the number of triggers is not five; it's based on system and licensing limits.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – File Drop Automation Requirements

→ "Each File Drop Automation must have its own unique directory. The directory must reside within the Import directory."

Source: Salesforce Help – Enhanced FTP File Drop Automations

→ "File Drop Automations require files to be dropped into a directory under the Import folder on Marketing Cloud’s Enhanced FTP."

✅ Comprehensive and Detailed Explanation:

A (Use Data Designer in Contact Builder) is necessary because relationships must be created between data extensions in Contact Builder for Journey Builder to access and evaluate cross-data attributes.

B (Utilize Entry Data on a Decision Split) is required because Decision Splits use Entry Data or Contact Data attributes (made available via the relationships created).

❌ Why Others Are Incorrect:

C: Data Relationships in Email Studio are for segmentation and sends, not Decision Splits in Journey Builder.

D: Automation Studio updates are irrelevant to Decision Splits in real-time journey flows.

Exact Extract:

Salesforce Help: Data Designer - Contact Builder

"Use Data Designer in Contact Builder to define relationships between data extensions. These relationships allow Journey Builder to evaluate contact data across multiple extensions when using activities such as Decision Splits."

Salesforce Help: Journey Builder Decision Split

"Decision Splits evaluate attributes from the entry event data or related data extensions defined in Contact Builder."

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