Comprehensive and Detailed Explanation:

Correct answers are A and B.

A — Large Data Extensions are required when handling tens or hundreds of millions of records. Regular Data Extensions have performance limitations.

B — Knowing the expected hourly API call volume is essential because Marketing Cloud has strict API rate limits. Bulk API usage must be planned carefully.

❌ Why others are wrong:

C: While time of day matters for planning, it’s not a discovery priority over licensing and scaling factors.

D: While it’s useful to know why they need 10 years of data, the technical feasibility depends first on license and API planning.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Large Data Extensions and API Limits:

"Use Large Data Extensions when working with millions of records to maintain performance. Understand API rate limits to ensure compliance with Marketing Cloud API usage policies."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_large_data_extensions.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is A — Data Filters.

Data Filters provide a drag-and-drop, no-code way to segment audiences based on profile attributes or behavior.

They allow marketing users without SQL or AMPscript knowledge to build audiences directly in Email Studio.

❌ Why others are wrong:

B: Attribute Groups are used for mapping relationships between data, not for audience segmentation.

C: Publication Lists manage opt-in/out preferences, not audience segmentation.

D: Query Activities require SQL coding, which the team lacks experience with.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Data Filters Overview:

"Data Filters allow users to segment data extensions based on attribute values and behavior using a simple drag-and-drop interface, without the need for coding."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_data_filters.htm )

—

The correct answer is C , because:

In Salesforce Marketing Cloud, when a subscriber's status changes to 'Held' , it means that Marketing Cloud has suppressed sending emails to that subscriber due to repeated soft or hard bounces.

Users cannot directly edit or re-enable subscribers marked as Held.

Instead, Salesforce Support must be contacted to review and re-enable those subscribers if appropriate (for example, if it was a temporary deliverability issue).

Salesforce official documentation states:

" Held Status : A subscriber is placed on Held status after a threshold of consecutive soft or hard bounces. To reactivate held subscribers, submit a case with Salesforce Support. Users cannot manually reactivate held subscribers themselves."

(Source: Salesforce Marketing Cloud - Subscriber Status Overview)

Important Points:

Held status is a safety mechanism to protect sender reputation and avoid deliverability issues.

Salesforce must verify that it is safe to re-enable these subscribers to prevent risking future blacklistings or IP reputation damage.

Why the other options are incorrect:

❌ A. Extract and Import as 'Active' :

You cannot change subscriber status from 'Held' back to 'Active' through data imports — importing won't override Held status .

❌ B. Mass update in Contact Builder :

Contact Builder cannot change the status of subscribers in the All Subscribers list — status is managed at the system level.

❌ D. SQL query to update 'Held' to 'Active' :

SQL queries cannot modify system-managed fields like subscriber status in the All Subscribers list.

Additional reference:

"Marketing Cloud Support can reset a subscriber's status to Active after evaluation. Self-service options are not available to update 'Held' statuses."

(Source: Salesforce Marketing Cloud Admin Guide - Managing Subscribers)

Thus, C is the correct and official answer.

The simplest and most efficient method to report on the number of Contacts is to schedule the built-in "Contacts Counts" Standard Report. This report summarizes the total number of Contacts and can be scheduled for automatic email delivery to stakeholders like the CMO.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Contact Count Standard Report

→ "The Contacts Counts report shows the number of Contacts in the account and can be scheduled to email automatically on a recurring basis."

Source: Salesforce Help – Standard Reports Overview

→ "Use Standard Reports like Contact Counts to quickly view and schedule basic statistics without needing custom queries or Automation Studio."

—

A File Drop Automation triggers automatically when a file is placed in a specified SFTP folder, allowing immediate processing. After importing the data, a SQL Query can segment the data based on specific criteria, preparing it for entry into a journey. ​

Comprehensive and Detailed Explanation:

The correct answer is D — Create and send to a sendable data extension containing those needed fields using a query activity.

Pre-populating a single sendable data extension with all necessary personalization fields eliminates the need for real-time lookups during sending.

It dramatically speeds up send processing because personalization is sourced directly from the send context.

❌ Why others are wrong:

A: Profile attributes are outdated and limited for handling many fields from multiple sources.

B: Send throttling slows down sends to control delivery rate — it doesn’t speed it up.

C: Lookup functions cause real-time database queries during send time, slowing down large sends.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Personalization and Send Performance:

"To improve send performance, include all required personalization attributes in the send context (Data Extension) rather than relying on AMPscript Lookups at send time."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_send_performance.htm )

—

Salesforce enforces a 24-hour rolling limit on standard API calls.

SOAP API calls (such as updating objects) count toward this limit.

The AMPscript function CreateSalesforceObject() internally performs a Salesforce API call and is also counted toward the Salesforce daily API limits.

Login Calls and Bulk API operations have separate limit tracking and do not typically count against the standard 24-hour API limit.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – API Request Limits and Allocations

→ "API requests that create, retrieve, update, or delete records count against your daily API call limits. This includes SOAP API and REST API requests."

Source: Salesforce Developer Documentation – CreateSalesforceObject() AMPscript

→ "The CreateSalesforceObject function uses Salesforce SOAP API calls internally, and these requests count toward Salesforce API limits."

—

✅ Comprehensive and Detailed Explanation:

A (Keyword opt-in and SMS Messaging) is ideal because attendees can text a keyword to opt-in, and SMS provides instant, mobile-friendly, time-sensitive alerts like safety notifications or room changes.

❌ Why Others Are Incorrect:

B : Email and Smart Capture are too slow for live event updates.

C : CloudPages require internet access and form submission — not practical for quick opt-ins at live events.

D : Existing email subscriptions are static, not event-specific or real-time.

Exact Extract:

Salesforce Help: MobileConnect Keyword Setup

"Keywords enable mobile users to opt in to receive SMS messages. MobileConnect supports using keywords for event-specific opt-ins."

════════════════════════════════════════════

Comprehensive and Detailed Explanation:

The correct answer is C — Scheduled Automation > Import Activity > Series of Query Activities > Series of Sends.

Scheduled Automation (set to run every day after file drop) automatically imports the file, segments the data via Query Activities, and sends emails.

No need for manual triggering because the file generation time is predictable.

This is the cleanest, most scalable setup.

❌ Why others are wrong:

A: File Transfer isn't needed if the file is directly available in the correct folder.

B and D: Triggered Automations are better for real-time, unexpected events — not predictable scheduled events.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Automation Studio Best Practices:

"Use scheduled automations when working with expected, time-based file imports and campaign sends to automate data processing and message delivery."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_best_practices.htm )

Comprehensive and Detailed Explanation:

Correct answers are B and D.

B — The subscriber key should be channel-agnostic (not tied to an email address or phone number).

D — If the external POS system is the source of truth, use its stable unique identifier as the Contact Key.

❌ Why others are wrong:

A: Contact Builder does not automatically generate subscriber keys; you must define them.

C: While merging duplicates is important, the question asks for initial best practices during setup, not ongoing maintenance.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Contact Key and Subscriber Key Best Practices:

"Use a stable, unique, non-channel-specific identifier as the Contact Key/Subscriber Key, preferably sourced from your system of record."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_contact_key_best_practices.htm )

—