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:

The correct answer is D — Journey Builder multi-step journey with an API entry event and a decision split.

API Entry Event: Order system triggers a real-time entry into the Journey when the order is ready.

Decision Split: Based on customer ' s communication preference (SMS or Email), the journey will send the appropriate message.

❌ Why others are wrong:

A: MobileConnect Outbound Message can ' t dynamically decide fallback channel inside AMPscript easily.

B: Transactional Send Journeys are typically for single email sends, not channel preference branching.

C: Automation Studio is time-based, not ideal for real-time order notifications and dynamic preference handling.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Journey Builder API Entry Event:

" API Event Entry allows external systems to trigger customer journeys in real-time, optionally combined with Decision Splits to deliver different channel communications based on customer attributes. "

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

✅ Comprehensive and Detailed Explanation:

This is a classic transactional use case involving multiple channels: if the password reset email fails to send, the system must fallback to SMS delivery.

The best-practice solution is to:

Use a Transactional Send API for password reset emails.

Use the Event Notification Service (ENS) to monitor delivery or bounce events in near real-time.

Based on failure status, trigger an API call to initiate an SMS message.

D is the only option that uses Salesforce’s native ENS and API infrastructure for near real-time failure handling, which meets the requirement for “timely delivery.”

❌ Why Other Options Are Incorrect:

A. The Not Sent data extract is not real-time and is typically processed in batch — not suited for password resets that require instant fallback.

B. Engagement Splits (e.g., link clicked) are not ideal for determining whether an email was delivered or not. Plus, password resets don’t rely on email clicks — they’re more about deliverability.

C. API responses for triggered email sends do not reflect actual delivery success or failure — they only reflect submission status. You need ENS to monitor actual send results.

Exact Extracts from Salesforce Documentation:

Salesforce Event Notification Service (ENS): " ENS sends near-real-time email delivery, bounce, or click events to external systems so you can monitor transactional sends and take automated actions (e.g., triggering an SMS). "

— Source: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/ens-overview.html

Transactional Email via API: " Use the Transactional Messaging API to send password resets or other 1-to-1 emails. Integrate with Event Notification Service to determine the outcome of each message. "

— Source: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/sendTransactionalEmail.html

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

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 )

Comprehensive and Detailed Explanation:

The correct answer is D — Contact Data using Synchronized Data Sources.

Synchronized Data Sources (via Marketing Cloud Connect) bring Salesforce CRM data into Marketing Cloud in near real-time (every 15 minutes minimum sync).

Contact Data allows access to the latest information related to the contact during the Journey for Decision Splits and personalization.

This setup ensures journeys react dynamically to CRM updates without waiting for a separate file import.

❌ Why others are wrong:

A: Journey Data is static — it does not update after the contact enters the journey unless using Contact Data.

B: Profile Attributes are old data model elements, not suitable for connected real-time CRM data.

C: CRM Report Import is batch-based and not truly near real-time.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Synchronized Data Sources Overview:

" Synchronized Data Sources allow Marketing Cloud to access near real-time CRM data, synchronized automatically at intervals (minimum every 15 minutes). You can use Synchronized Data with Contact Data in journeys and decision splits. "

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

—

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.

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 )

—

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

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

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

—