Salesforce Marketing-Cloud-Consultant Exam With Confidence Using Practice Dumps

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 )

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 )

Knowing if the file is a delta (only new/updated records) or historical (full set) impacts how imports and updates should be configured (A).

Consistency of the file drop time affects whether to use Scheduled or File Drop Automations (D).

Error notification is critical to quickly address any issues with file import (E).

File size over 5,000 rows (C) is not a problem — Marketing Cloud handles millions of records per automation. Data Relationships (B) are more relevant to segmentation after import, not the automation itself.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – File Import Automation Planning

→ "Determine if files are incremental or full to properly set import methods. Confirm expected file timing to design scheduled or triggered automations."

Source: Salesforce Help – Automation Studio Best Practices

→ "Always configure error notifications on Import Activities to ensure prompt action in case of import failures."

—