_Send Data Views are built-in system tables in Marketing Cloud that capture detailed tracking data across multiple channels including Email, SMS, and Push. They can be queried via SQL Query Activities to extract insights about sends, clicks, opens, bounces, and more.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Views in Marketing Cloud

→ " _Send Data Views provide detailed tracking data for sends across all messaging channels, including Email, Mobile, and Push. Query these views for advanced reporting. "

—

Data Views are system tables in Marketing Cloud that update in near real-time and provide detailed email tracking information such as sends, opens, clicks, bounces, and unsubscribes. They are ideal for custom queries and reports with an hourly refresh frequency through Automation Studio.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Views

→ " Data Views are system-generated tables that provide event-level data for sends, opens, clicks, bounces, and more, updated near real-time. "

Source: Salesforce Help – Automation Studio Query Activities

→ " Data Views can be queried every hour through Automation Studio for up-to-date reporting. "

—

Comprehensive and Detailed Explanation:

The correct answers are A and C.

A — If responses are not received within the configured Conversation Window (e.g., 30 mins, 1 hour), MobileConnect treats them as unrelated and sends the default response.

C — If a Next Keyword is not specified on the outbound message, MobileConnect has no instruction for how to handle a reply, so it falls back to the default keyword response.

❌ Why others are wrong:

B: The Conversation Window is based on minutes/hours, not 24 hours.

D: If a response contains " stop, " it triggers an opt-out process, not a fallback default keyword response.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — MobileConnect Conversation Window and Next Keyword Setup:

" Ensure that outbound messages include a configured Next Keyword to direct subscriber responses. Responses received outside the Conversation Window are treated as unrelated and routed to the default keyword response. "

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_ms_conversation_window.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 )

—

Comprehensive and Detailed Explanation:

The correct answer is B — Use Tracking Extract, File Transfer, and Import activities from Automation Studio to inject the subscribers into a data extension used as an Entry Source by Journey Builder.

Tracking Extract Activity allows the extraction of bounced or held subscribers’ data (bounce reasons like " Held " ).

File Transfer Activity moves the extracted file into the Import directory.

Import Activity loads the file into a Data Extension, which can then be used as the entry source for a re-engagement journey via SMS.

❌ Why others are wrong:

A: SQL Query only works if the data is already in a Data Extension; Held status bounce data typically resides in Tracking Extracts.

C: CloudPages Entry Source is incorrect — you want an automated process for SMS.

D: API Event would require custom API calls, but there ' s no mention of development resources.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract Activity:

" Use a Tracking Extract Activity to pull tracking data, such as bounces or held status, into a file that can be imported into a data extension for use in journeys or reports. "

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

—

✅ Comprehensive and Detailed Explanation:

B (Publication List) allows subscribers to opt down or up in terms of subscription types. Customers indicating product interests and preferred messaging frequency would fit into Publication List management.

C (Auto-Suppression List) can exclude certain groups or preferences at the message send level automatically, especially if customers opt-down or unsubscribe partially.

❌ Why Others Are Incorrect:

A : Suppression Lists are manually managed and aren ' t dynamically tied to preferences.

D : Domain Exclusion blocks entire domains (e.g., gmail.com) — not individual preference management.

Exact Extract:

Salesforce Help: Publication Lists Overview

" Publication lists manage opt-ins and opt-outs at a more granular level, allowing customers to control which messages they want to receive. "

Salesforce Help: Auto-Suppression Lists

" Auto-suppression lists automatically prevent messages from being sent to specific subscribers based on business rules and preferences. "

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

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

Comprehensive and Detailed Explanation:

The correct answer is D — A Sender Authentication Package (SAP) should be used for Cloud Kicks.

SAP provides a dedicated IP, Private Domain, DKIM, and SPF alignment, critical for brand deliverability and reputation.

Since Cloud Kicks will operate with its own brand identity, even under the same parent org, setting a distinct SAP ensures inbox placement and avoids shared reputation issues.

❌ Why others are wrong:

A: NTO already has an SAP; Cloud Kicks needs its own setup.

B and C: Private Domains without full SAP (dedicated IP, DKIM, SPF) are not sufficient alone for full brand reputation management.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Sender Authentication Package Overview:

" Use the Sender Authentication Package (SAP) to configure custom sending domains, dedicated IPs, and authenticated email, ensuring maximum deliverability and brand identity. "

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

—

To enable a web form to upsert rows into a Marketing Cloud data extension via the REST API, the consultant must create an installed package in Marketing Cloud with appropriate permissions. The correct approach is to ensure the package scope includes Read and Write permissions for data extensions .

Installed Package Overview : In Marketing Cloud, an installed package is used to manage API integrations by providing a client ID and client secret for authentication. The package defines the scope of permissions for API operations, such as accessing or modifying data extensions.

Why Read and Write Permissions are needed :

Read : Allows the API to retrieve data from the data extension (e.g., to check for existing records during an upsert).

Write : Allows the API to insert or update records in the data extension (the upsert operation).

Implementation :

Create an installed package in Marketing Cloud Setup under Platform Tools > Installed Packages .

Add an API integration component (e.g., Server-to-Server or Web App) and configure the scope to include Data Extensions: Read, Write .

Provide the client ID and client secret to the web developer team to authenticate API calls securely.

Why the other options are incorrect:

A. Enable the package for all business units in the Marketing Cloud account : While enabling the package for all business units might be relevant in an Enterprise 2.0 account, it is not the primary requirement. The focus is on ensuring the correct permissions (Read and Write) for the data extension, not necessarily enabling it across all business units unless specified.

B. Create a separate installed package for each individual web form : Creating separate packages for each web form is unnecessary and inefficient. A single package with the appropriate scope can handle multiple API integrations, including multiple web forms, as long as the permissions are correctly configured.

C. Instruct the web team to store the client ID and secret in the client-side code : Storing the client ID and secret in client-side code (e.g., JavaScript in the browser) is a security risk, as it exposes sensitive credentials to end users. Instead, these credentials should be stored securely on the server-side and used in server-to-server API calls.

Exact Extract from Salesforce Documentation:

Installed Packages for API Integration : " Create an installed package to generate a client ID and client secret for API integrations. Specify the scope of permissions, such as Data Extensions Read and Write, to control what the integration can access. " (Source: Salesforce Help - Create an Installed Package )

Data Extension API Permissions : " To upsert rows into a data extension via the REST API, the installed package must include Read and Write permissions for Data Extensions to allow retrieving and modifying records. " (Source: Salesforce Developer - REST API Data Extension Endpoints )

You would:

Use an Engagement Split in Journey A to track who engaged (opened or clicked).

After the Engagement Split, capture the engagement decision (typically Boolean) into an attribute or Data Extension.

Then use Automation Studio to query the JourneyActivity data views for those who engaged and inject them into Journey B.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Engagement Split Activity

→ " The Engagement Split activity evaluates contacts based on interactions with an email activity, such as opens or clicks. "

Source: Salesforce Help – Journey Activity and Data Views

→ " Query JourneyActivity Data Views to retrieve information about contact flow and outcomes, including engagement split results. "

—

✅ Comprehensive and Detailed Explanation: In a Multi-Org connection model, one Marketing Cloud instance can connect to multiple Salesforce CRM instances. However, once upgraded to Multi-Org, the setting is permanent and cannot be reverted. This is a critical consideration when planning long-term system architecture.

❌ Why Other Options Are Incorrect:

A: Shared Data Extensions are unrelated to Multi-Org setup.

B: Custom profile centers are still often needed to manage preferences across different organizations.

D: Existing accounts can be upgraded after careful planning and approval from Salesforce.

Exact Extract: Salesforce Help: Marketing Cloud Connect Multi-Org Considerations

" After Multi-Org is enabled, you cannot revert to Single-Org. Carefully consider this configuration before proceeding. "

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