Comprehensive and Detailed Explanation:

The correct answer is B — Create a new data extension and link it to the other data extension.

Best practice is to separate different data streams into different Data Extensions and use relationships (via Contact Builder Attribute Groups) to link them logically.

This allows independent updates from different sources without risking overwriting primary contact data.

❌ Why others are wrong:

A: Adding more fields to the main DE would make the model heavy and harder to manage, especially with separate feeds.

C: Salesforce Data Extensions are specific to CRM integration and not mentioned here.

D: New populations are used when contacts are fully separate audiences, which is not the case here (it's the same contact base).

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Contact Builder Data Relationships:

"Use separate data extensions for distinct types of information and create relationships between them to build a scalable contact data model."

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

—

Field-Level Encryption in Marketing Cloud encrypts specific fields at rest but restricts operations such as filtering, querying, or segmentation on those fields. You cannot perform SQL queries or create filtered sends directly using encrypted fields.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Field-Level Encryption Overview

→ "You cannot use encrypted fields in segmentation activities, query activities, or filters in Marketing Cloud. These fields are encrypted at rest and are only decrypted at send time."

—

Marketing Cloud Connect allows users to send emails directly to Salesforce Report audiences without needing to sync all custom objects into Marketing Cloud. This method minimizes setup and allows continued use of existing Salesforce reports.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect: Send to Salesforce Reports

→ "Use Salesforce Reports as an audience for sends from Marketing Cloud without syncing all Salesforce data."

Source: Salesforce Help – Marketing Cloud Connect Overview

→ "Marketing Cloud Connect enables sending emails to Leads, Contacts, Campaigns, and Reports directly from Marketing Cloud."

—

A Scheduled Automation using a Send Activity is ideal for sending emails to a data extension that is regularly updated. This approach allows for efficient and timely sends without the overhead of journey management, making it suitable for periodic newsletters with dynamic subscriber lists. ​

To centralize analytics data from Marketing Cloud, Sales Cloud, and a third-party warehouse service for efficient analysis and to drive better return on investment (ROI) and growth, Datorama (now part of Salesforce Marketing Cloud Intelligence) is the recommended product.

Datorama Overview : Datorama is a marketing intelligence platform that integrates data from multiple sources, including Marketing Cloud, Sales Cloud, and external systems like third-party data warehouses. It provides advanced analytics, visualization, and reporting capabilities to measure campaign performance, optimize ROI, and drive growth.

Why it fits the use case :

Centralized Analytics : Datorama can ingest and harmonize data from Marketing Cloud (email, SMS, push metrics), Sales Cloud (CRM data), and third-party warehouse services, creating a unified view of marketing performance.

Efficient Analysis : It offers pre-built dashboards, AI-driven insights, and customizable reports to analyze campaign effectiveness across channels.

ROI and Growth : Datorama’s ability to correlate marketing activities with sales outcomes (via Sales Cloud integration) and external data helps NTO identify high-ROI campaigns and opportunities for growth.

Why the other options are incorrect:

A. Web Analytics Connector : This connector integrates Marketing Cloud with web analytics platforms like Google Analytics to track web behavior. It is limited to web data and does not provide comprehensive cross-platform analytics or integration with Sales Cloud and third-party warehouses.

B. Report Studio : Report Studio does not exist as a standalone Salesforce product. Marketing Cloud’s native reporting tools (e.g., Email Studio Reports) are limited and cannot centralize data from Sales Cloud or external systems.

C. Interaction Studio : Interaction Studio (now part of Salesforce Marketing Cloud Personalization) focuses on real-time personalization and customer journey orchestration. While it can use data for personalization, it is not designed for centralized analytics or ROI analysis across multiple platforms.

Exact Extract from Salesforce Documentation:

Datorama Overview : "Marketing Cloud Intelligence (Datorama) connects and unifies data from Marketing Cloud, Sales Cloud, Service Cloud, and external sources to deliver actionable insights. It helps marketers optimize campaigns, improve ROI, and drive growth through advanced analytics and AI." (Source: Salesforce Help - Marketing Cloud Intelligence (Datorama) )

Cross-Platform Integration : "Datorama integrates with Salesforce platforms and third-party data sources to provide a holistic view of marketing performance, enabling data-driven decisions." (Source: Salesforce Help - Datorama Integration )

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 C — Data Extract with the Tracking Extract type > File Transfer from Safehouse > File Transfer unzip > Import File.

Tracking Extract Activity pulls detailed email event data, including 'Not Sent' events, into a compressed file (.zip).

You need a File Transfer Activity to move the file from the Safehouse and unzip it.

After unzipping, Import Activity loads the extracted data into a Data Extension where queries can run.

❌ Why others are wrong:

A and B: Data Extension Extract type is for DE records, not tracking events like Not Sent.

D: Data Factory Utility is not part of the standard Automation Studio activities for these operations.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Tracking Extract and Automation Studio:

"Use Tracking Extract to retrieve event-level data, including Not Sent events, then use a File Transfer Activity to unzip and import the extracted data for analysis or reporting."

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

—

In Marketing Cloud, if multiple BUs need access to the same data (like Product Information), the best practice is to store and manage the data extension in the top-level (Parent) BU and share it with the Child BUs using Shared Data Extensions.

This avoids duplication, ensures consistency, and simplifies data management.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Shared Data Extensions

→ "Shared Data Extensions enable parent business units to share data extensions with one or more child business units for consistent access and management."

—

Comprehensive and Detailed Explanation:

The correct answer is D — How to determine engagement.

Before you can generate a targeted audience for a campaign (like a discount), you must clearly define what "engaged" means (e.g., opened 2+ emails in 30 days, clicked 1+ email, etc.).

Only after you define engagement criteria can you accurately query or filter your audience.

❌ Why others are wrong:

A, B, and C are campaign details, but none impact how you technically define and segment the audience itself.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Audience Segmentation Planning:

"Clearly define segmenting criteria (e.g., engagement behavior) prior to audience selection to ensure correct targeting."

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

—

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."

—