Salesforce Marketing-Cloud-Consultant - Salesforce Certified Marketing Cloud ConsultantSFMCExam (SP25)

✅Comprehensive and Detailed Explanation:

Option B uses a Salesforce CRM Date-Based Entry Source in Journey Builder, which is designed exactly for these kinds of time-based communications triggered off of Salesforce object records (such as Appointment__c). This entry source allows Marketing Cloud to initiate a Journey X days before a date field, and execute native Salesforce activities (such as updating the record when the message is sent).

You can enter contacts into a journey before or after a specific date in a CRM object.

You can configure the journey to start at a specific time of day, such as 10:00 AM.

You can use the Salesforce Update Contact Activity within the Journey to update fields on the original record.

Exact Extract from Salesforce Documentation:

📄Source: Salesforce Help - Use a Salesforce Data Entry Source in Journey Builder

"Date-Based Entry: Add contacts to a journey based on a date attribute in the Salesforce object. You can configure contacts to enter the journey before, after, or on the specified date and time."

"The Salesforce Update Contact Activity updates a record in your connected Salesforce account. For example, use the activity to change the status of a lead or add a note to a contact after the contact receives an email."

📄Source: Marketing Cloud Connect Implementation Guide

"With Marketing Cloud Connect, you can use Salesforce Data (such as Contacts or Custom Objects) as the entry source in Journey Builder. This allows for triggering journeys directly from CRM records with date-based logic."

❌Why Other Options Are Incorrect – Backed by Official Extracts:

A – Invalid due to write-back to CRM limitations

"Synchronized Data Extensions are read-only copies of Salesforce CRM data. They can be used to segment and send, but not updated directly from Marketing Cloud."

— Source: Salesforce Help – Synchronized Data Extensions

C – Not ideal due to manual AMPscript update workaround

"AMPscript can interact with data extensions, but using it to write back to Salesforce CRM requires custom API integration and is not recommended when using Marketing Cloud Connect."

D – Data Extension entry source doesn't natively update CRM records

"Journeys triggered from a data extension cannot natively update Salesforce CRM unless custom API calls are made through custom activities or server-side scripts."

Comprehensive and Detailed Explanation:

The correct answer is C — Data Extract Activity.

Specifically, a Tracking Extract (a type of Data Extract) can pull all Not Sent events within the past 24 hours.

After extracting, the data can be moved to SFTP via a File Transfer Activity.

❌Why others are wrong:

A: Report Definition Activity runs standard reports — it doesn't create extract files for automation.

B: SendLog Extract extracts SendLog DEs, not Not Sent tracking events.

D: SQL Query Activity manipulates DE data but doesn't extract system event data directly.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Extract Activity Overview:

"Data Extract Activities allow you to retrieve tracking event data such as Sends, Deliveries, Bounces, Not Sent, Opens, Clicks, etc. Use a Tracking Extract type to pull these events into a file for export."

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

—

Comprehensive Explanation:

Profile Attributes in MobileConnect are used to store subscriber-specific information, such as first name, last name, or preferences. These attributes can be utilized to personalize SMS messages, enhancing engagement and relevance.​

Comprehensive and Detailed Explanation:

The correct answer is B — Use an info capture message template to capture the response.

Info Capture templates are designed specifically to collect information via SMS (like survey responses, open text feedback, or registrations).

MobileConnect automatically writes the captured information to a selected Data Extension when using this template type.

❌Why others are wrong:

A: Text-response messages are simple replies and do not auto-capture or save open-ended feedback to Data Extensions.

C: Outbound templates are designed for sending messages, not capturing replies.

D: Vote/survey templates are for fixed response options (e.g., 1 for Yes, 2 for No) — not open-ended text.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Info Capture Template:

"Use an Info Capture message template to collect and store SMS responses in a designated data extension."

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

—

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

—

If Email Address is used as the Subscriber Key instead of ContactID or LeadID, Salesforce cannot map tracking data back to the CRM records, because Marketing Cloud Connect requires a direct relationship to a Lead, Contact, or User ID.

If Individual Level Tracking is not enabled in the Marketing Cloud Connector settings, tracking information is not pushed back to individual Contact or Lead records.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect Tracking

→ "Marketing Cloud Connect tracking requires that Subscriber Key matches ContactID, LeadID, or UserID. If Email Address is used instead, tracking cannot be attributed."

Source: Salesforce Help – Individual Email Results Tracking

→ "Individual Level Tracking must be selected to enable tracking data writeback at the individual record level."

—

Because of the complex relationships (multiple objects and property matches), it's best to use Automation Studio to:

Query and flatten the relational data into a single personalized Data Extension.

Then use Journey Builder to send based on that prepared data.

This approach avoids heavy personalization scripting inside emails (which would reduce performance) and makes the sends more efficient.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Journey Data Preparation Best Practices

→ "For complex relationships and personalization requirements, prepare the data with Automation Studio before injecting into Journey Builder."

Source: Salesforce Help – Personalization in Journey Emails

→ "Avoid heavy personalization logic inside the email. Prepare the personalization using query activities beforehand to ensure send performance."

The process requires refreshing the Filtered List (to ensure it captures contacts with upcoming birthdays) and then using the Outbound Send activity configured in MobileConnect to deliver the SMS. “Outbound Send” is the correct action in MobileConnect, not just a basic "Send SMS."

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – MobileConnect Filtered Lists and Sends

→ "Use a Refresh Mobile Filtered List Activity in Automation Studio to refresh mobile filtered lists automatically before performing an Outbound Message Send."

Source: Salesforce Help – MobileConnect Outbound Messaging

→ "Outbound Messages are scheduled SMS sends managed via Automation Studio or MobileConnect."

—