Explanation:
In Marketing Cloud Engagement, when a subscriber's status is "Bounced," it means the platform has received a specific number of non-delivery notifications (bounces) indicating the email address is potentially invalid or experiencing a persistent issue. However, a user action, such as clicking a link in an email, is considered a definitive sign of engagement and confirms the email address is indeed active and reachable. The system prioritizes this positive, user-initiated engagement over the past bounce history.

Correct Option:

D. Status is changed to Active and the bounce count is set to Zero
A click on a link is the highest form of positive engagement and acts as a direct validation that the subscriber's email address is active and that the subscriber is receiving the emails.

Marketing Cloud automatically changes the status from Bounced to Active upon this interaction to ensure the subscriber continues to receive future sends.

The bounce count is reset to zero because the system has received proof that the email address is working, invalidating the previous bounce tally.

Incorrect Options:

A. Status is changed to Active and the bounce count is unchanged:
While the status changes to Active, the bounce count must be reset to zero. Keeping a non-zero bounce count would incorrectly imply a past issue that the recent click has proven to be resolved or erroneous.

B. Status is changed to Held for 72 hours and the bounce count is set to Zero:
The Held status is typically assigned when a user has a high number of soft or hard bounces before the click threshold is reached. A user-initiated click does not result in a temporary "Held" status; it results in an immediate and permanent (until the next hard bounce) Active status.

C. Status remains as Bounced the bounce count is unchanged:
This is incorrect. A click is a powerful signal of validation. Marketing Cloud is designed to optimize deliverability by immediately marking proven, engaged subscribers as Active, overriding the Bounced status.

Reference:
Salesforce Help Documentation on Subscriber Statuses and Lifecycle (Hard Bounces and Clicks)

Explanation:

The Email Form Content Block is a specific feature within Salesforce Marketing Cloud's Content Builder that allows you to embed a form directly into an email. The form is designed to collect customer feedback or other information without requiring the recipient to click a link and navigate to an external website.

Here's a breakdown of why the other options are incorrect:
A. Cloud Page Forms Content Block: This block is used to create and embed forms that submit data to a Cloud Page. While a Cloud Page can be used for feedback, it requires the user to click a link and navigate away from the email, which is contrary to the requirement.

C. Dynamic Content Block: This block allows you to display different content based on subscriber data. While it's powerful for personalization, it's not designed to collect data directly from a form within the email itself. It's used to show content, not gather information.

D. Reference Content Block: This block is used to reference content from an external source or another content block. It is a way to reuse content, not to create a functional form for data collection.

By using the Email Form Content Block, Northern Trail Outfitters can embed a simple feedback form (e.g., a star rating or a short survey) directly into the post-purchase email, making it easy for customers to provide feedback with a single click and without leaving their inbox.

Explanation:

Email clients vary widely in how they render fonts, and most do not support custom fonts reliably. The best practice is to use web-safe fonts (like Arial, Georgia, or Verdana) that closely resemble the brand’s custom font.

This ensures:

✅ Consistent rendering across devices and email clients

📱 Accessibility and responsiveness

📧 Deliverability and performance, since text remains selectable and searchable

If brand fidelity is critical, designers can use images sparingly for headers or logos—but never for body text, as it harms accessibility and load times.

📘 Why not the other options?

B. Build an email as one image
Hurts accessibility, increases load time, and risks deliverability issues. Text in images can’t be read by screen readers or indexed.

C. List the custom font in HTML
Most email clients ignore custom fonts unless they’re web-hosted and supported (which is rare). Fallback fonts are still needed.

D. Use multiple images for text
Same issues as option B, plus layout complexity and poor mobile responsiveness.

🔗 Reference:
Salesforce Marketing Cloud Email Design Best Practices
Litmus Guide to Email Font Support

Explanation:
The administrator is setting up a new SFTP user account, which is crucial for secure, automated file transfers (imports and exports) between Marketing Cloud and external systems. SFTP accounts are highly sensitive and require strict adherence to security and configuration policies. The considerations for setting up a new user revolve around the default username, password strength, and the activation status of the account upon creation.

Correct Options:

B. Minimum password length is 12 characters.
SFTP account passwords are subject to both the Marketing Cloud account's general password policies and additional server-side FTP requirements. The complexity requirements often mandate a minimum length of 12 characters and can include other rules (e.g., no reuse of the most recent password) to ensure the security of the file transfer channel.

D. Once created, the user will need to be activated in order to use the SFTP.
When a new SFTP user is created in Setup > Data Management > FTP Accounts, their status is initially often set to Pending. The administrator or system usually needs to wait a few moments or refresh the page for the user's status to change to Enabled or Active before the credentials can be used to successfully log in and transfer files via an SFTP client (like FileZilla).

Incorrect Options:

A. By default, the username is the MID for the current Marketing Cloud MID.
While the first SFTP user created for an account historically defaulted to the Business Unit's Member ID (MID), modern setups allow the admin to create a custom username when adding a new SFTP user account. For additional users, the username is not necessarily the MID, and for all users, the system often suggests a username which is not just the MID. The primary username for the Enhanced SFTP is often set system-wide for the BU.

C. By default, the password will be the password of the logged-in user.
This is incorrect and would be a significant security flaw. When creating a new SFTP user, the admin is required to enter and confirm a new, separate password for the SFTP account, which must meet the minimum complexity requirements. The password is not automatically inherited from the admin's personal Marketing Cloud login credentials.

Reference:
Salesforce Help Documentation on Creating SFTP User Accounts and Password Requirements

Explanation:
The Path Optimizer feature allows an admin to test different paths in a journey and automatically send contacts down the best-performing path after a defined period or interaction count. To use the "Holdback" feature, which reserves a portion of the audience (60% in this case) until a winner is declared, the journey must be designed for a single evaluation and must have a clear mechanism for determining the winner.

Correct Options:

C. Run Once schedule type:
The Holdback feature only works with the Run Once schedule type (or a scheduled one-time send). This is because the Holdback percentage relies on the journey having a fixed, known audience from the start that can be divided and held. If the journey were running on a repeating schedule or a continuous stream of contacts (like an API entry), the total audience size would constantly change, making the Holdback percentage calculation and consistent winner selection impossible.

D. Winner evaluation:
This setting defines the mechanism and criteria for how the "winner" path will be selected (e.g., clicks, opens, or manual selection) and after what period (time or volume). The Holdback contacts will only proceed down the chosen path after this evaluation is complete. Therefore, setting the evaluation criteria is a prerequisite for using the Holdback feature.

Incorrect Options:

A. Data Extension entry source:
While a Data Extension is a common and necessary entry source for a Run Once journey, the specific type of entry source itself (Data Extension vs. API Event) is not the setting that enables the Holdback feature. The enablement is tied to the Run Once schedule.

B. Journey re-entry settings:
Re-entry settings (whether a contact can re-enter immediately, after a delay, or never) pertain to how a contact interacts with the journey over time. Since the Holdback feature is tied to a single evaluation run (the Run Once schedule), re-entry settings are irrelevant to enabling the initial holdback percentage.

Reference:
Salesforce Help Documentation on Journey Builder Path Optimizer Holdback Feature