Marketing Cloud Next requires an authenticated sending domain for branded email delivery. The domain is configured under Unified Messaging and authenticated through DNS records supplied by Salesforce. DKIM is a core part of this authentication process.

Salesforce states that Marketing Cloud Next uses Unified Messaging for outbound email and that an activated authenticated domain is required for email sending. Current Marketing Cloud Next DKIM keys are 2048-bit by default, and Salesforce uses outbound CNAME records to establish the DKIM authentication chain. Once the domain is active, From addresses using that domain can be configured for legitimate branded delivery.

A tracking domain serves a different purpose: it supports branded links, redirect tracking, or related channel tracking functionality. It doesn't substitute for the authenticated email-sending domain. An "Authorized domain" verified solely by an ownership TXT record isn't the Marketing Cloud Next sending-domain configuration described by Salesforce.

The uploaded bank correctly identifies A. Salesforce's May and August 2026 documentation confirms that an authenticated domain is mandatory for Marketing Cloud Next sending and that DKIM authentication uses generated DNS records.

Study Guide Reference: Platform Setup and Governance → Unified Messaging Setup → Authenticated Sending Domains and DKIM.

===============

The critical word is initial . Marketing Cloud Next Business Units provide organizational separation for regions, brands, product lines, or other marketing divisions, but their data isolation is enforced through Data 360 Data Spaces. Salesforce establishes a one-to-one relationship between a Business Unit and a Data Space: a Business Unit can map to only one Data Space, and that Data Space can't be associated with another Business Unit.

More importantly, Salesforce's Business Unit setup instructions specify that before creating the initial Business Units, the organization must already have two or more Data Spaces . Therefore, for North American and European environments requiring segregation, the consultant first establishes the separate Data Spaces. The Business Units can then be created and mapped to those unique Data Spaces, with their associated marketing workspaces and content.

Option B represents an important subsequent configuration but isn't the prerequisite initial step. Option C addresses content organization but by itself doesn't establish the required data boundary.

The master bank likewise identifies A.

Study Guide Reference: Platform Setup and Governance → Business Units in Marketing Cloud Next → Data Spaces and Business Units.

===============

The Communication Subscription DMO represents the category or purpose of marketing communication itself. Examples include Product Updates, Weekly Deals, Newsletters, Promotions, or Events. Salesforce's Marketing Cloud Next documentation directs marketers to create a communication subscription for each category of marketing content they send.

After creating a Communication Subscription, one or more channel types—such as Email, SMS, RCS, or WhatsApp where supported—can be associated with that subscription. This channel relationship is represented separately through the Communication Subscription Channel Type model.

Communication Subscription Consent , by contrast, stores the individual's actual consent state in relation to the relevant subscription/contact-point/channel context. It doesn't define the communication category itself.

Therefore, C correctly identifies the object representing the subscription concept that recipients can choose to receive or decline.

The source bank keys C. Salesforce's official documentation states that a communication subscription should be created for each category of marketing content, such as product updates, and that communication channels are then added to that subscription.

Study Guide Reference: Consent → Communication Subscription Data Model → Subscription, Channel Type, and Subscription Consent.

===============

Salesforce's current Conversational Email implementation guide lists essentially the same five activities shown in option C . First, configure the human representative escalation experience in Service Cloud and Omni-Channel. Second, configure an Agentforce Service Agent capable of handling email conversations. Third, enable and configure Conversational Email in Unified Messaging for the applicable sending address. Fourth, create the Conversational Email campaign and its flow. Finally, monitor engagement, routing, resolutions, and agent escalation outcomes.

Salesforce emphasizes that the human escalation experience should be configured before Conversational Email is enabled, because customers must have a supported path to a human representative when the AI agent can't resolve an inquiry. Service Agents are likewise a formal prerequisite because Agentforce provides the automated interpretation and response capability.

Option A introduces a transactional API endpoint that isn't a standard implementation requirement. Option B relies on Journey Builder and Marketing Cloud Connect concepts that aren't part of the Marketing Cloud Next Conversational Email setup sequence.

The uploaded source correctly identifies C.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Agentforce, Service Cloud, Escalation, and Monitoring.

The Forms Engagement dashboard is specifically designed to provide an aggregate view of Marketing Cloud Next form performance. Salesforce's current Reporting in Marketing Cloud Next reference describes the Forms Engagement dashboard as a big-picture view of form KPIs that can be filtered by date, public title, and other attributes . That wording aligns directly with this scenario.

The Landing Page Engagement dashboard instead measures landing-page performance. Although the forms may be embedded on landing pages, the marketing manager is asking to compare the performance of the forms themselves. Campaign Performance provides higher-level campaign analysis across multiple assets and interactions but isn't the specialized dashboard for form-level KPIs.

Typical form analytics can help marketers understand submission activity and compare forms used across campaigns. Because the requirement explicitly calls for a high-level view across several gift-finder forms and filtering by public title, Forms Engagement is the exact reporting surface Salesforce documents for this purpose.

The uploaded master bank also identifies option B.

Study Guide Reference: Analytics and Performance Insights → Reporting in Marketing Cloud Next → Forms Engagement Dashboard.

===============

An Actionable List is the correct audience mechanism when marketers need to target a fixed, specifically selected collection of existing Leads or Contacts without building a Data 360 segment. Salesforce describes Actionable Lists as static collections suited to known individuals, such as imported event attendees or other deliberately selected contacts. An Audience Flow can use a List as its audience source.

For personalization, Content Variables provide dynamic placeholders whose values can be populated by Flow at runtime. Salesforce allows content variables to map to data sources available to Flow, including Salesforce records and other connected data. This makes it possible to supply attributes such as First Name and Account information during message execution.

A Data Graph is designed primarily as a personalization data source and isn't itself the appropriate fixed-list audience source described here. Option A unnecessarily introduces a marketing object and AMPscript when the records already exist as Contacts.

The uploaded master bank identifies C. Salesforce confirms that Audience Flows support List sources and that Actionable Lists represent fixed audiences.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Actionable Lists and Content Variables.

===============

Marketing Cloud Next provides on-canvas Flow Analytics for supported marketing-flow elements. Salesforce identifies this capability as On-Canvas Insights and states that recent performance metrics for active and completed flows can appear directly on the flow canvas. To expose those insights, marketers select the relevant flow element and enable or review insights from its Analytics tab.

For messaging elements such as Send Email Message, these analytics allow marketers to evaluate element-level execution and engagement without relying on low-level automation logs. Depending on the edition and configuration, detailed Flow Performance analytics are powered by Tableau Next, and users may require the Tableau Next Included App Business User permission set.

Debugging the flow is useful for validating logic, variables, and execution paths during development, but it isn't the intended interface for production engagement metrics. Flow Interview logs similarly focus on flow execution and troubleshooting rather than marketer-facing email engagement analysis.

The uploaded master keys A. Salesforce's current Flow Builder documentation specifically states that On-Canvas Insights are enabled from the Analytics tab of a flow element's editing panel .

Study Guide Reference: Analytics and Performance Insights → Flow Analytics → On-Canvas Insights and Messaging Element Performance.

===============

Marketing Cloud Next supports both Salesforce Record and Offer as native email personalization data sources. Salesforce Record is designed to surface current business information from Salesforce objects. Salesforce specifically notes that marketers can add a Salesforce Record data source and reference Salesforce object fields directly in email content.

That makes it appropriate for a recipient's assigned sales representative when the representative relationship is maintained in Salesforce/Agentforce Sales data.

The Offer data provider is specifically designed for promotions. Salesforce states that marketers can add an Offer as an email data source and use merge fields for values such as the offer name, description, or coupon code . It also supports multiple offer providers and conditional targeting based on customer attributes.

An Apex Class would be unnecessary custom logic for retrieving an ordinary Salesforce business attribute. A Data Graph also isn't the natural mechanism for a Marketing Cloud Next-managed, time-sensitive offer code when the purpose-built Offer data source exists.

The uploaded bank identifies A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization Data Sources → Salesforce Record and Offer.

===============

Data 360 supports source-record filters directly on identity resolution rulesets . These filters act as preprocessing gates that determine which records from the ruleset's primary DMO enter that particular unification pipeline.

This is exactly the appropriate architecture when two populations share the same primary DMO but must be unified independently. The consultant can configure criteria distinguishing B2B from B2C records and apply complementary filters to the respective rulesets.

Salesforce specifically identifies separation of B2B and B2C populations as a valid ruleset-filter use case. For example, records can be filtered using an account type, customer type, record type, or other partition-level attribute so that business records don't enter the consumer ruleset and vice versa.

Creating separate DMOs simply to achieve identity-processing isolation isn't necessary when the records properly belong to the same canonical Individual model. Filtering source DLOs also places the separation at the wrong architectural layer because identity-resolution filtering is supported directly at the ruleset level.

The uploaded bank keys B. Salesforce's current ruleset documentation explicitly recommends filters for broad partition-level segregation, including B2B versus B2C scenarios.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Ruleset Source Filters.

===============

Unified Engagement History is designed to give Salesforce users a consolidated view of marketing engagement directly within CRM record pages. Salesforce instructs administrators to turn on Unified Engagement History Dashboards and then add the appropriate dashboard component to Account, Lead, Contact, and Opportunity record pages.

This provides sales and marketing users with contextual engagement information without requiring them to leave the CRM record. Marketing engagement can include the individual's interactions with emails, forms, web activity, campaigns, and other Marketing Cloud Next touchpoints represented through the unified engagement model.

The Email Engagement dashboard is useful for aggregate email-performance analysis, but it isn't the specialized CRM-record-level engagement-history experience requested here. Similarly, the Website Engagement DMO alone only represents one class of behavior and wouldn't provide the combined email, form, and page-view history required by the scenario.

The uploaded master bank identifies B. Salesforce's current setup documentation explicitly states that Unified Engagement History components should be added to Contact and other CRM record pages to expose marketing engagement data to users.

Study Guide Reference: Analytics and Performance Insights → Unified Engagement History → CRM Record Page Integration.

===============