Salesforce Marketing-Cloud-Consultant Dumps

When new records are continuously added via API and you want to inject them into a journey, you should use Contact Evaluation set to Evaluate new records only. This ensures that only the newly added (not existing) records are evaluated for entry into the journey.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Contact Evaluation Settings in Journey Builder

→ "When using a Data Extension Entry Source, you can choose to evaluate new records only, ensuring that only fresh entries are processed."

Source: Salesforce Help – Data Extension Entry Source

→ "Select 'Evaluate new records only' to inject new rows added to the data extension into the journey."

—

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

—

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

Salesforce Campaigns are the best way for Sales Cloud users to manually create a segment of Leads and Contacts. Through Marketing Cloud Connect, Salesforce Campaigns can be used directly as an audience source in the Content Builder Send Flow, allowing quick selection and targeting without custom queries.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect and Salesforce Campaigns

→ "Salesforce Campaigns can be used as an audience for sending emails from Marketing Cloud. Campaign Members (Leads and Contacts) can be targeted directly."

Source: Salesforce Help – Send Flow and Salesforce Data

→ "When sending an email using Content Builder’s Send Flow, users can select Salesforce Campaigns as the audience source if Marketing Cloud Connect is enabled."

✅ Comprehensive and Detailed Explanation: Approval Workflows and Content Sharing Settings in Marketing Cloud allow organizations to control who can view, edit, and approve content. Approval workflows ensure that no content goes live without review. Sharing settings manage visibility across business units and roles.

❌ Why Other Options Are Incorrect:

A: Governance is important but is policy, not a technical enforcement.

C: Outside CMS integration is unnecessary when Marketing Cloud’s internal governance capabilities are sufficient.

D: Editing Role permissions alone would not enforce approval processes.

Exact Extract: Salesforce Help: Approval Rules in Content Builder

"Use Approval Workflows in Content Builder to require that users submit content for approval before publishing. You can define reviewers and assign permissions to edit or view content."

When a new user registers through the mobile app, and the ContactKey isn't immediately set, the MobilePush SDK assigns a temporary identifier (a GUID) to the device. This results in the creation of a new Contact in Marketing Cloud. Once the user's information is synced from Sales Cloud and the ContactKey is established, the device can be correctly associated. However, until this association occurs, the system treats the device as belonging to a separate, anonymous contact. ​

The correct answer is D , because:

In Salesforce Marketing Cloud's Journey Builder , a Decision Split Activity allows marketers to direct contacts down different paths based on defined attributes.

When comparing data from the entry source (Journey Data) and from additional data extensions (Contact Data or Event Data Extensions like a Transaction DE), you must configure the Decision Split to reference both Contact and Journey Data .

Salesforce documentation explains:

" Journey Data is information captured at the moment of journey entry (i.e., the fields from the entry event data extension).

Contact Data is information related to the contact stored outside the entry event, often in other data extensions linked to the Contact model.

To compare fields across these datasets inside a Decision Split, you must configure the split to use both Contact Data and Journey Data ."

(Source: Salesforce Help - Journey Builder Decision Splits Overview)

Specifically, for NTO:

Journey Data would be the birthday journey source Data Extension.

Contact Data would be the external Transaction DE containing promotional code redemption information.

Key actions required:

Use Decision Split Activity .

Configure the decision split to evaluate both Contact Data and Journey Data .

Compare the Customer Number fields between both datasets to determine if a promotion was redeemed.

Why the other options are incorrect:

❌ A. Decision Split Activity using only Contact Data :

Only using Contact Data won't allow comparison with the Journey Data (entry DE values).

❌ B. Decision Split Activity using only Journey Data :

Only using Journey Data won't allow checking against external Transaction Data Extensions.

❌ C. Einstein Split Activity :

Einstein Split uses AI to predict engagement (like open or click probability), not field comparison across datasets.

Additional official extract for clarity:

"When building decision splits that rely on both entry data and external profile attributes, ensure to select the appropriate source (Contact Data and Journey Data) to create accurate comparisons."

(Source: Salesforce Marketing Cloud Journey Builder User Guide)

Thus, the correct answer is D .

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

—

The correct answer is B , because:

In Salesforce Marketing Cloud, Reply Mail Management (RMM) processes replies to email messages and can automatically take action — such as unsubscribing a user — when specific unsubscribe keywords are detected.

Salesforce official documentation states:

" Reply Mail Management uses filtered keywords to identify unsubscribe requests. You must configure these keywords manually. If users reply with phrases not included in the filtered keyword list, they won't be unsubscribed automatically. "

(Source: Salesforce Marketing Cloud Reply Mail Management Overview)

Thus, if phrases like "take me off your list" or "opt out" are not yet added to the filtered keyword list, RMM will not recognize them as unsubscribe requests, and no action (unsubscribe) will be taken.

✅ To correct this:

You must add custom phrases such as "take me off your list" and "opt out" to the Filtered Keywords list in RMM settings.

Why the other options are wrong:

❌ A. Ensure the DNS Record Redirect is correctly configured :

DNS redirection issues affect reply routing, not keyword detection.

❌ C. Ensure the two phrases are added to the "Filtered Keywords" data extension :

There is no "Filtered Keywords" data extension. It’s a configuration inside RMM settings, not a data extension.

❌ D. Ensure "Common Misspellings" is selected as one of the Reply Filters :

"Common Misspellings" handles typos but won't automatically detect entirely new phrases unless those phrases are explicitly added.

Further reference:

"Customizing the filtered keywords list improves unsubscribe recognition. Without these custom keywords, subscriber responses will not trigger the intended actions."

(Source: Salesforce Marketing Cloud Admin Guide - Reply Mail Management Configuration)

Thus, B is the correct solution.

When configuring a sending domain for SAP (Sender Authentication Package), you need to know:

If the company allows delegation of subdomains to a third party (Marketing Cloud).

Whether they can modify the DNS entries (important for setting up SPF, DKIM, and CNAME records).

Options A and C incorrectly imply that Salesforce/Marketing Cloud will update or post files directly, but typically, DNS configuration must be done by the customer’s IT team.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Domain Delegation for Marketing Cloud

→ "Delegation of subdomains to Salesforce is often required if Marketing Cloud is to manage the domain authentication setup."

Source: Salesforce Help – Sender Authentication Package DNS Requirements

→ "Customers must be able to add and manage DNS records, including TXT, CNAME, and MX records, to complete the domain branding process."

Comprehensive and Detailed Explanation:

The correct answers are A and C.

A — If responses are not received within the configured Conversation Window (e.g., 30 mins, 1 hour), MobileConnect treats them as unrelated and sends the default response.

C — If a Next Keyword is not specified on the outbound message, MobileConnect has no instruction for how to handle a reply, so it falls back to the default keyword response.

❌ Why others are wrong:

B: The Conversation Window is based on minutes/hours, not 24 hours.

D: If a response contains "stop," it triggers an opt-out process, not a fallback default keyword response.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Conversation Window and Next Keyword Setup:

"Ensure that outbound messages include a configured Next Keyword to direct subscriber responses. Responses received outside the Conversation Window are treated as unrelated and routed to the default keyword response."

(Source: )

—

In Marketing Cloud, if multiple BUs need access to the same data (like Product Information), the best practice is to store and manage the data extension in the top-level (Parent) BU and share it with the Child BUs using Shared Data Extensions.

This avoids duplication, ensures consistency, and simplifies data management.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Shared Data Extensions

→ "Shared Data Extensions enable parent business units to share data extensions with one or more child business units for consistent access and management."

—

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

AMPscript can be used to retrieve external content, such as an RSS feed, dynamically at send time using HTTPGet().

External Content blocks in Content Builder allow you to bring in an RSS feed URL directly into an email design without writing custom AMPscript.

Dynamic Content and Personalization Strings are based on internal data extensions or profile attributes, not pulling from external real-time sources.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – External Content Blocks

→ "Use an External Content block to retrieve and display data from an external source, such as an RSS feed, at send time."

Source: Salesforce Help – AMPscript HTTP Functions

→ "Use the HTTPGet() AMPscript function to retrieve information from an external URL and display it in a message."

—

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

—

Comprehensive and Detailed Explanation:

The correct answer is C — Query Activity > Data Extension Entry Source > Journey Activities.

A Query Activity can select subscribers who haven't purchased in six months based on date logic.

The results are saved into a Data Extension.

This Data Extension is then used as the entry source into a Journey, which can orchestrate sending across multiple channels (email, SMS, push).

❌ Why others are wrong:

A: API Event is not necessary; you already have the data internally.

B: Import Activity is for external file imports; no external file mentioned.

D: Salesforce Entry Event relates to CRM records, not Data Extension queries.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Extension Entry Source:

"Use the Data Extension Entry Source to inject contacts into a journey based on criteria from a query or automation. This supports orchestrating communications across multiple channels."

(Source: )

—

An Auto-Suppression List is designed exactly for this use case. It automatically excludes specified subscribers from email sends across multiple campaigns or sender profiles. It can also be dynamically updated, such as through SQL queries and Automation Studio activities.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Auto-Suppression Lists Overview

→ "Auto-Suppression Lists automatically exclude email addresses from specific sends, business units, or sender profiles, and can be updated dynamically."

Source: Salesforce Help – Managing Suppression Lists

→ "Suppression lists are used during sending; however, Auto-Suppression Lists are configured per sender profile or business unit and maintained separately."

—

The best practice is:

Use Automation Studio to process the incoming file (import, validate, segment new customers).

Then inject the properly prepared audience into Journey Builder for decisioning, sending, and managing wait steps with Send Time Optimization.

Journey Builder is ideal for managing personalized campaigns over time, while Automation Studio is suited for heavy data processing and segmentation.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Automation Studio and Journey Builder Best Practices

→ "Use Automation Studio to prepare and transform data before injecting into Journey Builder for personalized messaging, campaign orchestration, and Send Time Optimization."

Source: Salesforce Help – Journey Builder Overview

→ "Journey Builder manages multi-step, personalized customer journeys that adapt based on contact behavior and timing."

—

Comprehensive and Detailed Explanation:

The correct answer is B — LookupRows AMPscript function.

LookupRows() can retrieve multiple records (e.g., multiple products in a cart) for a given Session ID.

It allows dynamic rendering of multiple product details for each subscriber within the email content.

It is ideal for cart abandonment where one user may have multiple products.

❌ Why others are wrong:

A: Lookup() retrieves only a single value (one row, one field) — not multiple rows.

C: Dynamic Content Block is for switching static content based on rules, not dynamically listing multiple items.

D: Enhanced Dynamic Content Block is used for more complex content switching, but LookupRows is simpler and more appropriate for abandoned cart listings.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — LookupRows AMPscript function:

"The LookupRows function returns multiple rows from a data extension where the specified column matches the specified value. Use LookupRows when you expect multiple matching rows, such as multiple items in a cart."

(Source: )

— —

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

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:

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

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

—

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

—

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

—

Since they are using Marketing Cloud Connect, the best real-time option is Salesforce Triggered Sends. When a new Contact or Lead is created in Sales Cloud (via the website sign-up form), a Triggered Send can immediately deploy the Welcome Email via Marketing Cloud.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Triggered Sends Overview

→ "Triggered Sends allow Salesforce to initiate an immediate email send from Marketing Cloud when a record meets specified conditions."

Source: Salesforce Marketing Cloud Connect Guide

→ "Use Salesforce Triggered Sends to capture and act on real-time interactions like new sign-ups or opportunities."

—

The best solution for fast, transactional emails like password resets is the Transactional Messaging API.

It is optimized for speed (near real-time delivery).

It supports notification of status via response payloads and optional callbacks.

Triggered Send Definitions are older and not as real-time or robust. Journey-based API entry methods (C and D) introduce unnecessary delays for critical transactional messaging.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Developer Guide – Transactional Messaging API Overview

→ "Transactional Messaging API provides fast, secure sending of transactional messages like order confirmations or password resets, with near real-time delivery."

Source: Salesforce Help – Transactional Messaging vs. Triggered Sends

→ "Transactional Messaging APIs are designed to deliver messages as quickly as possible, whereas classic Triggered Sends and API Event Journeys are better suited for marketing campaigns."

—

Comprehensive and Detailed Explanation:

The correct answer is A — Orders should be set up to allow injection upon update in Connect Configuration.

When setting up Salesforce Data Entry Source in Marketing Cloud Connect, you must explicitly configure whether records should inject only upon creation or also upon updates.

If injection on update is not configured, only the original create event triggers the Journey entry.

❌ Why others are wrong:

B: The associated Contact does not need to be updated — it’s the Order object that triggers the injection.

C: Synchronized Data Extensions are not used here — it’s a direct connection via Marketing Cloud Connect, not polling.

D: Even if status fields change properly, if updates are not allowed to trigger injection, no entry will occur.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Salesforce Data Entry Configuration:

"When configuring Salesforce Data Entry Sources, ensure the setting to allow journey entry on record update is enabled if updates to the record should trigger journey entry."

(Source: )

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:

The correct answer is C — Data Extract with the Tracking Extract type > File Transfer from Safehouse > File Transfer unzip > Import File.

Tracking Extract Activity pulls detailed email event data, including 'Not Sent' events, into a compressed file (.zip).

You need a File Transfer Activity to move the file from the Safehouse and unzip it.

After unzipping, Import Activity loads the extracted data into a Data Extension where queries can run.

❌ Why others are wrong:

A and B: Data Extension Extract type is for DE records, not tracking events like Not Sent.

D: Data Factory Utility is not part of the standard Automation Studio activities for these operations.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract and Automation Studio:

"Use Tracking Extract to retrieve event-level data, including Not Sent events, then use a File Transfer Activity to unzip and import the extracted data for analysis or reporting."

(Source: )

—

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

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

Salesforce enforces a 24-hour rolling limit on standard API calls.

SOAP API calls (such as updating objects) count toward this limit.

The AMPscript function CreateSalesforceObject() internally performs a Salesforce API call and is also counted toward the Salesforce daily API limits.

Login Calls and Bulk API operations have separate limit tracking and do not typically count against the standard 24-hour API limit.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – API Request Limits and Allocations

→ "API requests that create, retrieve, update, or delete records count against your daily API call limits. This includes SOAP API and REST API requests."

Source: Salesforce Developer Documentation – CreateSalesforceObject() AMPscript

→ "The CreateSalesforceObject function uses Salesforce SOAP API calls internally, and these requests count toward Salesforce API limits."

—

Tokenized Sending allows PII (such as email addresses) to stay external until send time; however, once pulled in via personalization strings, PII can still be displayed within emails.

Since Tokenized Sending relies on live API calls to an external database during sends, Salesforce Marketing Cloud's normal service-level guarantees (e.g., send speed and reliability) no longer apply because they now depend on third-party system response times.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Tokenized Sending Overview

→ "Tokenized Sending retrieves sensitive customer data at send time, reducing Marketing Cloud's data storage liability. However, if personalization strings reference retrieved fields, PII can still be displayed in the email."

Source: Salesforce Help – Tokenized Sending Limitations

→ "Marketing Cloud does not guarantee service levels for sends that rely on external Tokenized Sending lookups."

—

The most native, no-code solution would be using an Engagement Split in Journey Builder to capture customer responses (positive or negative) and, for negative responses, trigger a Case Activity to automatically create a Case record in Service Cloud.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Activities in Journey Builder

→ "Use Case Activity in Journey Builder to create a Case record in Salesforce based on customer behavior within the journey."

Source: Salesforce Help – Journey Builder Engagement Splits

→ "Engagement Split evaluates a contact’s interaction and directs them down a different path in the Journey based on their engagement."

—

—

—

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 Sender Authentication Package (SAP) includes private domain branding, dedicated IP address, and Reply Mail Management. It is ideal for brands that send at scale (like 500,000 emails monthly) and need consistent branding for deliverability and trust.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Sender Authentication Package Overview

→ "The SAP provides domain branding, dedicated IP addresses, and improved deliverability. It is recommended for customers with high volume sends who want to maintain consistent brand recognition."

Source: Salesforce Marketing Cloud Implementation Guide

→ "Brands expecting to send more than 250,000 emails per month and prioritizing branding should strongly consider SAP."

You would:

Use Salesforce Data Entry to identify the Contacts and Leads in scope.

Use SQL Query Activity to evaluate who has not opened five emails based on Data Views.

Use Task Activity to create Salesforce tasks automatically.

This path matches Option A exactly.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Salesforce Activities in Journey Builder

→ "Salesforce Activities, including Task creation, can be used to automate CRM record updates from Marketing Cloud."

Source: Salesforce Marketing Cloud Connect Guide – SQL Query Activities

→ "SQL Query Activities allow filtering and evaluation of marketing engagement data (such as opens and clicks) stored in Data Views."

—

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.

To resolve the issue of new contacts not receiving SMS messages due to missing country codes in the mobile number field, the best solution is to select 'Normalize Phone Number' in Journey settings .

Normalize Phone Number : In Journey Builder’s SMS activity settings, enabling the "Normalize Phone Number" option automatically formats phone numbers to the E.164 standard (e.g., +1 for US numbers) by appending the appropriate country code based on a specified default country (in this case, the United States). This ensures that phone numbers missing a country code are correctly formatted for SMS delivery.

Why it works :

SMS providers require phone numbers in E.164 format (e.g., +12025550123 for a US number).

If the mobile number in the Salesforce Entry Data Extension lacks the country code (e.g., 2025550123), the SMS will fail to send.

Normalizing phone numbers at the journey level corrects this issue without requiring manual updates to Salesforce records.

Why the other options are incorrect:

A. Select 'US' as the sending country in SMS activity : The sending country setting in MobileConnect determines the short code or long code used for sending, not the formatting of recipient phone numbers. It does not address missing country codes in the data.

B. Format the phone field in Salesforce as +1[phonenumber] : While manually formatting phone numbers in Salesforce to include the +1 country code would work, it requires updating all existing records and implementing validation rules for new records, which is inefficient and prone to errors compared to normalization.

D. Configure the phone field in Salesforce as US locale : Setting the phone field’s locale in Salesforce affects display formatting (e.g., (202) 555-0123) but does not automatically add the +1 country code in the E.164 format required for SMS.

Exact Extract from Salesforce Documentation:

Normalize Phone Number : "When you enable Normalize Phone Number in an SMS activity, Marketing Cloud automatically formats phone numbers to include the country code based on the selected country, ensuring compliance with E.164 standards for SMS delivery." (Source: Salesforce Help - MobileConnect SMS Activity Configuration )

E.164 Format : "SMS messages require phone numbers in E.164 format, which includes the country code (e.g., +1 for the United States). Use normalization to correct improperly formatted numbers." (Source: Salesforce Help - MobileConnect Best Practices )

A Verification Activity can check conditions (such as row count) between steps in an automation. You can configure it to send an alert if the number of imported records exceeds a threshold (like 1,000) and halt the automation, preventing the SQL query from running and updating the sendable Data Extension.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Verification Activities

→ "Verification Activities allow you to evaluate conditions during an automation. You can stop the automation or send a notification if the verification fails."

—

Comprehensive and Detailed Explanation:

The correct answer is C — _PublicationSubscriber.

The _PublicationSubscriber Data View stores the mapping between subscribers and publication lists.

This Data View contains fields like SubscriberKey, PublicationListID, and Status that can be used in queries to find active subscribers on specific publication lists.

❌ Why others are wrong:

A: _ListSubscribers relates to standard subscriber lists, not publication lists.

B: _Subscribers contains general subscriber profile data but not list membership.

D: _EnterpriseAttribute is related to Enterprise-level attributes, not publication list membership.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Views:

"_PublicationSubscriber contains information about subscribers' subscription status for publication lists."

(Source: )

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

For integrating Marketing Cloud with Sales Cloud via Marketing Cloud Connect, the API user in Marketing Cloud should have the "API User" checkbox selected. Additionally, assigning both the "Administrator" and "Marketing Cloud Administrator" roles ensures the user has the necessary permissions to facilitate the integration effectively. ​

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

✅ 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 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 answers are A and B.

A — Import Activity: To bring the latest coupon code counts into Marketing Cloud from an external system or FTP.

B — Verification Activity: To check that a data extension meets a specified condition, such as the number of records (coupon codes) not falling below a certain threshold. If it fails, the automation can notify users.

❌ Why others are wrong:

C: Data Extract Activity is for file extraction from Marketing Cloud, not real-time monitoring.

D: Filter Activity is used for segmenting subscribers, not for conditional validation.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Verification Activity:

"Verification activities check a data extension or file to validate that it meets predefined conditions, such as record count. Failure of the verification can trigger a notification."

(Source: )

—

Comprehensive and Detailed Explanation:

The correct answer is D — A Sender Authentication Package (SAP) should be used for Cloud Kicks.

SAP provides a dedicated IP, Private Domain, DKIM, and SPF alignment, critical for brand deliverability and reputation.

Since Cloud Kicks will operate with its own brand identity, even under the same parent org, setting a distinct SAP ensures inbox placement and avoids shared reputation issues.

❌ Why others are wrong:

A: NTO already has an SAP; Cloud Kicks needs its own setup.

B and C: Private Domains without full SAP (dedicated IP, DKIM, SPF) are not sufficient alone for full brand reputation management.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Sender Authentication Package Overview:

"Use the Sender Authentication Package (SAP) to configure custom sending domains, dedicated IPs, and authenticated email, ensuring maximum deliverability and brand identity."

(Source: )

—

Info Capture templates in MobileConnect are designed specifically to capture free-form, open- ended text responses from customers and save them into a Data Extension. This is ideal for surveys or open feedback loops.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Info Capture in MobileConnect

→ "The Info Capture template allows subscribers to send a text response that is captured and stored in a designated data extension."

—

Comprehensive and Detailed Explanation:

The correct answer is A — Implement two separate Marketing Cloud instances.

To fully segregate test data (sandbox) from production data with zero risk of mixing, separate instances are necessary.

Business Units (BU) would still share the same All Subscribers list — so using BUs alone is not sufficient for strict separation.

❌ Why others are wrong:

B and D: Filtering doesn’t prevent accidental cross-contamination.

C: Business Units are logical partitions, but not physical — they still share the same SubscriberKey space at the instance level.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Sandbox vs Production in Marketing Cloud:

"For true separation of test and production data in Marketing Cloud, separate instances are required. Business Units do not guarantee complete data segregation."

(Source: )

—