Free Practice Questions for Salesforce Marketing-Cloud-Consultant Exam

In Marketing Cloud's Automation Studio, when configuring a File Drop Automation, the system automatically detects and uses the file that triggers the automation.The Import File Activity within this automation doesn't require a specific filename; instead, it processes the file that initiated the automation.Therefore, there's no need to set a dynamic file naming pattern or check additional options.​

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 properly log values, the AMPscript variable names must match the field names in the Send Log (A).

Additionally, Send Logging must be configured and enabled during the send setup to ensure data is captured into the log (C).

Simply linking a Send Log to an Attribute Group (B) is irrelevant to Send Logging. WriteToLog() (D) is used mainly for server-side debug logging, not for populating Send Logs.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Send Logging Overview

→ "To log values to the Send Log, AMPscript variable names must exactly match the corresponding field names in the log, and logging must be enabled during the send process."

Source: Salesforce Help – AMPscript Functions (WriteToLog)

→ "WriteToLog() is primarily used for troubleshooting and development, not for writing data to the Send Log."

—

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.

The correct answer isB, 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 specificunsubscribe keywordsare 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" arenot yet addedto the filtered keyword list, RMM will not recognize them as unsubscribe requests, andno action(unsubscribe) will be taken.

✅To correct this:

You must add custom phrasessuch as "take me off your list" and "opt out" to theFiltered Keywordslist 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 butwon't automatically detect entirely new phrasesunless 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,Bis the correct solution.

To enable sending emails from a new domain (comms.nto.com.au) for Australian customers without impacting deliverability, Northern Trail Outfitters (NTO) must implement anadditional 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)

The correct answer isD, because:

In Salesforce Marketing Cloud'sJourney Builder, aDecision Split Activityallows marketers to direct contacts down different paths based on defined attributes.

Whencomparing data from the entry source(Journey Data)and from additional data extensions(Contact Data or Event Data Extensions like a Transaction DE), you must configure the Decision Split to referenceboth Contact and Journey Data.

Salesforce documentation explains:

"Journey Datais information captured at the moment of journey entry (i.e., the fields from the entry event data extension).

Contact Datais information related to the contact stored outside the entry event, often in other data extensions linked to the Contact model.

To compare fields across these datasets inside a Decision Split, you must configure the split to useboth Contact Data and Journey Data."

(Source: Salesforce Help - Journey Builder Decision Splits Overview)

Specifically, for NTO:

Journey Datawould be the birthday journey source Data Extension.

Contact Datawould be the external Transaction DE containing promotional code redemption information.

Key actions required:

UseDecision Split Activity.

Configure the decision split to evaluate bothContact Data and Journey Data.

Compare theCustomer Numberfields between both datasets to determine if a promotion was redeemed.

Why the other options are incorrect:

❌A. Decision Split Activity using only Contact Data:

Only using Contact Data won't allow comparison with the Journey Data (entry DE values).

❌B. Decision Split Activity using only Journey Data:

Only using Journey Data won't allow checking against external Transaction Data Extensions.

❌C. Einstein Split Activity:

Einstein Split uses AI to predict engagement (like open or click probability), not field comparison across datasets.

Additional official extract for clarity:

"When building decision splits that rely on both entry data and external profile attributes, ensure to select the appropriate source (Contact Data and Journey Data) to create accurate comparisons."

(Source: Salesforce Marketing Cloud Journey Builder User Guide)

Thus, the correct answer isD.

BuildRowSetFromJSON() is an AMPscript function specifically designed to parse JSON payloads into usable row sets inside emails. This allows marketers to iterate through JSON objects easily and display order details dynamically in triggered transactional emails.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – AMPscript BuildRowSetFromJSON() Function

→ "BuildRowSetFromJSON parses a JSON string and creates a rowset suitable for use in AMPscript loops."

Source: Salesforce Help – Formatting JSON in Emails

→ "Use BuildRowSetFromJSON to extract and format dynamic data from JSON payloads in triggered transactional sends."

—

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 )

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

—