Practice Free MCE-Con-201 Salesforce Certified Marketing Cloud Engagement Consultant Exam Questions Answers With Explanation

Reply Mail Management ' s auto-reply functionality is configured to respond back to the original sender using the same From Address that the original marketing send used — in this case, marketing@email.nto.com — because from the customer ' s perspective, their reply was addressed to that sending domain, and the automatic acknowledgment they receive should logically and consistently come from that same recognizable address rather than an internal, customer-facing forwarding destination. This maintains a coherent sender identity for the customer even though, behind the scenes, RMM is simultaneously forwarding the actual reply content to the internal Customer Service team ' s inbox (customerservice@nto.com) for follow-up. Option D, customerservice@nto.com, is the internal destination the reply content gets forwarded to for the Customer Success team ' s visibility — it is not the address the customer ' s automatic acknowledgment appears to come from. Option A, customer@example.com, is the customer ' s own address and the recipient of the auto-reply, not its sender. Option B, a generic ' reply@marketingcloud.com, ' is not a real, functional Marketing Cloud sending address and does not correspond to how RMM auto-reply From Address configuration actually works. Reference: Reply Mail Management, Auto-Reply Configuration.

The Verification Activity in Automation Studio is specifically designed to evaluate a target data extension against a defined condition — such as a maximum row/record count — before the automation is allowed to proceed to the next step. Configured with a row-count threshold of 2,500, it checks each segmented loyalty data extension prior to the send step and, if the count exceeds that threshold, can halt the automation and optionally notify an administrator, preventing an oversized segment from ever reaching the Send Activity. This is exactly the safeguard the scenario calls for: proactively preventing sends rather than reacting after the fact. A Stop Activity (B) unconditionally halts an automation wherever it is placed — it has no built-in conditional evaluation logic of its own and cannot, by itself, assess whether a count threshold has been exceeded; it would need to be paired with something like a Verification Activity to be meaningful here. A Script Activity (C) could theoretically be custom-coded to check a count, but this introduces unnecessary development overhead when a native, purpose-built activity already exists. A Query Activity (D) segments or transforms data but has no native conditional gating or count-based stop logic. Reference: Automation Studio Verification Activity.

This structure directly maps onto the stated organizational and operational requirements: a parent Business Unit is created purely for governance purposes — NTO holding company staff gain natural account-level, cross-BU visibility into all subscribers and aggregate reporting from that top-level vantage point without ever needing to execute campaigns from it, matching the explicit statement that no marketing is sent on the parent ' s behalf. Each of the three subsidiaries — Universal Containers, Ursa Major Solar, and Cloud Kicks — receives its own dedicated child Business Unit, which provides full content, branding, and subscriber isolation between the three regularly-campaigning brands, exactly as required. Assigning each child BU its own Sender Authentication Package ensures each subsidiary ' s sending domain, IP reputation, and deliverability posture remain fully independent, appropriate given each brand runs meaningfully distinct campaign volumes and identities. Option A provides only one child BU, insufficient for three distinct subsidiaries. Option C under-provisions with only two child BUs for three subsidiaries. Option D substitutes private domains for actual Business Unit separation, which would not achieve the content, subscriber, and branding isolation between the three subsidiaries that dedicated child BUs provide. Reference: Business Unit Hierarchy Design, Sender Authentication Packages.

Reply Mail Management (RMM) processes inbound email replies against configured keyword lists to automatically detect and action unsubscribe intent, complaint language, and other reply categories; when a customer ' s specific free-text phrasing — such as ' take me off your list ' or ' opt out ' — is not already present among the recognized unsubscribe keywords, RMM will fail to classify that reply as an unsubscribe request and the subscriber remains on the active send list, exactly matching the complaint described. The correct fix is to explicitly add these specific phrases to RMM ' s filtered keyword list configuration, so future replies containing that exact language are correctly recognized and automatically actioned as unsubscribes. Option A, the ' Common Misspellings ' reply filter, addresses typo variants of already-recognized keywords, not entirely new phrases that were never configured in the first place. Option B, DNS Record Redirect configuration, governs how inbound replies are routed to Marketing Cloud ' s RMM processing infrastructure at the mail-server level — it is a plumbing/delivery concern, not a content-classification issue, and would not explain why recognized-but-unlisted phrases go unactioned. Option C references a ' Filtered Keywords data extension, ' which is not the correct configuration surface; RMM keyword configuration is managed through its dedicated filtered keyword list interface, not a generic data extension. Reference: Reply Mail Management, Filtered Keyword Lists.

Because the campaign relies on a pre-built MobileConnect Filtered List (rather than a fresh import each cycle), the correct weekly automation sequence begins with a Refresh Mobile Filtered List activity, which re-evaluates the filter criteria (birthdays falling within the current week) against the existing contact population and updates the list ' s membership accordingly for that week ' s run. Once refreshed, the Outbound Send activity is the correct Automation Studio activity to dispatch the pre-configured Outbound Message created in MobileConnect to the newly refreshed filtered list — ' Outbound Send ' being the specific, documented activity name used to trigger a MobileConnect Outbound Message, as distinct from a generic ' Send SMS ' activity name. Options C and D both reference a ' Send SMS ' activity, which is not the precise, correct Automation Studio activity name for dispatching a MobileConnect Outbound Message — this naming distinction matters for exam accuracy. Options B and D both propose ' Import Mobile Contacts, ' which is unnecessary and incorrect here, since the scenario explicitly states a Filtered List already exists and simply needs to be refreshed on each cycle, not re-imported from scratch. Reference: MobileConnect Filtered Lists, Automation Studio Outbound Send Activity.

Because the customer already possesses a fixed, curated list of known competitor email addresses — a static, externally-sourced list rather than a set dynamically derived from an internal query against existing behavioral or attribute data — the correct approach is to load these known addresses directly into an auto-suppression list, which then automatically applies to all qualifying future sends and prevents any of the listed addresses from receiving marketing communications going forward without requiring the list to be manually re-attached to each individual send. Populating it directly with the known email addresses (rather than subscriber keys, as in option B) is appropriate here specifically because the source data the customer has in hand is a list of raw email addresses, not internal subscriber key values, and the suppression mechanism can match directly against the email address field. Option A describes building a list via query to ' exclude the subscriber key, ' which misapplies a query-based approach to what is fundamentally a static, externally-provided list rather than data that needs to be dynamically derived through SQL logic. Option D ' s ' exclusion list ' is not the correct, standard Marketing Cloud terminology or mechanism for this scenario — auto-suppression list is the actual, documented feature that automatically applies across future sends. Reference: Auto-Suppression Lists.

Marketing Cloud ' s Content Permissions and Restrictions by Role framework, configured through Setup and Role permissioning, is the native, platform-enforced mechanism that governs precisely which users and business units can view, access, or edit specific content folders and assets, and which content requires review before changes take effect. Because permissions are tied to defined roles rather than ad hoc individual grants, this creates consistent, auditable control over both content visibility (who can see what) and content editability (who can change what and under what review conditions), directly answering both parts of the stated requirement using tools already built into the platform. Option A, Approval Workflow and Share settings, addresses collaboration and folder-sharing scope but is not the comprehensive, role-based permission structure needed to fully control both access and edit/review rights across users and business units. Option B, integrating an external CMS, introduces unnecessary architectural complexity and cost when native Marketing Cloud role permissions already solve the stated need without external systems. Option D, relying purely on internal process without platform-enforced controls, leaves the requirement unenforced technically — process alone does not prevent unauthorized access or edits the way role-based permissioning does. Reference: Content Permissions and Restrictions by Role, Marketing Cloud Roles.

Identifying subscribers who did not receive their intended email over a rolling 24-hour window requires filtering logic against send-outcome data (such as the Sent, Bounce, or related data views) based on a specific date range and a negative-outcome condition — precisely the kind of conditional, criteria-based filtering that a SQL Query Activity is built to perform. This activity is the essential step that actually identifies and isolates the correct population of non-received subscribers before anything can be exported; without it, there is no mechanism within the automation to determine which specific subscribers meet the ' did not receive ' criteria. While a Data Extract Activity (C) would ultimately be needed to produce the exportable file and place it on the SFTP, the scenario is asking specifically which activity is required to correctly identify the target population in the first place — and that identification step is the SQL Query Activity, making it the most essential, non-optional component of this automation given the filtering complexity described. A Report Definition Activity (A) is not the standard mechanism for this kind of granular, criteria-based subscriber-level filtering. A ' SendLog Extract ' (B) is not a distinctly named standard Automation Studio activity separate from the general Data Extract Activity. Reference: Automation Studio SQL Query Activity, Data-Driven Segmentation for Exports.

Data Filters in Contact Builder provide a point-and-click, drag-and-drop interface for building segmentation logic against attribute groups without writing SQL, which is exactly the on-ramp a non-technical team coming from manual Excel/VLOOKUP segmentation needs for sustainable self-sufficiency. Marketers can visually construct AND/OR filter logic against contact and related data, save the resulting filtered segment, and reuse or export it — replicating what they were doing manually in spreadsheets, but natively within the platform and without ongoing developer or consultant involvement. Query Activities (A), while powerful, require hand-written SQL syntax, which directly conflicts with the stated ' very little coding experience ' constraint and would create an ongoing dependency on technical resources rather than long-term self-sufficiency. Publication Lists (B) are a list-management construct for organizing subscribers by communication type/preference, not a segmentation-logic tool for building audiences from arbitrary attribute conditions. Attribute Groups (D) are the underlying Contact Builder configuration that defines which data extensions and relationships are available for segmentation — they are a prerequisite setup layer, not the marketer-facing segmentation tool itself; Data Filters are what marketers actually interact with to build audiences from those groups. Reference: Contact Builder Data Filters, Data Designer.

Automation Studio ' s Random Split Activity is purpose-built for exactly this use case: it takes a source data extension and divides its population into a specified number of evenly-sized, randomly-allocated output data extensions — up to 15 target groups in a single configuration — making it the direct, native tool for splitting 880,000 subscribers into 11 test cells for a messaging strategy experiment. This runs as a discrete, batch-oriented step well suited to a one-time or periodic large-scale segmentation exercise ahead of a send. While Journey Builder (B) does offer a Random Split/Engagement Split concept for path allocation within a running journey, it operates at the individual-contact, in-journey routing level rather than as a bulk pre-send data-partitioning tool for building separate testable data extensions, making it a mismatched tool for this specific batch-preparation requirement. Contact Builder (C) is the data modeling and relationship configuration workspace — it does not contain data-splitting or randomization functionality. Email Studio (D) is the content and list-management workspace for building and sending emails; it likewise has no native random data-extension splitting capability. For any ' divide a data extension into N random groups ' requirement, Automation Studio ' s Random Split Activity is the standard answer. Reference: Automation Studio Random Split Activity.

Because the file arrives intermittently rather than on a predictable cadence, a File Drop Automation (C) is the correct trigger mechanism — it kicks off the automation the moment the file lands on the Enhanced SFTP location, satisfying the ' immediately imported ' requirement, in contrast to a Scheduled Automation (A), which only runs at fixed, predetermined intervals and would introduce unnecessary delay between file arrival and processing. Once imported, the requirement that contacts be ' segmented to enter a specific journey depending on the data inside the file ' describes routing different subsets of the imported data toward different journey entry sources, which is precisely what a SQL Query Activity (D) accomplishes: it evaluates the imported data ' s field values and writes matching subsets into the appropriate, journey-specific data extensions that then serve as entry sources for the correct journeys. Decision Split (B) is a Journey Builder activity that routes contacts already inside a single journey down different internal paths based on criteria — it does not determine which of several distinct journeys a contact should enter in the first place, which is the segmentation task described here; that pre-entry routing decision belongs to a Query Activity performed in Automation Studio before journey injection. Reference: File Drop Automations, Automation Studio Query Activity, Journey Entry Source Segmentation.

When Email Address is used as the Subscriber Key, unsubscribe status is tied to that specific address value rather than to a stable, unique identifier. If the automation-driven, file-based send last week processed the unsubscribe against a subscriber record keyed by email address, but MCC ' s own record-matching and opt-out logic resolves identity differently (for example, against ContactID or a separate Subscriber Key structure), a mismatch between how the two send pathways identify ' the same person ' can result in the unsubscribe not being recognized when Marketing Cloud Connect later sends to that same individual — effectively creating two disconnected identity records for opt-out purposes. This is a classic, documented pitfall of using Email Address as Subscriber Key in environments where both native Marketing Cloud sends and Marketing Cloud Connect sends coexist. Option B is inaccurate — Email Opt Out status is not gated by whether a send ' originates in Salesforce ' ; it is a subscriber/contact-level status. Option C, adding a field to a page layout, is a UI-visibility concern with no bearing on whether opt-out logic is honored at send time. Option D, edit permissions, would affect the user ' s ability to configure the send, not whether unsubscribe status is respected. Reference: Subscriber Key Best Practices, Marketing Cloud Connect Opt-Out Handling.

A Salesforce Report is the correct recommendation because it is the tool Sales Cloud users themselves can build and manage manually, directly within their familiar Salesforce interface, without needing any Marketing Cloud access or technical skill — critically, Salesforce Reports natively support combining both Lead and Contact records (through report types built for that combination), and once built, such a report can be directly selected as the target audience within Email Studio ' s Send Flow via Marketing Cloud Connect, which specifically supports sending to Salesforce Reports as an audience source. This directly satisfies the requirement that Sales Cloud users — not Marketing Cloud specialists — are the ones manually creating the segment. Automation Studio (A) and Salesforce Data Extensions or Synchronized Data Extensions (D, B) all require Marketing Cloud-side configuration, SQL knowledge, or Contact Builder access to build and maintain — none of which are accessible or manageable directly by Sales Cloud users working purely within their own CRM interface, working against the explicit ' Sales Cloud users to manually create ' requirement. The Salesforce Report send-flow integration is specifically designed for exactly this kind of CRM-user-driven, cross-object (Lead and Contact) audience creation. Reference: Marketing Cloud Connect Send Flow, Salesforce Report Audiences.

Because the Marketing Cloud Connect app-level connection itself reports as successful, but Sales Cloud objects still fail to appear or synchronize within Contact Builder, the most direct and efficient troubleshooting step is to verify that the specific users involved in the integration — both on the Marketing Cloud side (the integration/API user) and the Sales Cloud side — hold the correct permission sets and role-based access required to expose and synchronize Salesforce objects into Contact Builder, since a successful app connection does not automatically guarantee sufficient object-level and field-level permissions for synchronization to function. This is a targeted, low-effort first diagnostic step consistent with standard troubleshooting methodology: verify permissions before escalating to more invasive fixes. Option A, sending a test email to validate tracking, addresses a different layer of the integration (send-tracking sync) rather than the object-visibility issue described in Contact Builder specifically. Option B, creating new users and reinstalling entirely, is a drastic, high-effort action that should only be considered after simpler causes like permissions have been ruled out. Option C, validating Sales Cloud users have BU access, is narrower and less complete than validating permissions across both platforms, which is the more thorough and correct first diagnostic. Reference: Marketing Cloud Connect Troubleshooting, Contact Builder Salesforce Data.

This scenario again splits cleanly into two distinct requirements best handled by two complementary tools working together. Automation Studio is the correct tool for building the complex, multi-data-extension segmentation logic needed to assemble the 200,000-subscriber weekly coupon audience, since SQL Query Activities can efficiently join and filter across several data extensions at that scale. Once that audience is prepared, Journey Builder is required for the sequencing and timing behavior described — waiting three days before sending a reminder, and critically, delivering that reminder at each subscriber ' s individually optimized send time, a feature (Send Time Optimization) that is native to Journey Builder ' s message activities and is not available within Automation Studio ' s Send Activity. Option B, Automation Studio alone, could technically schedule a delayed second send, but cannot natively deliver per-subscriber optimized send-time personalization the way Journey Builder does. Option D, Journey Builder alone, is less efficient for the complex initial multi-data-extension segmentation task, which is better suited to Automation Studio ' s query capabilities before contacts ever enter a journey. Option C references ' Interaction Builder, ' which is not a real Salesforce Marketing Cloud product name. Reference: Journey Builder Send Time Optimization, Automation Studio Segmentation.

The Verification Activity is precisely designed for this two-part requirement: it evaluates the staging data extension against a defined row-count threshold (over 1,000 records) immediately after the Import activity runs, and if that threshold is breached, it can simultaneously send an email notification to the marketing manager and halt the automation before it proceeds to the subsequent SQL Query step. Placing it directly between the Import and SQL Query activities ensures that if the staging data is over-imported, the automation stops right there — preventing the downstream SQL Query from ever populating the sendable data extension that day, satisfying both stated requirements (notification and prevention of the sendable DE update) with a single, native activity requiring no custom development. Option C proposes writing a custom SSJS script to replicate this exact functionality manually, which is unnecessary and less maintainable than using the native, purpose-built Verification Activity that already provides both the conditional check and notification capability out of the box. Option B, splitting into two automations, does not itself provide the conditional row-count evaluation and stop logic — it ' s a structural change that doesn ' t solve the underlying validation requirement. Option D ' s Wait Activity pauses for time-based delay, not conditional record-count validation, and does not address the requirement at all. Reference: Automation Studio Verification Activity.

Tracking Extract, run as an Automation Studio Data Extract Activity, is the documented mechanism for pulling detailed, per-send delivery status data — including records marked as Not Sent — for journey-driven email sends. Unlike the standard Sent Data View, which primarily reflects records that were successfully processed for sending, Tracking Extract exposes the fuller set of delivery outcome codes, including exclusions and failures, giving the granularity needed to specifically isolate and report on the ' Not Sent ' population from journey emails. Option A, querying the Sent Data View, is not reliable for this purpose because that view is generally populated with records that were successfully sent, not the ones that were excluded or failed to send — it is the wrong data source for isolating non-sends. Option B references a ' Subscribers Not Sent to ' standard report, which is not a real, out-of-the-box Marketing Cloud report name. Option D, Analytics Builder Intelligence Reports, refers to a different reporting layer focused on broader engagement and journey performance visualizations rather than granular per-record delivery-status extraction, and is not the documented tool for this specific ' Not Sent ' reporting need. Reference: Tracking Extract, Automation Studio Data Extract Activity.

The Lookup() function ' s fourth parameter must be the value to match against the lookup column — here, SubscriberKey in the Fav_Animals data extension — and that value must be sourced from the current recipient ' s own SubscriberKey at send time. In this scenario, because the audience is being pulled from a Salesforce Report rather than a native Marketing Cloud list, the relevant personalization string that resolves correctly is the plain, unscored SubscriberKey personalization string (matching the field/column naming used generally in Report-based and Salesforce Data Extension sends), which is what option C supplies as the literal fourth argument. Option A ' s ContactID is a Salesforce record identifier, not the Marketing Cloud Subscriber Key value the Fav_Animals data extension is keyed on, so it would fail to match. Option B ' s _emailaddr personalization string returns the recipient ' s email address, an entirely different value than SubscriberKey, and would not correctly match the lookup column. Option D ' s underscore-prefixed _subscriberkey is the legacy/system personalization string typically associated with native list-based sends rather than Salesforce Report-audience sends, making the unscored SubscriberKey reference the more contextually correct choice for this Report-driven scenario. Reference: AMPscript Lookup() Function, Personalization Strings for Salesforce Report Audiences.

The most reliable, documented pattern for cross-journey handoff based on engagement is to capture the engagement outcome as a persisted, queryable data point rather than attempting to read it indirectly from system-level journey data views, which do not reliably expose per-contact Engagement Split path results in a directly queryable format. In this pattern, Journey A includes an Engagement Split after the email send, and the branch a contact falls into (engaged vs. not) is written out via an Update Contact Activity into a Boolean field on a dedicated Engagement data extension — creating a durable, explicit record of that contact ' s engagement outcome. A separate Automation Studio process then queries this Engagement data extension directly to build the entry-source population for journey B, giving a clean, reliable, and fully controllable handoff mechanism between the two journeys. Options A, B, and D all attempt to derive the engagement outcome by querying system Journey/Journey Activity data views for Engagement Split results, which is not a standard, reliably queryable data structure for this purpose — Engagement Split path outcomes are not natively exposed as a clean Boolean field in those system data views the way this scenario ' s options imply. Reference: Journey Builder Engagement Split, Update Contact Activity, Cross-Journey Data Handoff Patterns.

Shared Data Extensions, created at the parent/top-level Business Unit and configured to be visible to child Business Units, are the platform ' s native mechanism for maintaining a single, centrally-managed copy of data — such as product catalogs and support information — that is genuinely identical and consistent across every regional BU, eliminating the redundancy and synchronization risk of maintaining separate regional copies. Because the data is shared by reference from a single source rather than duplicated, any update to product or support information only needs to be made once at the parent level to be immediately reflected everywhere it ' s used, which is both the most efficient and most maintainable configuration for consistent, non-region-specific reference data. Option B, maintaining regional-specific duplicate copies, directly contradicts the requirement that the data ' is consistent across all regions ' and introduces ongoing synchronization overhead and risk of the copies drifting out of alignment over time. Option C, provisioning broad Data Manager Roles for cross-BU visibility, addresses user permissions and access rather than the actual data architecture and storage efficiency question being asked. Option D references a nonstandard, fabricated ' CustomObjectData API ' mechanism that is not a documented Marketing Cloud feature for this purpose. Reference: Shared Data Extensions, Business Unit Data Architecture.

Multi-Org support in Marketing Cloud Connect allows a single Marketing Cloud account (with its multiple Business Units) to connect to more than one Salesforce org — precisely the acquisition scenario described, where each acquired company retains its own Sales Cloud instance. The critical, documented consideration a consultant must flag before recommending this upgrade is that it is a one-way, irreversible architectural change: once an account is upgraded to support Multi-Org connections, it cannot be reverted back to a single-org configuration. This is a significant governance decision that warrants careful upfront planning around Business Unit-to-org mapping, since undoing it later is not possible. Option A is factually incorrect — existing single-org accounts can be upgraded to Multi-Org; that is the entire point of the upgrade path. Option B is also inaccurate; Multi-Org actually partitions Synchronized/Salesforce Data Extensions per connected org and Business Unit rather than sharing them freely across the whole account. Option D is unrelated and untrue — subscription centers and profile configuration still need to be built out per Business Unit regardless of Multi-Org status. The irreversibility in option C is the single most important decision-point consultants must surface. Reference: Marketing Cloud Connect Multi-Org.

The _Click system data view holds granular, per-event click-tracking records across all sends, and a SQL Query Activity is the correct tool to filter this data view against a six-month date range condition to identify the specific set of subscribers who clicked on any link during that window — this is exactly the kind of precise, criteria-based, date-bounded filtering that a SQL Query is built to perform, and the result can be written to a new data extension to seed the loyalty program population. Option B, a ' Data Filter ' applied directly to a system data view, is not the correct mechanism — Data Filters in Contact Builder are built against Attribute Groups modeled from data extensions the consultant configures, not directly against raw system data views like _Click; querying via SQL is the standard, documented approach for working with data views. Option A, Tracking Extract, is designed to export tracking data to a file for external analysis or archival, rather than to directly filter and produce an actionable, in-platform data extension of qualifying subscribers for immediate program enrollment. Option C, a ' Subscriber Engagement report, ' is not a standard, precisely-named Marketing Cloud feature capable of the specific six-month, click-based filtering and segment-creation task described. Reference: Marketing Cloud Data Views — _Click, SQL Query Activity.

Data Designer is the dedicated Contact Builder workspace where relational connections between data extensions are modeled and configured — establishing one-to-one or one-to-many relationships on a common key between the journey ' s entry source data extension and additional, related data extensions holding supplementary attributes. Once these relationships are defined in Data Designer, that related data becomes available for use in Decision Splits, personalization, and other journey logic without needing to physically merge every related field directly into the entry source itself, which is precisely the ' without overloading the entry data ' requirement: the entry source stays lean and purpose-built for triggering journey entry, while richer related data remains accessible on demand through the modeled relationships rather than being duplicated into a bloated single table. ' Data Relationships ' (A) is a plausible-sounding but not the precisely correct, named Contact Builder feature — Data Designer is the actual product name for this configuration workspace. ' Entry Source Data Extension ' (C) describes the object being connected to, not the tool used to establish the connection. ' Contact Configuration ' (D) is not a recognized, standard Marketing Cloud feature name for this purpose. Reference: Data Designer, Contact Builder Relationships.

Because the same Contact/Subscriber record is being reused with a changing Email Address value at send time, standard data views and reports that key off the current subscriber record will not preserve the specific address that was actually used for a given historical send — they reflect present-state data, not point-in-time send detail. Send Logging is the feature purpose-built for this exact requirement: when enabled, it captures a persistent, granular record for every individual send, storing the exact email address (and other attributes) as they existed at the moment of send, independent of any later changes to the subscriber record. That data lands in a queryable Send Log Data Extension the consultant can report from. Data Views (A) reflect current, not historical, attribute values and would show whichever email address is on the record now, not what was used per send. Recent Email Send Report (C) is a high-level send-count summary, not per-subscriber address-level detail. Tracking Extract (D) captures engagement events (opens, clicks) rather than the address used at send time and is not designed to solve the ' which address received which specific send ' problem. Reference: Send Logging, Marketing Cloud Reporting.