Explanation:
In Marketing Cloud MobileConnect, keywords must be unique within an Enterprise account. If the keyword “CELEBRATION” is unavailable, it usually means it is already in use elsewhere in the account, possibly in another Business Unit. Each keyword can only be active in one business unit at a time, preventing duplication across campaigns or regions.

Correct Option:

A — Keyword is used within another business unit
Marketing Cloud enforces uniqueness of keywords across the account. Even if the keyword is not used in the current Business Unit, if it exists in another Business Unit, it cannot be reused. This ensures that incoming SMS messages are correctly routed and prevents conflicts between multiple campaigns using the same keyword.

Incorrect Options:

B — Keyword is a reserved word
Reserved words are system-defined and typically include commands like STOP, HELP, or START. “CELEBRATION” is not a reserved word, so this is not the cause of the issue.

C — Keyword has too many characters
Marketing Cloud allows keywords up to 25 characters long. “CELEBRATION” is only 11 characters, so length is not the problem.

D — Keyword fails to meet content standards
Marketing Cloud does not restrict general words for content standards. Unless the keyword contains prohibited characters, it would not be blocked for content reasons. “CELEBRATION” is valid content.

Reference:
Salesforce Documentation – MobileConnect Keywords

Trailhead – Set Up SMS Messaging with MobileConnect

Explanation:
Parameter Manager in Salesforce Marketing Cloud allows centralized configuration of URL parameters (like UTM values) that are automatically appended to links. To apply the same utm_campaign value to every link inside one specific email or journey message while keeping it different for other emails, the parameter must be defined at the level that controls individual sends rather than globally or per subscriber.

Correct Option:

C. Email
The utm_campaign parameter should be configured at the Email level in Parameter Manager. This setting overrides any Account-level defaults only for that specific email send (or Journey Builder email activity). It ensures every tracked link in that single message receives the exact same Campaign Identifier needed for reporting, without affecting other emails.

Incorrect Option:

A. Subscriber
Parameter Manager does not support configuration at the Subscriber level. UTM values cannot be dynamically set per individual recipient in Parameter Manager; subscriber-specific personalization would require AMPscript or dynamic content instead.

B. Link
Parameter Manager does not allow configuration at the individual Link level. You cannot set different UTM values for specific links within the same email using Parameter Manager (Web & Mobile Analytics Connector would be needed for link-level granularity).

D. Account
Account-level configuration applies the same utm_campaign value to every email sent from the entire account/business unit. This is too broad when the requirement is to set a unique Campaign Identifier for only one specific campaign message.

Explanation:
Einstein Recommendations for Marketing Cloud requires behavioral and catalog data to generate product recommendations. This data is collected from a brand's website or mobile app and sent to Marketing Cloud for processing. The primary method for capturing this user interaction data is through a client-side JavaScript code snippet.

Correct Option:

B. Collect Tracking code:
This is the correct answer. The Collect Code (or Einstein Recommendations Collect Code) is a specific piece of JavaScript provided in the Einstein Recommendations setup. It must be implemented on the brand's digital properties (website/app). This code fires on page views and user interactions, sending behavioral data (e.g., product views, purchases) to Marketing Cloud to power the recommendation models.

Incorrect Options:

A. Google Analytics 360:
While Google Analytics 360 has an integration with Marketing Cloud, it is not the standard, native method for passing the specific user-interaction and catalog data required by the Einstein Recommendations service. Einstein relies on its own Collect Code for direct data ingestion.

C. CloudPages:
CloudPages are used to host web content and landing pages within Marketing Cloud. They are not a mechanism for passing external website data into Einstein Recommendations. Data collection happens on the client's own site via the Collect Code.

D. Web & Mobile Analytics:
This is a broad category or feature name, not a specific technical method. Within the Marketing Cloud context, "Web & Mobile Analytics" is the reporting module that displays data, but the data is collected via the Collect Tracking Code. This option names the destination/report, not the transmission method.

Reference:
The setup guide for Einstein Recommendations in Marketing Cloud explicitly details the implementation of the Einstein Recommendations Collect Code (a JavaScript tag) on the client's website to track visitor behavior and send data to Marketing Cloud.

Explanation:
The constraint is a fixed number of user licenses. A user on extended leave does not need active platform access, freeing up their license. The goal is to provide access to a temporary replacement without purchasing an additional license. The proper administrative action is to reclaim the inactive user's license and reassign it.

Correct Option (Presumed):

D. Deactivate the campaign manager's license and assign it to the new user:
This is the correct and efficient procedure. In Setup > Users, the admin can deactivate the user on leave. This frees up their license without deleting their historical data or user record. The admin can then use that now-available license to create and activate the new temporary user.

Incorrect Options (Common Distractors):

A. Delete the campaign manager's user and create a new user:
Deleting a user is a permanent action that can remove their association with historical activities (like sent journeys) and is generally not reversible. It is not the recommended method for temporary coverage. Deactivation is the non-destructive alternative.

B. Disable the campaign manager's user and create a new user:
"Disable" is not a standard term in this context. The standard actions are Activate/Deactivate. Even if this means deactivation, the core issue is that creating a new user would require a new license, which NTO does not have. You must free up a license first.

C. Transfer the campaign manager's permissions to a new user:
Permissions are assigned via roles, which can be copied. However, this does not solve the license constraint. A new user account consumes a license regardless of the permissions assigned. You cannot create a new user without an available license.

Reference:
Marketing Cloud user management documentation explains that user licenses are a pooled resource. To add a new user when all licenses are consumed, you must first deactivate an existing user to free up a license slot, then create the new user.

Explanation:
The core issue is a data discrepancy between an external database and Marketing Cloud subscribers after a daily automated import. The business needs a way to audit the import process to see if all records from the CSV file were successfully processed and added to the target data extension. This is a need for logging and verification, not for correcting the import mapping itself.

Correct Option:

D. Notification Settings within the Import File Activity:
This is the correct feature. Within an Import File activity in an Automation Studio automation, the Notification Settings allow an administrator to set up an email alert that is sent upon completion of the import. This notification includes a detailed log file as an attachment. This log specifies exactly how many records were processed, added, updated, or had errors, enabling NTO to monitor the success and volume of each daily import job.

Incorrect Options:

A. External Key within the Import File Activity:
The External Key is used to uniquely identify and update existing records in the target data extension. It is crucial for data integrity during an upsert operation but provides no monitoring or alerting functionality to report on the total number of records processed.

B. Run Completion within the File Drop Automation:
While you can set an automation to trigger another activity upon "Run Completion," this status only indicates that the automation finished running. It does not, by itself, provide a detailed log of how many records from the file were successfully imported versus rejected.

C. Runtime Error within the File Drop Automation:
Configuring an action for a "Runtime Error" would alert the team if the automation itself failed to execute (e.g., file not found, credential error). It would not trigger if the automation runs successfully but imports fewer records than expected due to data errors within the file.

Reference:
Marketing Cloud product documentation on Import File Activity configuration details the Notification Settings option, which states that upon completion, "a notification email is sent. This email contains a log file that details the import results."