Pass the Salesforce Marketing Cloud Consultant Marketing-Cloud-Consultant Questions and answers with ExamsMirror

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

B — AMPscript can dynamically lookup the subscriber's preferred language and pull the appropriate localized content inside the same email template.

D — Enhanced Dynamic Content Blocks allow managing different content variations (like languages) efficiently inside Content Builder without duplicating entire templates.

❌Why others are wrong:

A: Personalization strings only pull field values — they are not intended for managing full language-specific content changes.

C: Concept Builder does not exist — you may have meant Content Builder, but creating separate templates for each language would not be scalable as the number of languages grows.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Personalization and Dynamic Content:

"Use AMPscript or Enhanced Dynamic Content to personalize email messages based on subscriber attributes, including language preferences, ensuring efficient management of multiple content variations."

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

—

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 A — Data Filters.

Data Filters provide a drag-and-drop, no-code way to segment audiences based on profile attributes or behavior.

They allow marketing users without SQL or AMPscript knowledge to build audiences directly in Email Studio.

❌Why others are wrong:

B: Attribute Groups are used for mapping relationships between data, not for audience segmentation.

C: Publication Lists manage opt-in/out preferences, not audience segmentation.

D: Query Activities require SQL coding, which the team lacks experience with.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Filters Overview:

"Data Filters allow users to segment data extensions based on attribute values and behavior using a simple drag-and-drop interface, without the need for coding."

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

—

Comprehensive and Detailed Explanation:

The correct answer is D — Create and send to a sendable data extension containing those needed fields using a query activity.

Pre-populating a single sendable data extension with all necessary personalization fields eliminates the need for real-time lookups during sending.

It dramatically speeds up send processing because personalization is sourced directly from the send context.

❌Why others are wrong:

A: Profile attributes are outdated and limited for handling many fields from multiple sources.

B: Send throttling slows down sends to control delivery rate — it doesn’t speed it up.

C: Lookup functions cause real-time database queries during send time, slowing down large sends.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Personalization and Send Performance:

"To improve send performance, include all required personalization attributes in the send context (Data Extension) rather than relying on AMPscript Lookups at send time."

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

—

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 toselect '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)

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:

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 )

The correct answer isB, because:

Salesforce Marketing Cloud uses aSender Authentication Package (SAP)to establish proper authentication (including setting up DNS entries for SPF, DKIM, and DMARC) for email sending domains.

When NTO wants tosend emails from a new domain(comms.nto.com.au), they would need anew SAPto configure authentication correctly for that domain — this ensuresdeliverability, 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 atracking domainused for link redirection, not sending domain authentication itself.

❌D. Register the new domain in Setup > From Address Management:

From Address Management is forallowing or restrictingsender addresses butdoes not authenticatethe 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,Bis the correct and required action.

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

—