Explanation:

📝 Summary:
NTO is seeing unsubscribe reasons linked to RMM, a feature they don't use. This occurs because modern email clients like Gmail offer their own unsubscribe buttons. When used, these clients send an automated request that Marketing Cloud processes and categorizes as an "RMM-related" unsubscribe, even if the full RMM feature isn't activated in the account.

✅ Correct Option:

A. 🧾 List Unsubscribe header
✔️ This email header allows ISPs (like Gmail) to add an unsubscribe button within their own interface.
✔️ When a subscriber uses this ISP button, it triggers an automated unsubscribe request back to Marketing Cloud.
✔️ The system logs this automated request type under an "RMM" reason category by default, explaining why NTO sees these reasons without having RMM configured.

❌ Incorrect Options:

B. ⚙️ Profile Center Unsubscribe
➡️ This is a direct link to the subscriber's preference center managed within Marketing Cloud.
➡️ Unsubscribes happen on a Salesforce-hosted page, and the reason is recorded as a standard "Profile Center" unsubscribe.
➡️ It does not generate an automated request that would be misclassified as an RMM event.

C. 🔗 Universal Unsubscribe
➡️ This is a one-click link that immediately unsubscribes the subscriber from all sends.
➡️ This action is handled directly by Marketing Cloud's core unsubscription service.
➡️ Like the Profile Center, it is a direct action and does not involve the ISP-triggered automation that causes RMM-like reason codes.

📚 Reference:
Salesforce Official Documentation on Reply Mail Management (RMM) and List-Unsubscribe.

Explanation:

This question checks how shared templates should be permissioned in Marketing Cloud to keep branding centrally controlled while allowing broad reuse. It focuses on which permission setting lets business units use a global, on-brand template without being able to change it and accidentally break brand standards.

✔️ Correct Option:

✔️ B. Select the View and Send permission option.
View and Send allows users in all business units to access the template, insert it into emails, and send campaigns while keeping the original template locked from editing. This preserves global branding standards as defined by the top-level team. Central updates to the shared template automatically flow to everyone, ensuring company-wide consistency and reducing the risk of off-brand local changes.

❌ Incorrect options:

❌ A. Select the Edit Globally permission option.
Edit Globally would let users modify the shared template itself, increasing the chance that different teams change logos, colors, or layout and break the global brand standards. It undermines the purpose of a centrally maintained template designed to keep all business units aligned on consistent branding.

❌ C. Make a copy in each business unit to allow local edits.
Creating local copies in every business unit leads to many variations of the template, each potentially drifting from brand guidelines over time. It also makes global updates difficult, as changes must be replicated manually in each unit. This approach conflicts with the goal of maintaining one centralized, always-on-brand template.

🔧 Reference:
⇒ Salesforce Help: Shared Content and Templates
→ Confirms how shared folders and permissions are used to control access and editing of centrally managed content and templates in Marketing Cloud Engagement.

Explanation:

When collecting information (like user corner information) from users who come from social media channels, marketers typically include URL parameters in the links they post on social media (like UTM tags or custom query parameters).

To capture that information in Marketing Cloud, you would:
Create a CloudPage (via Web Studio / Landing Pages)
Configure it to read the query parameters from the URL
Use AMPscript or Server-Side JavaScript to store that data into a Data Extension

This allows you to collect and track social users and store the metadata (e.g., source, campaign, or even corner-related info) for future email campaigns.

❌ Why the other options are incorrect:

A. Use Journey Builder to build an audience using AdStudio
→ Incorrect. AdStudio is used for advertising campaigns (Facebook, Google, LinkedIn), but not for collecting data or capturing query parameters.

C. Use an interactive form from Email Studio to collect this information
→ Incorrect. Email Studio does not support interactive forms directly in emails for collecting data (due to email client limitations). Forms are typically hosted on CloudPages, not embedded in emails.

📚 Salesforce Reference:
CloudPages (part of Web Studio) can be used to capture user information by using AMPscript to read and process URL query parameters.

Explanation:

Spam complaints harm sender reputation, so addressing repeat complainers is critical in Salesforce Marketing Cloud. For a subscriber consistently marking emails as spam, the marketer needs a solution to exclude them from future commercial sends while adhering to compliance and maintaining list integrity.

Correct Option: ✅ B. Add the subscriber to the auto-suppression list
The auto-suppression list blocks specific email addresses from receiving commercial emails across campaigns.
It’s designed for cases like repeat spam complaints, ensuring compliance with CAN-SPAM regulations.
This method is reversible and targeted, preserving the subscriber’s data in All Subscribers.

Incorrect Options:

❌ A. Use the complaint exclusion list on future sends:
There’s no specific “complaint exclusion list” in Marketing Cloud; this is a misleading option, as suppression is handled via auto-suppression lists.

❌ C. Delete the subscriber from All Subscribers:
Deleting removes the subscriber entirely, which may not be ideal if they could engage with non-commercial emails or if data retention is needed.

Reference:
Auto-Suppression Lists

✅ Explanation:

In this scenario, the daily customer feed includes only customers who are still active. This means:

1. If a customer drops out of the feed, they should also be removed from the target Data Extension.
2. To accomplish this, you need the import to clear out the existing data and replace it with the new day’s file.

That’s exactly what the Overwrite import option does:

1. Delete all existing records in the target Data Extension
2. Replace them with the new data from the file

This ensures the Data Extension always contains only the current active customers, with no outdated records lingering.

❌ Why the other options are incorrect:

A. Append
→ Incorrect. This would just add new rows to the Data Extension every day. Customers who are no longer active (missing from the feed) would remain, which breaks the requirement.

C. Add and Update
→ Incorrect. This would update existing records (if SubscriberKey matches) and add new ones — but it would not remove customers who no longer appear in the daily feed. So inactive customers would stay.

📚 Salesforce Reference:
“Use the Overwrite option if you want the target data extension to contain only the records in the import file. This clears out old records and replaces them with the new file contents.”

Source:
Salesforce Help: Data Extension Import Options