Explanation:

These are key architectural constraints when using a File Drop Automation to trigger a workflow based on an incoming file:

B. The directory is unable to be used by another File Drop Automation: This is a hard technical limit. Each specific directory monitored on the Enhanced SFTP can be associated with only one File Drop Automation trigger.

C. The directory used by the file trigger should be inside the import directory: This is the required structure for the Enhanced SFTP when setting up Automations. The file must be dropped into a folder structure that exists inside the /Import/ directory of the Marketing Cloud Enhanced SFTP for the File Drop Automation to successfully detect and process the file.

❌ Analysis of Incorrect Answers

A. They may utilize an external FTP site: File Drop Automations require the use of the Marketing Cloud Enhanced SFTP. They cannot monitor external SFTP sites.

D. The directory cannot contain more than five file triggers: The limit is one File Drop Automation per directory, not five.

📚 References
Salesforce Help: File Drop Automation (Specifically covers the directory constraints and usage of the Enhanced SFTP).

Explanation:

Why the Answer is Correct
In a Journey Builder setup where rows are continually added to a Data Extension via API for daily payment reminders, selecting "Contact Evaluation > Evaluate new records only" ensures that only the newly inserted subscribers (those with payments due that day) are processed and enter the journey each time it runs on a recurring schedule.
This setting optimizes performance by scanning only additions since the last evaluation, preventing re-injection of prior days' subscribers who may have already received their reminders or no longer qualify. For Northern Trail Outfitters, this means accurate, timely sends without duplicates or unnecessary processing, aligning with API-driven real-time data ingestion. The journey can be configured with a Data Extension Entry Source on a recurring schedule (e.g., daily at midnight), and this evaluation mode maintains data integrity while scaling for high-volume additions. It also supports compliance by avoiding over-messaging, as older records are ignored unless explicitly re-entered via other rules.
This configuration promotes efficiency in resource usage, reduces send costs, and ensures the journey focuses solely on the intended daily cohort, enabling long-term reliability for ongoing API integrations.

Why the Others are Incorrect

Journey Settings > No re-entry (A)
controls whether contacts can re-enter after exiting but does not address evaluating only new API-added rows; it would still process all records if evaluation is set to all.

Contact Evaluation > Evaluate all records (B)
would re-scan the entire Data Extension each run, injecting previous subscribers unnecessarily and causing duplicate reminders.

Journey Settings > Use email attribute from Contacts (D)
relates to personalization or attribute resolution but has no impact on which records are evaluated for entry.

References
Salesforce Help – Journey Builder Contact Evaluation:
Trailhead – Journey Builder Advanced Configuration
Salesforce Documentation – Data Extension Entry Sources:

Explanation:

Here’s the logic:

The team has very little coding experience.

Today they use Excel + VLOOKUP to segment, then import — so they’re used to a visual, non-technical workflow.

They want long-term self-sufficiency in segmentation inside Marketing Cloud.

✅ Why Data Filters (A)
Data Filters in Email Studio:

Use a drag-and-drop UI (no SQL required).
Let you build segments based on Data Extension fields (e.g., demographics, behavior, flags).
Can be saved and reused as Filtered Data Extensions.
Are a natural upgrade path from “Excel filtering” to in-platform segmentation.

This is exactly what a non-technical marketing team needs.

❌ Why not the others

B. Attribute Groups
These define data relationships in Contact

Explanation:

Why this is correct:
The customer is a B2B organization that wants to trigger a customized journey for key accounts as soon as contacts associated with those select accounts are created.
Marketing Cloud Connect supports Salesforce Data Entry Source directly on the Account object.
You can create a journey with:

Entry Source → Salesforce Data
Object → Account
Trigger → “When a record is created or updated”
Filter → Account Name IN (list of key accounts) OR Account Type = “Key Account”, etc.

When a new Contact is added to one of those filtered Accounts (or when the Account itself meets the entry criteria), the Account record enters the journey.
Inside the journey, you can immediately use a Contact Data entry event or Related Data (via Data Relationships) to pull in all related Contacts on that Account and send the personalized welcome/nurture sequence to every time a new contact is added to one of the key accounts.
This is the native, lowest-setup way to accomplish account-based journey triggering.

Why the others are wrong:

A. Salesforce Campaign Entry Source on the Lead Object
Campaign entry only works when someone is added to a Campaign, and it is Lead- or Contact-based, not Account-based.

B. Salesforce Data Entry Source on the Contact Object
This would trigger one journey per Contact, not one coordinated journey per key Account. It also loses the account-level context the customer wants.

D. Welcome Email Configuration on the Account Object
There is no such thing as “Welcome Email Configuration” in Marketing Cloud Connect.

References
Salesforce Help – Salesforce Data Event in Journey Builder: (“You can select Account, Opportunity, Case, or any custom object as the entry source”)
Trailhead – Marketing Cloud Connect > Account-Based Journeys module
Marketing Cloud Connect Guide – “Use Account object entry to initiate account-based marketing journeys when contacts are added to strategic accounts”

Explanation:

✅ Why B is correct
When using a File Drop Automation, Marketing Cloud automatically captures the actual filename of the dropped file and passes it into downstream activities (like an Import Activity).
To take advantage of this, the Import Activity must use:

%%BASEFILENAME_FROM_TRIGGER%%

This token tells Marketing Cloud to:
Use the filename of the file that triggered the automation
Regardless of what the exact name is
As long as it matches the file pattern in the File Drop folder (e.g., starts with thankyou_customers)

This is exactly what NTO needs since the filename changes but has a consistent prefix.

❌ Why the other options are incorrect

A. %%AUTOMATED_FILENAME%%
Not a valid token for Import Activities in File Drop Automations.

C. Filename is automatically passed to Import Activity with File Drop Automations
Not true by itself.
You must explicitly reference it in the File Naming Pattern using the correct token.

D. Check the “Use filename from Automation” checkbox
No such option exists for Import Activities in File Drop Automations.

✔️ Final Answer
B. Set File Naming Pattern to %%BASEFILENAME_FROM_TRIGGER%%