Free Salesforce Marketing Cloud Engagement Consultant Practice Test Questions

Explanation:

When using a File Drop Automation, the file that triggers the automation can have a changing name, as long as it follows a consistent pattern, such as always starting with thank_you_customers.

To make the subsequent Import Activity pick up exactly the file that triggered the automation, you use a substitution string in the Import Activity's File Naming Pattern field:

%%BASEFILENAME_FROM_TRIGGER%%
This returns the base name of the file that triggered the automation, without any file extensions. You can then append the expected extension if needed, such as %%BASEFILENAME_FROM_TRIGGER%%.csv.

This is the standard and recommended way to dynamically reference the triggering file in File Transfer or Import activities within a File Drop Automation.

Why the Other Options Are Incorrect

A. %%AUTOMATED_FILENAME%%
%%AUTOMATED_FILENAME%% is not a valid substitution string for this purpose.

B. The filename is automatically passed to the Import Activity
The filename is not automatically passed to the Import Activity. You must explicitly use a substitution string.

C. Use filename from Automation checkbox
There is no "Use filename from Automation" checkbox in the Import Activity.

Reference
Salesforce Help – Substitution Strings Example (Automation Studio):
%%BASEFILENAME_FROM_TRIGGER%% is specifically documented for use in the File Naming Pattern of Import / File Transfer activities in File Drop Automations so the activity can reference the exact file that started the automation.

Explanation:

When you need to segment contacts before they enter a journey, the standard and most efficient approach is to use a Data Extension Entry Source with a filter. Journey Builder allows you to configure a filter directly on the entry source, so only contacts who meet the criteria, such as recent member activity, are admitted into the journey.

The expected volume, approximately half the contacts, is not a barrier. Journey Builder handles large data extensions efficiently, and pre-filtering at the entry source reduces processing load by limiting the contacts evaluated for injection.

How It Works
Create a sendable Data Extension containing the loyalty member data, including fields for recent activity.
In Journey Builder, drag a Data Extension entry source onto the canvas and select that Data Extension.
Configure a filter on the entry source using the relevant activity attribute, such as LastActivityDate being within the last 30 days.
Set the schedule to evaluate the Data Extension and admit matching contacts.

This approach ensures only contacts meeting the activity criteria enter the journey, avoiding unnecessary processing for the half of the database that doesn't qualify.

Why Other Options Are Wrong

B. Use a Contact Data Entry Source to segment the data configured in Attribute Groups in Contact Builder
The Contact Data entry source type is being deprecated. Salesforce explicitly notes: "In an upcoming release, Contact Data Events aren't supported. Use the Data Extension entry source to admit contacts instead". Contact Data is designed for decision splits within a journey, such as evaluating changing values, not as a primary entry source for segmenting contacts before they enter.

C. Use an Import Activity in Automation Studio to filter the data as a Data Extension Entry Source
Import Activities import data into a Data Extension. They do not filter records based on criteria. You would still need to apply a filter on the entry source itself. This option describes a data ingestion step, not an entry source configuration.

D. Use a Query Activity in Automation Studio to create a segment before entering the journey
While a Query Activity can create a segmented Data Extension, this is an additional step that is not required. The question asks how to configure the entry source, and the native filter option on the Data Extension entry source achieves the segmentation directly without needing a separate Query Activity.

Key Exam Takeaway
When a scenario involves segmenting contacts before they enter a journey, the answer is almost always Data Extension Entry Source with a filter. Remember:

The filter is configured on the entry source itself in Journey Builder
Contact Data entry sources are being deprecated — use Data Extension entry sources instead
Pre-filtering at the entry source is a best practice for performance

Explanation:

NTO needs to ensure that no loyalty segment exceeds 2,500 contacts before the monthly balance email is sent.

In Automation Studio, the Verification Activity is specifically designed for this purpose:

Place it in the automation after the Query/Filter activities that create the segmented Data Extensions and before the Send Email activities.
Configure it to evaluate the target Data Extension(s).
Set a condition such as “Count is greater than 2,500”.
Choose the action to Stop the automation and optionally send a notification email.

If any segment exceeds the limit, the Verification Activity stops the automation, preventing the email from being sent.

Why the Other Options Are Incorrect

B. Stop Activity
There is no standalone “Stop Activity” in Automation Studio. Stopping is an action available inside the Verification Activity.

C. Script Activity
Could theoretically be used with custom code, but it is more complex and not the intended tool for simple record-count checks.

D. Query Activity
Used to create or filter data, not to evaluate a count and halt the automation.

Reference
Salesforce Help – Verification Activity: Allows you to monitor a Data Extension’s record count and stop the automation, or send a notification, when a defined threshold is met, preventing unintended sends.

Explanation:

Northern Trail Outfitters wants to run a re-engagement campaign targeting app users, social platform users, and email subscribers.
The requirement is that if a subscriber opens or clicks an email, they should be removed from the campaign.
This type of cross-channel orchestration is best handled in Journey Builder using a single omni-channel Journey:

Email channel → initial re-engagement attempt.
Push notifications → target app users who did not engage with email.
Social ads → target social platform users who did not engage with email.

Journey Builder supports exit criteria (e.g., if subscriber opens/clicks, they exit the journey). This ensures that once engagement occurs, the subscriber is removed from further messaging across all channels.

Why Not the Other Options?

B. An automation within Automation Studio which leverages a Script Activity
Automations are batch-based and not designed for real-time, cross-channel re-engagement logic. Script Activities add unnecessary complexity.

C. Multiple journeys focused on individual communication channels
Splitting into multiple journeys would make it harder to manage exit criteria across channels. Omni-channel orchestration is more efficient.

D. An automation in Automation Studio that imports engagement data and creates a suppression audience
Suppression audiences can remove engaged contacts, but this approach is batch-based and not real-time. It doesn’t fulfill the requirement for immediate removal upon engagement.

Reference
Salesforce Help: Journey Builder Activities and Exit Criteria
Trailhead: Marketing Cloud Journey Builder

Explanation

NTO is continually adding new rows to a Data Extension via API, with each row representing a subscriber who should receive that day's payment reminder.
When a Journey uses a Data Extension Entry Source, Journey Builder needs to identify which records should enter the journey. Since the API is continuously adding new subscribers, the journey should evaluate new records only.

With:

Contact Evaluation → Evaluate new records only
Journey Builder evaluates records that are newly added to the entry Data Extension and injects those contacts into the journey. Existing records that were already evaluated aren't repeatedly processed.

This is appropriate for a recurring process where API processes populate the Data Extension with the subscribers who need a reminder.

Why the Other Options Are Incorrect

A. Contact Evaluation → Evaluate new records only — Correct
This is the appropriate setting when new rows are continuously added to the entry Data Extension and only those newly added subscribers should be evaluated for entry.

B. Journey Settings → Use email attribute from Contacts — Incorrect
This setting determines where Journey Builder obtains the email address used for sending. It does not determine which new Data Extension records are evaluated for entry.

C. Contact Evaluation → Evaluate all records — Incorrect
Evaluating all records could cause existing records in the Data Extension to be evaluated again. The requirement is to process the newly added subscribers, not repeatedly evaluate the entire Data Extension.

D. Journey Settings → No re-entry — Incorrect
Re-entry settings control whether a contact can enter a journey again after already entering it. They don't determine whether newly added Data Extension records are evaluated.

Exam Tip

When you see:
API continually adds new rows to a Journey entry Data Extension

Think:
Contact Evaluation → Evaluate new records only

This ensures that the newly added subscribers are evaluated and processed without unnecessarily re-evaluating existing records.

Answer: A. Contact Evaluation → Evaluate new records only

Explanation:

Why A is correct: The Verification Activity in Automation Studio evaluates a target data extension against predefined conditions, such as minimum or maximum row counts. By placing it directly after the import activity (which populates the staging data extension) and before the SQL Query activity, the automation can inspect the volume of imported records. If the record count exceeds the specified threshold (e.g., more than 1,000 records), the verification fails, stops the automation workflow from proceeding, and sends a notification to the marketing manager—preventing the downstream sendable data extension from being updated.

Why B is incorrect: Splitting activities into separate automations introduces orchestration complexity and timing issues without inherently providing a threshold-checking or safety-stop mechanism.

Why C is incorrect: Writing custom Server-Side JavaScript (SSJS) requires complex custom coding, whereas Marketing Cloud provides a native, declarative feature (Verification Activity) specifically designed for quality control and volume checks.

Why D is incorrect: A Wait Activity only pauses workflow execution for a set duration or until a specific time; it does not check data row counts or evaluate conditional volume rules.

Reference
Salesforce Documentation: Verification Activity in Automation Studio

Explanation:

In Salesforce Marketing Cloud, a Random Data Extension is a built-in feature specifically designed to randomly segment a source audience into smaller groups for testing purposes. You can create a Random Data Extension from the Email Studio interface (under Subscribers > Data Extensions).

The key constraint provided in the question is the need to split the audience into 11 groups. According to Salesforce documentation, when using the Random Data Extension feature, you can create up to 12 groups at a time. This perfectly aligns with the requirement to split 880,000 subscribers into 11 distinct groups. This method is the standard, no-code solution for this specific use case.

Analysis of Why Other Options Are Incorrect
Here is why the other options do not fit the requirements:

A. Use Automation Studio with a random split activity.

This option is incorrect because Automation Studio does not have a native "Random Split" activity. The activities available in Automation Studio include SQL Query, Filter, Import File, Data Extract, and Send Email. While you could use a complex SQL query to assign random numbers to records and split them, there is no dedicated "Random Split" activity in Automation Studio like there is in Journey Builder.

B. Use Journey Builder with a random split activity.

While Journey Builder does have a Random Split activity, it is not the correct tool for this specific scenario. The Journey Builder Random Split activity is designed to route contacts that are entering a journey down different paths based on a percentage (e.g., a 50/50 split). It is not a tool for segmenting a static, master data extension of 880,000 subscribers into 11 distinct, persistent groups for testing outside of a journey. Furthermore, the Journey Builder Random Split activity is configured for a limited number of paths (often up to 10), whereas the Data Extension method allows for up to 12.

C. Create a random data extension within Contact Builder.

This option is incorrect because, while Contact Builder is the central location for managing data relationships, the functionality to create a Random Data Extension resides within Email Studio. If you navigate to Contact Builder and attempt to create a Data Extension, you will not find the "Random" type as a native creation option there. The feature is accessed via the Email Studio menu path (Subscribers > Data Extensions).