Salesforce Marketing-Cloud-Consultant Dumps Questions Answers

To enable sending emails from a new domain (comms.nto.com.au) for Australian customers without impacting deliverability, Northern Trail Outfitters (NTO) must implement an additional Sender Authentication Package (SAP) .

Sender Authentication Package (SAP) : An SAP is a Marketing Cloud feature that authenticates a custom sending domain (e.g., comms.nto.com.au) to ensure emails are sent from a verified domain, improving deliverability and brand trust. It includes:

DomainKeys Identified Mail (DKIM) : Signs emails to verify the sender’s identity.

Sender Policy Framework (SPF) : Validates the sender’s IP address.

Domain-based Message Authentication, Reporting, and Conformance (DMARC) : Enforces authentication policies to prevent spoofing.

Why it’s needed :

Using a new domain without proper authentication risks emails being marked as spam or rejected by email providers, impacting deliverability.

An SAP ensures that the new domain (comms.nto.com.au) is fully authenticated and aligned with email best practices, maintaining NTO’s sender reputation.

Implementation : NTO must purchase an additional SAP for the new domain, configure DNS records (DKIM, SPF, DMARC), and associate the domain with their Marketing Cloud account.

Why the other options are incorrect:

B. An additional IP address : A new IP address is not required for sending from a new domain. IPs are tied to the sending infrastructure, not the domain. Using a new domain with an existing IP is standard practice, provided the domain is authenticated via SAP.

C. An additional private domain : A private domain in Marketing Cloud is used for link wrapping and image hosting, not for sending emails. It does not address sender authentication or deliverability for the From address.

D. Register the new domain in Setup’s From Address Management : While registering the domain in From Address Management is a step in configuring the sending domain, it alone does not provide the full authentication (DKIM, SPF, DMARC) required to maintain deliverability. An SAP is needed to complete the setup.

Exact Extract from Salesforce Documentation:

Sender Authentication Package : "A Sender Authentication Package (SAP) authenticates a custom domain for sending emails, ensuring compliance with SPF, DKIM, and DMARC standards to maximize deliverability and protect your brand reputation." (Source: Salesforce Help - Sender Authentication Package )

Domain Setup for Deliverability : "To send emails from a new domain without impacting deliverability, configure a Sender Authentication Package to authenticate the domain and update DNS records for SPF, DKIM, and DMARC." (Source: Salesforce Help - Email Deliverability Best Practices )

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