The Email Engagement dashboard is the purpose-built dashboard for analyzing standard email performance metrics across Marketing Cloud Next sends. Salesforce's Marketing Performance Intelligence package includes preconfigured Email Engagement reports and dashboard components for common KPIs including Total Emails Sent, Open Rate, Click-Through Rate, Bounce Rate, and Opt-Out Rate.

The dashboard provides visualizations such as status bar graphs, time-based activity graphs, campaign click-engagement rankings, email-send-status views, and detailed activity tables. This allows marketers to evaluate messaging performance without having to construct a custom analytics model.

Campaign Performance is broader and focuses on campaign-level outcomes across associated marketing activity rather than being the specialized email KPI view requested here. Unified Engagement History serves another purpose: it surfaces marketing engagement alongside CRM records such as Contacts, Leads, Accounts, and Opportunities for sales and service users.

Therefore, B precisely matches the requirement for an easy-to-use, cross-send email analytics dashboard.

The uploaded master bank also identifies B. Salesforce's 2026 Marketing Cloud Next reporting documentation explicitly lists Open Rate, Click-Through Rate, Bounce Rate, and related metrics in the Email Engagement dashboard.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Email Engagement Dashboard.

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

The correct reconciliation strategy is Source Sequence , also described in newer Salesforce materials as Source Priority . This rule lets the consultant rank source systems from most trusted to least trusted when Data 360 must select a single representative value for a unified profile attribute.

In this scenario, Salesforce CRM has already been identified as the authoritative source for First Name. The consultant therefore places the CRM source first in the reconciliation priority. When a CRM value exists, Data 360 selects that value instead of choosing one from a lower-priority ecommerce, loyalty, or external source.

Most Frequent would select whichever value occurs most often among the linked records. That doesn't satisfy the requirement because multiple unreliable sources could outweigh the single trusted CRM value. A custom approach isn't required when source prioritization directly addresses the business rule.

The uploaded master bank identifies B. Salesforce Trailhead still describes this reconciliation method as Source Sequence , while current Help and architecture materials commonly use Source Priority for the same source-ranking concept.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Reconciliation Rules → Source Sequence/Source Priority.

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

An Omni-Channel flow is the appropriate mechanism because inbound customer conversations on Salesforce messaging channels are represented by Messaging Sessions and must be routed through supported messaging-routing infrastructure. Salesforce documents that an inbound Omni-Channel flow can use the Route Work action with the Service Channel set to Messaging and the routing destination set to an Agentforce Service Agent. This provides the supported handoff from the messaging channel to the autonomous agent while preserving the conversation context.

A record-triggered flow is not the standard routing mechanism for assigning an active messaging conversation to an Agentforce Service Agent. Although record-triggered flows can automate changes to Salesforce records, they don't provide the specialized work-routing semantics required for messaging sessions. Assignment rules similarly aren't designed for conversational Omni-Channel routing.

Therefore, option A correctly implements the inbound routing architecture. The uploaded master bank also identifies A as the keyed response.

Study Guide Reference: Agentforce and AI Innovation → Conversational Marketing Fundamentals for Marketing Cloud Next → Agentforce messaging and channel orchestration.

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