CRT-550 Salesforce Certified Marketing Cloud Consultant Exam (SP25) Questions and Answers

Data Views are system tables in Marketing Cloud that update in near real-time and provide detailed email tracking information such as sends, opens, clicks, bounces, and unsubscribes. They are ideal for custom queries and reports with an hourly refresh frequency through Automation Studio.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Views

→ " Data Views are system-generated tables that provide event-level data for sends, opens, clicks, bounces, and more, updated near real-time. "

Source: Salesforce Help – Automation Studio Query Activities

→ " Data Views can be queried every hour through Automation Studio for up-to-date reporting. "

—

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

—

A Scheduled Automation using a Send Activity is ideal for sending emails to a data extension that is regularly updated. This approach allows for efficient and timely sends without the overhead of journey management, making it suitable for periodic newsletters with dynamic subscriber lists. ​

Einstein Engagement Frequency analyzes subscriber engagement and determines optimal send frequencies. By querying the Einstein Engagement Frequency data extension, you can identify subscribers who have received emails within the past 14 days and exclude them from the current send, ensuring compliance with the desired frequency cap. ​ CloudKettle

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

—

—

—

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

Comprehensive and Detailed Explanation:

The correct answer is C — MuleSoft Anypoint Platform.

MuleSoft is Salesforce’s integration platform that allows data transformation, API orchestration, and real-time integration between systems like a POS and Marketing Cloud.

It can modify and deliver data in the proper format required by the Triggered Send API.

❌ Why others are wrong:

A: Datorama is for marketing analytics, not transactional API integration.

B: Data Studio is a data marketplace, not an integration platform.

D: " Data Connector " is not a standalone Salesforce product for such API transformations.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MuleSoft and Marketing Cloud Integration:

" Use MuleSoft Anypoint Platform for real-time data transformation and integration, allowing external systems to trigger transactional messaging via Marketing Cloud APIs. "

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

—

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

—

The best method is:

Use an Engagement Split in Journey A to identify engagement.

Use Update Contact Activity to update a Boolean field in a Data Extension based on the engagement result.

Later, query this updated engagement Data Extension to inject subscribers into Journey B based on their behavior.

This avoids relying directly on querying system data views and enables near-real-time, easy-to-manage segmentation.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Update Contact Activity in Journey Builder

→ " Use Update Contact Activity to update attribute values for contacts during a journey based on behaviors such as engagement. "

Source: Salesforce Help – Journey Builder Engagement Split

→ " Engagement Split evaluates engagement (open, click) and can trigger updates to data for further automation. "

—

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

—

In Marketing Cloud, using Email Address as the Subscriber Key can lead to issues with tracking subscriber preferences, especially when integrating with Salesforce via Marketing Cloud Connect. If the previous send (from the external system) used Email Address as the Subscriber Key, it might not have correctly updated the subscriber ' s status in the All Subscribers list. Consequently, when MCC sent the email, it treated the subscriber as active, resulting in the email being sent despite the prior unsubscribe. ​

Comprehensive and Detailed Explanation:

The correct answer is C — An external system to receive and confirm callback and subscriptions.

Marketing Cloud’s Transactional Messaging API supports Event Notification Service (ENS), where an external endpoint (callback URL) can subscribe to event notifications like “Not Sent.”

You need an external system capable of receiving real-time POST messages (JSON format) from Marketing Cloud and sending 2xx HTTP status responses to confirm receipt.

❌ Why others are wrong:

A: There is no " Not Sent Notification activity " inside Transactional Journeys — it’s API-based event notifications.

B and D: Datorama and Interaction Studio are analytics and personalization tools, not real-time event handling systems.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Transactional Messaging Event Notification Service:

" An external system must be configured to subscribe to notifications and must be capable of responding to callbacks with an HTTP 2xx status. Event types include Sent, Delivered, Not Sent, etc. "

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

—

Distributed Marketing is specifically designed to allow centralized marketing teams to control messaging and branding while empowering field teams (subsidiaries, partners) to personalize and send communications. It ensures consistency, compliance, and unified branding across campaigns.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Distributed Marketing Overview

→ " Distributed Marketing helps central teams create standardized messaging while allowing local teams to personalize and send communications — ensuring branding consistency. "

Source: Salesforce Product Documentation – Distributed Marketing for Salesforce

→ " Unify your brand experience across every customer communication while enabling personalization and local customization. "

To accomplish the requirement of diverting contacts in a birthday journey based on whether they have redeemed a promotional code (stored in a separate transactional data extension), NTO needs to use a Decision Split Activity using both Contact and Journey Data .

Decision Split Activity : In Journey Builder, the Decision Split Activity evaluates conditions to direct contacts down different paths. It can compare attributes from the journey’s entry source (Journey Data) and related data extensions (Contact Data) linked via Contact Builder.

Journey Data : This refers to the data from the entry source data extension (e.g., the customer data extension used for the birthday journey, containing the customer number).

Contact Data : This refers to data from other data extensions related to the contact, such as the transactional data extension containing promo code redemption details, also linked by the customer number.

Attribute-to-Attribute Comparison : The requirement specifies comparing the customer number field between the journey source and transaction data extensions. This comparison is achieved by configuring the Decision Split to evaluate both Journey Data (from the entry source) and Contact Data (from the related transactional data extension).

Why this solution works:

The Decision Split Activity allows NTO to check if a customer number in the journey’s entry source matches a customer number in the transactional data extension where a promo code was redeemed. If a match exists, the contact can be diverted to a different path, avoiding reminder emails.

Using both Contact and Journey Data ensures the comparison spans the two data extensions, which is necessary since the transactional data is stored separately.

Why the other options are incorrect:

A. Einstein Split Activity : Einstein Splits use AI-driven predictions (e.g., likelihood to open or purchase) rather than direct attribute comparisons. They are not suitable for comparing specific fields like customer numbers across data extensions.

B. Decision Split Activity using only Contact Data : Using only Contact Data would limit the comparison to attributes in related data extensions, excluding the journey’s entry source data (Journey Data), which contains the customer number from the birthday journey. Both data sources are needed for the comparison.

D. Decision Split Activity using only Journey Data : Using only Journey Data would restrict the comparison to the entry source data extension, ignoring the transactional data extension where promo code redemption data is stored.

Exact Extract from Salesforce Documentation:

Journey Builder Decision Splits : " Decision Splits evaluate attributes from the entry event data (Journey Data) or related data extensions defined in Contact Builder (Contact Data). To compare fields across these datasets, configure the split to use both Contact Data and Journey Data. " (Source: Salesforce Help - Journey Builder Decision Splits )

Contact and Journey Data : " Journey Data is dynamic and tied to a specific journey instance. Use Journey Data when evaluating data related to a specific event. Contact Data includes attributes from related data extensions linked via Contact Builder. " (Source: Salesforce Help - Journey Data vs Contact Data )

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: https://help.salesforce.com/s/articleView?id=sf.mc_es_sandbox_testing.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is B — Advertising Studio.

Advertising Studio allows you to sync CRM and behavioral data (like email engagement) with advertising platforms (Google, Facebook, LinkedIn).

It enables you to suppress audiences who have taken specific actions, such as multiple email opens and clicks, from being targeted in paid media campaigns.

❌ Why others are wrong:

A: Mobile Studio handles mobile messaging (SMS, push), not audience suppression for display ads.

C: Google Analytics 360 is used for web tracking and reporting, not managing ad suppression from Salesforce data.

D: Einstein Engagement Scoring helps with email targeting, but it doesn’t manage external ad suppression directly.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Advertising Studio Overview:

" Use Advertising Studio to suppress or target audiences for advertising channels like Facebook, Google, LinkedIn, based on engagement data or CRM attributes to optimize marketing spend. "

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

—

Comprehensive and Detailed Explanation:

Correct answers are A, C, and D.

A — Long and Short Codes are country-specific; availability must be checked per country.

C — Inbound messaging (users texting keywords to subscribe) generally requires local Short or Long Codes.

D — MobileConnect is not supported in every country; Salesforce provides a list of supported regions.

❌ Why others are wrong:

B: Customers are billed by Salesforce, not directly by the mobile carriers.

E: Opt-ins can occur via Web Forms, Mobile Keyword responses, or API — not only via inbound messaging.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Considerations:

" Short and long code availability is country-specific. Inbound messaging requires a local code. MobileConnect is not available in all countries. "

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

—

To efficiently pull in relational data during a journey without overloading the initial entry payload, marketers should use Data Relationships. These relationships allow Journey Builder to dynamically reference related records during a Decision Split, Lookup, or Wait Until Activity without needing to duplicate all the information at entry.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Relationships in Contact Builder

→ " Data Relationships define how different data extensions relate to each other and allow Journey Builder to reference external data dynamically during a contact’s journey. "

Source: Salesforce Help – Journey Builder Best Practices

→ " Use Contact Builder data relationships to reference additional information without overloading entry events. "

—

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

Comprehensive Explanation:

Long codes can be used for outbound messaging across multiple countries. However, inbound messaging capabilities are often restricted to specific countries due to local regulations and carrier requirements. If NTO needs to support inbound messages (i.e., two-way communication) in each country, they may need to provision separate long codes for each country to comply with local regulations and ensure message deliverability. ​

Comprehensive and Detailed Explanation:

The correct answer is B — Use an automation with Tracking Extract.

Tracking Extract Activity in Automation Studio can pull detailed send status data, including ‘Not Sent’ reasons (bounces, held status, validation errors).

From the extracted tracking file, you can create reports or data extensions specifically identifying Not Sent contacts.

❌ Why others are wrong:

A: No built-in standard report in Salesforce Marketing Cloud specifically called “Subscribers Not Sent to.”

C: Discover reports focus on aggregate metrics, not granular send statuses.

D: _Sent Data View records only successful send attempts; ' Not Sent ' contacts are not logged in _Sent.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract Activity Overview:

" Use the Tracking Extract Activity to extract detailed subscriber-level data including message not sent events, undelivered messages, and reasons for failure. "

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

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 _Click data view in Marketing Cloud stores information about link clicks for up to six months. By writing and executing a SQL query against this data view in Automation Studio, the customer can accurately identify subscribers who have clicked on any links within the specified timeframe. ​

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: https://help.salesforce.com/s/articleView?id=sf.mc_amplanguage_lookuprows.htm )

— —

Comprehensive and Detailed Explanation:

The correct answer is D — Select " Subscribers will be unsubscribed from this business unit only " in Settings.

This setting ensures that if a subscriber unsubscribes from the children ' s brand (child business unit), they are only removed from communications for that BU — not for the main Enterprise brand.

It ' s the easiest, no-code-required solution ideal for customers with minimal technical resources.

❌ Why others are wrong:

A: Separate Subscription Center would require building and maintaining separate pages, adding complexity.

B: Managing unsubscribe status manually through attributes would be a heavy lift without developers.

C: Business Unit Filters manage viewing access, not opt-out behaviors.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Business Unit Settings and Unsubscribe Management:

" To allow independent unsubscribe management, select ' Subscribers will be unsubscribed from this business unit only. ' This setting ensures opt-outs affect only the business unit where the unsubscribe occurred. "

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

Understanding why 10 years of historical data is required will help assess if storing all that data in Marketing Cloud is necessary and practical (A).

Knowing whether their account includes Large Data Extensions is critical because standard Data Extensions might not efficiently support 200+ million records (C).

Timing (B) and API rate (D) are relevant for optimization but not as critical as validating storage capabilities and necessity.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Large Data Extensions Overview

→ " Large Data Extensions are required for storing more than 30 million records and for managing massive datasets efficiently. "

Source: Salesforce Best Practices – Data Management Discovery

→ " Clarify the business purpose of historical data import to align storage and performance with actual marketing needs. "

—

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

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

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

Text Response templates allow recipients to reply to an SMS message, and MobileConnect can handle that reply.

Data Capture templates allow you to store the SMS reply into a specific Data Extension for further processing, especially when using AMPscript.

Info Capture is used for form-style step-by-step conversations, not one-shot responses. Outbound is simply for sending SMS messages, without expecting or processing replies.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – MobileConnect Message Templates

→ " Use Text Response to receive responses from subscribers and store those responses in a data extension with Data Capture templates. "

Source: Salesforce Help – Data Capture for SMS Responses

→ " Data Capture templates in MobileConnect enable collection of information from subscribers directly into a data extension for further use. "

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

The correct answer is D, because:

When using the " View As Web Page " (VAWP) link in Salesforce Marketing Cloud, it references a unique URL tied to the SendID and SubscriberKey.

If the original audience is overwritten (i.e., deleted and recreated), the SendID linked to the VAWP breaks, because the original context no longer exists.

To prevent this, upserting (inserting new and updating existing records) ensures that subscriber records persist and stay tied to the correct send, keeping the VAWP links functional even as the audience updates daily.

Official Salesforce documentation specifies:

" Overwriting a Data Extension can cause issues with Send Logging and View As Web Page links. If historical data must be maintained to ensure link functionality, records should be upserted rather than overwritten. "

(Source: Salesforce Marketing Cloud Data Extensions Best Practices Guide)

In an upsert, you are updating existing records based on a primary key (typically SubscriberKey) and inserting new ones when no match exists, thus maintaining historical integrity necessary for things like VAWP.

Reference Extract:

" An upsert operation adds new records and updates existing ones in a Data Extension without deleting historical data. This method maintains the consistency required for links like ' View As Web Page ' to remain functional. "

(Source: Salesforce Marketing Cloud SQL Query Activities - Best Practices)

Why the other options are wrong:

A: Exclusion lists are about avoiding resending, not about preserving VAWP functionality.

B: AMPscript and send logging manage dynamic content, not VAWP link integrity.

C: Overwriting the DE deletes the old SendIDs, breaking VAWP links.

Thus, option D (Upsert) is correct.

Comprehensive and Detailed Explanation:

The correct answer is D — Dynamic Content Blocks.

Dynamic Content Blocks allow non-technical users to personalize email content based on field values without writing code.

It ' s a drag-and-drop method where rules are created visually, ideal for a team with little coding experience.

❌ Why others are wrong:

A: Sending separate template-based emails would be inefficient and hard to manage at scale.

B: Reference Content Blocks help reuse content but don ' t personalize based on data fields.

C: AMPscript requires scripting knowledge, which the team lacks.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Dynamic Content Blocks Overview:

" Dynamic Content Blocks let users create different content variations based on subscriber attributes without the need for coding, making it easy to personalize emails. "

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

—

✅ Comprehensive and Detailed Explanation: The correct approach is one Parent Business Unit (corporate) with one Child Business Unit per franchise owner . This setup allows:

Corporate to control global assets, subscriber management, and brand compliance.

Franchise owners to localize messages within their own Business Unit, without accessing or changing corporate-controlled assets.

❌ Why Other Options Are Incorrect:

A: “Franchise owners” (plural) need individualized control; a single child BU won ' t be sufficient.

C: One Business Unit won ' t provide separation between different franchise operations.

D: Having a separate parent BU for each franchise is excessive, costly, and not scalable.

Exact Extract: Salesforce Help: Business Unit Overview

" Use Business Units to manage assets, permissions, and subscribers separately while maintaining corporate brand control across an enterprise. "

To prevent duplicate Contact records, the customer needs to update the current All Subscribers list and Contact model by migrating the Subscriber Key to match the Sales Cloud ContactID or LeadID (B).

Uploading a CSV with the new Subscriber Keys mapped appropriately will ensure that existing records are updated (A).

Simply continuing as normal (C) will not prevent duplicates because Email Address is not unique enough across Salesforce objects. Full purge (D) is unnecessary and risks data loss.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Subscriber Key and Contact Key Best Practices

→ " When integrating Sales Cloud, update existing Marketing Cloud subscribers to match the Salesforce ContactID or LeadID as Subscriber Key to prevent duplicate contacts. "

Source: Salesforce Implementation Guide – Marketing Cloud Connect Setup

→ " Migrating existing contacts requires careful key management to align records across systems without duplication. "

—

Comprehensive and Detailed Explanation:

Correct answers are C and D.

C — Shipment object must have a Lookup relationship to either Lead or Contact to map and trigger the send to the correct subscriber.

D — An Apex Trigger must be created on the Shipment object to fire the Triggered Send via the Marketing Cloud Connect package.

❌ Why others are wrong:

A: It does not matter if the Shipment is visible on the Account Related List.

B: A Lookup relationship (not necessarily Master-Detail) is needed. Master-Detail is not required.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Triggered Sends in Marketing Cloud Connect:

" To use Triggered Sends on custom objects, the object must include a Lookup field to Lead or Contact and must have an Apex Trigger to initiate the send based on changes to the object. "

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

—

Marketing Cloud Connect allows users to send emails directly to Salesforce Report audiences without needing to sync all custom objects into Marketing Cloud. This method minimizes setup and allows continued use of existing Salesforce reports.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect: Send to Salesforce Reports

→ " Use Salesforce Reports as an audience for sends from Marketing Cloud without syncing all Salesforce data. "

Source: Salesforce Help – Marketing Cloud Connect Overview

→ " Marketing Cloud Connect enables sending emails to Leads, Contacts, Campaigns, and Reports directly from Marketing Cloud. "

—

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: https://help.salesforce.com/s/articleView?id=sf.mc_automation_studio_verification_activity.htm )

—

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

Comprehensive and Detailed Explanation:

Correct answers are A, B, and C.

A — Journey Builder allows simple segmentation using Entry Events and Filters without complex SQL Queries.

B — Journey Builder’s drag-and-drop UI helps create complex decision splits and paths easily.

C — Behavior-based goals (e.g., click a link, open an email, purchase completed) are set within Journey Builder to track success.

❌ Why others are wrong:

D: Processing zipped, encrypted files (e.g., decryption, file transfer) is handled in Automation Studio, not Journey Builder.

E: Complex customer segmentation across multiple DEs often still requires SQL queries in Automation Studio.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder vs Automation Studio:

" Use Journey Builder to create behavior-based journeys and decision splits with a visual interface. Use Automation Studio for complex queries, large data imports, and file processing. "

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_jb_vs_as.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 )

To synchronize subscriber data and unsubscribe statuses across all child business units in an Enterprise 2.0 Marketing Cloud account to an external CRM, the appropriate data views to query are _Subscribers and _BusinessUnitUnsubscribes.

_Subscribers Data View : This data view contains information about all subscribers in the Marketing Cloud account, including their Subscriber Key, Email Address, Status (e.g., Active, Unsubscribed, Bounced, Held), and other attributes. It is essential for identifying subscribers and their current status across the enterprise account.

Why it’s needed : The question specifies finding subscribers in the Marketing Cloud account, which requires querying the _Subscribers data view to retrieve subscriber details.

_BusinessUnitUnsubscribes Data View : This data view tracks unsubscribe events at the business unit level, including the Subscriber Key, Business Unit ID, Event Date, and other details for each unsubscribe event. It is critical for capturing unsubscribe data across child business units in an Enterprise 2.0 account, as it provides a consolidated view of unsubscribe activities specific to each business unit.

Why it’s needed : The question emphasizes capturing unsubscribe data for child business units, which _BusinessUnitUnsubscribes uniquely provides.

Why the other options are incorrect:

A. _Complaint : This data view tracks email complaints (e.g., when a subscriber marks an email as spam). While related to subscriber behavior, it does not capture general unsubscribe events or subscriber status, making it irrelevant for this use case.

B. _Unsubscribe : This data view records unsubscribe events but is limited to the context of the parent business unit and does not provide business unit-specific unsubscribe data for child business units. In an Enterprise 2.0 account, _BusinessUnitUnsubscribes is required for cross-business unit tracking.

Exact Extract from Salesforce Documentation:

_Subscribers Data View : " The _Subscribers data view returns information about the subscribers in a Marketing Cloud account, including SubscriberKey, EmailAddress, Status, and DateJoined. " (Source: Salesforce Help - Data View: Subscribers )

_BusinessUnitUnsubscribes Data View : " This data view contains a record for each unsubscribe event at the business unit level. It’s used in Enterprise 2.0 accounts to track unsubscribe activity across multiple business units. " (Source: Salesforce Help - Data View: BusinessUnitUnsubscribes )

The correct answers are A, C, and D , because:

When planning the number of Business Units (BUs) for a Marketing Cloud Enterprise 2.0 account, Salesforce recommends evaluating organizational structure and data/content needs carefully. Business Units help segment marketing assets, contacts, and campaigns, often aligned to brands, regions, or departments.

According to Salesforce official documentation:

" When considering the number of Business Units needed, important factors include:

Number of brands, products, or regions that require separate marketing efforts.

Requirements to separate data and content between business units (for security, branding, or operational independence).

The need for dedicated development or test environments within Marketing Cloud. "

(Source: Salesforce Marketing Cloud Implementation Guide – Business Unit Planning)

Let ' s break it down:

✅ A. Number of brands/geographies which NTO operates

Different brands or regions often need separate BUs to manage independent marketing strategies, content, and contacts.

✅ C. If testing/development business unit(s) are required

It’s a best practice to have separate BUs for development and testing purposes to avoid interfering with live sends.

✅ D. If data/content needs to be segregated between brands/geographies

When different teams or brands should not have access to each other ' s customer data or assets, separate BUs ensure proper data governance and security.

Why the other options are incorrect:

❌ B. Number of Sales Cloud sandboxes :

The number of Sales Cloud sandboxes is irrelevant to how many BUs you need. BUs are for organizational segmentation, not related to sandbox environments.

❌ E. Number of Marketing Cloud users :

User count affects licensing and access management but does not drive the number of BUs needed.

Additional official note from Salesforce:

" Use Business Units to separate marketing activities by division, brand, or region. Business Units are not determined by the number of users or CRM sandboxes. "

(Source: Salesforce Help - Enterprise Account Structure Overview)

Thus, the correct choices are A , C , and 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: https://help.salesforce.com/s/articleView?id=sf.mc_ms_send_data_extensions.htm )

—

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: https://help.salesforce.com/s/articleView?id=sf.mc_ms_conversation_window.htm )

—

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 )

—