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

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.

Because the incoming file is encrypted, a File Transfer activity must run first to decrypt/decompress it from the Enhanced SFTP location into the Safehouse before it can be processed, which rules out options B and C, which begin directly with an Import activity. The decrypted file is then brought in via a Data Copy or Import File activity into a staging data extension containing the third-party platform ' s identifiers (email addresses, since that ' s what the external unsub file will contain). Because NTO does not use Email Address as Subscriber Key, a Query Activity is required next to join this staged file against existing subscriber records to correctly resolve the corresponding internal Subscriber Key for each matched email address — without this step, the unsubscribe action would have no reliable way to target the correct internal records. A Data Extract Activity then produces a properly formatted unsubscribe file keyed on Subscriber Key, a second File Transfer moves that file to the location the unsubscribe process expects, and a final Data Copy or Import File activity performs the actual unsubscribe action against the All Subscribers List using the correctly resolved Subscriber Key values. Option A skips the essential Query step needed to resolve identity when Subscriber Key differs from Email Address. Reference: File Transfer Activity, Query Activity for Key Resolution, All Subscribers Unsubscribe Import.

The Transactional Messaging API is Salesforce ' s purpose-built, API-driven mechanism for sending exactly this class of message — a one-off, highly time-sensitive, security-relevant notification (new-IP login alert) that must be dispatched with minimal latency directly from an external system ' s real-time event trigger, without waiting on any batch, scheduled, or journey-evaluation cycle. Because the request is initiated synchronously via a direct API call at the exact moment the security event (new IP login) occurs, and the response includes send-status confirmation, it delivers the fastest possible deployment path among the available options while also supporting the dynamic, per-message content (the specific login IP) that needs to be included. Injecting the subscriber into a Journey (A) introduces journey entry-evaluation timing and processing overhead that, while often fast, is not as directly immediate as a synchronous transactional API call purpose-built for exactly this kind of urgent, individual, security-triggered message. ' User Initiated Emails Interaction ' (B) and ' Triggered Emails Interaction ' (D) are not standard, precisely-named Marketing Cloud features matching this real-time, API-driven transactional use case as directly as the Transactional Messaging API. Reference: Transactional Messaging API, Security/Fraud Alert Messaging Patterns.

Journey Builder ' s Salesforce Campaign Member entry source is the native, event-driven mechanism specifically designed to inject a contact into a journey the moment they are added as a Campaign Member to a designated Salesforce Campaign — precisely matching the trigger condition described (Contact added as a Campaign Member to the Loyalty Members ' Campaign) — and the journey ' s Email Activity then sends the welcome message promptly upon that entry event, all natively within the existing Marketing Cloud Connect integration. This is the correct, purpose-built, real-time-triggered pattern for Campaign-Member-driven welcome emails. Option A ' s Content Builder Send Flow is designed for one-time, ad hoc sends directly to a Salesforce Report or Campaign audience as a snapshot at the moment of sending — it is not an ongoing, event-driven trigger that automatically fires a welcome email each time a new member is added over time. Option B ' s scheduled Automation with a Query Activity introduces batch-processing delay and requires manually re-querying for new Campaign Members on each run, lacking the immediate, native entry-event triggering that Journey Builder ' s Campaign entry source provides. Option D, creating an import definition, is unrelated to triggering an outbound email based on Campaign membership changes. Reference: Journey Builder Salesforce Campaign Entry Source.

SSH key-based authentication is the correct, security-conscious solution because it replaces the password-based login entirely with a cryptographic key pair — the external data warehouse system authenticates using its private key rather than a password subject to the 90-day expiration policy, eliminating the recurring maintenance burden of updating the file transfer script every time a password rotates, while actually strengthening security compared to password authentication rather than compromising it. This is precisely why Salesforce documents SSH Key Management as the recommended approach for unattended, script-driven, recurring file transfer integrations that need to avoid password-expiration disruption. Option A, disabling password expiration entirely for FTP users, directly conflicts with the explicit requirement that the customer does ' not want to compromise security ' — permanently exempting an account from password rotation policy is a security downgrade, not a secure workaround. Option B, enabling SAML Single Sign-On, is designed for interactive human user authentication into the Marketing Cloud application interface, not for unattended, script-based SFTP file transfer authentication. Option D is a non-solution — the scenario already specifies an Enhanced FTP account, which uses SFTP protocol; simply restating ' use SFTP ' does not address the underlying password-expiration/automation problem at all. Reference: SSH Key Management, Enhanced FTP Authentication.

Marketing Cloud Connect ' s integration user requires both the API User checkbox enabled — which designates the account as a dedicated, non-interactive system/integration user rather than a standard human login, exempting it from normal password-expiration and login-count restrictions that would otherwise break the integration — and sufficiently elevated role permissions to perform the full range of actions Marketing Cloud Connect needs, which is why Salesforce ' s documented setup specifies both the Administrator and Marketing Cloud Administrator roles be applied to this user. Together, these two settings ensure the integration user can reliably authenticate on an ongoing, unattended basis while having the necessary permissions across both the Marketing Cloud and Salesforce sides of the connection to support synchronization, triggered sends, and Connect app functionality. Option B leaves the user without the roles needed to actually perform Connect ' s required operations, which would cause integration failures. Options C and D both leave the API User checkbox deselected, meaning the account behaves as a standard interactive user subject to expiration and session policies unsuited to an always-on system integration, and option D ' s Marketing Cloud Viewer role is read-only and insufficient for an integration user that must write and synchronize data. Reference: Marketing Cloud Connect API User Setup.

Synchronized Data Extensions, delivered through Marketing Cloud Connect, replicate Salesforce object data into Marketing Cloud on a near-real-time cadence (well within the stated 30-minute tolerance) and scale to millions of records without the manual scheduling overhead of report-based imports. Critically, Synchronized Data Extensions support a filter condition at setup, so the consultant can configure the sync to include only records where the consent checkbox equals true — satisfying the requirement that just the opted-in half of the customer base is brought over, rather than importing everything and filtering downstream. Salesforce Report Import via Automation Studio (A) is a scheduled, batch-oriented process typically running on an hourly-or-longer cadence and does not reliably guarantee a 30-minute SLA at this scale, nor does it filter as cleanly as a native sync filter. Event Data from a Journey Builder Entry Event (B) is designed to trigger journey entry from a Salesforce event (like a Platform Event or Process Builder/Flow action), not to bulk-import and maintain a filtered customer dataset for general use across multiple journeys. ' All Subscribers ' (D) is the legacy subscriber list, not a Salesforce-synchronized, filterable dataset, and the claim that it is synchronized in real time is inaccurate. Reference: Marketing Cloud Connect, Synchronized Data Extensions.

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.

BuildRowSetFromJSON() is the AMPscript function documented by Salesforce specifically for parsing a JSON payload — such as an order-details object from a commerce platform — directly into an AMPscript rowset that can be looped through with RowCount() and Field() to render order line items, quantities, and prices inline in email content. Because AMPscript executes natively at send time within Content Builder emails, this is the correct, in-content mechanism for the scenario described. Option D, the SSJS platform function ParseJSON, is a real Marketing Cloud function, but it operates in server-side JavaScript context (used in Script Activities and CloudPages), not natively inside AMPscript-based email content — it is the wrong layer for formatting JSON directly within an email ' s AMPscript. Option A, ' ParseJSON content block within Content Builder, ' is not a real Content Builder block type; ParseJSON is a function, not a drag-and-drop content block. Option B, TransformJSON(), does not exist as an AMPscript or SSJS function in Marketing Cloud ' s documented function library and should be treated as a fabricated distractor. Consultants should default to BuildRowSetFromJSON() whenever the requirement is parsing and displaying JSON-structured order or product data directly within AMPscript email content. Reference: AMPscript BuildRowSetFromJSON() Function.

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.

Configuring a dedicated sending domain (used for links, tracking, and authentication) separate from the company ' s primary corporate domain is fundamentally a DNS delegation exercise, and the two gating questions a consultant must confirm with IT are precisely about DNS control and organizational policy. First, the IT team must confirm they are able to modify their domain ' s DNS entries at all — without edit access to the authoritative DNS zone, no sending-domain configuration (CNAME records for link/tracking domains, SPF/DKIM entries) can proceed. Second, because a dedicated sending domain is typically implemented as a subdomain (for example, email.company.com) with its DNS delegated or pointed to Marketing Cloud ' s infrastructure, IT must confirm whether company policy permits delegating subdomains to a third-party platform like Salesforce — some organizations restrict this for security or governance reasons. Option C, about creating and posting DNS files when self-hosting, is not a standard Marketing Cloud domain configuration concept — Marketing Cloud does not require the customer to ' host ' DNS files. Option D, giving Marketing Cloud direct access to update DNS records, is not how the process works; the customer ' s own IT team makes the DNS changes based on records Salesforce provides, rather than granting Salesforce direct DNS access. Reference: Sending Domain Configuration, Email Domain Setup.

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.

Journey Builder provides two native building blocks that together satisfy this requirement without any custom development: an Engagement Split evaluates each recipient ' s response — click behavior on a satisfaction survey, for example — to branch negative responses down a distinct journey path, and the native Case Activity (available through Marketing Cloud Connect) can then directly create a new Case record in Service Cloud for that negative-response branch, all within a single orchestrated journey and using entirely out-of-the-box functionality, matching the explicit ' use as much native functionality as possible ' guidance. This is the cleanest, lowest-effort path precisely because both the routing logic and the Salesforce write-back are native journey activities requiring no custom code. Option A ' s AppExchange/custom API integration approach is unnecessarily heavy engineering when native functionality already accomplishes the goal. Option C substitutes a Custom Activity, which by definition requires custom development and external hosting, for the native Case Activity, working against the stated preference for native functionality. Option D proposes handling response capture in Automation Studio, which lacks the native engagement-based branching logic that Journey Builder ' s Engagement Split provides for evaluating individual response sentiment in real time. Reference: Journey Builder Engagement Split, Case Activity (Marketing Cloud Connect).

The requirement explicitly calls for an attribute-to-attribute comparison between the customer number field in the journey ' s entry source data extension and the customer number field in a separate transaction data extension. A Decision Split configured for ' both Contact and Journey Data ' allows the split ' s filter criteria to reference attributes from Attribute Groups configured in Contact Builder (relational, contact-scoped data such as the transaction/redemption DE) alongside the journey ' s own entry-source attributes in a single condition — precisely the cross-DE, field-to-field comparison described. A split using only Journey Data (A) is confined to the fields present in the entry source itself and cannot reach into the separate transactional data extension. A split using only Contact Data (B) can query related, contact-linked data but loses the ability to reference journey-specific attributes in the same condition, which the scenario also implies is needed for the comparison. Einstein Split (C) is a machine-learning-driven random/predictive path allocator, not a rules-based attribute comparison tool, and is unrelated to this use case. Consultants should recognize ' compare a field in the entry source against a field in a related data extension ' as the signature use case for the combined Contact-and-Journey Data Decision Split. Reference: Journey Builder Decision Split, Data Designer Relationships, Attribute Groups.

A newsletter sent to a volatile, frequently-changing data extension is best served by a Scheduled Automation containing a Send Email/Send Activity, because that activity evaluates and sends to whatever population exists in the data extension at the moment the automation runs — additions and removals since the last run are automatically respected without requiring re-entry logic or contact-level state tracking. This is also the fastest delivery mechanism for large batch newsletter sends, since Send Activities in Automation Studio are optimized for bulk, list-based dispatch rather than the per-contact evaluation overhead of Journey Builder. A journey with re-entry allowed (B) introduces unnecessary complexity and processing overhead for a simple recurring batch send, and re-entry rules are designed for repeatable individual customer experiences, not periodic newsletter blasts to a churning list. Single Send Journeys (A) are designed for one-time, ad hoc sends to a static snapshot audience and are not suited to a recurring, periodically-changing send. Triggered Send Emails inside a Scheduled Automation (C) is a mismatched combination — Triggered Sends are typically driven by individual API/Salesforce events, not scheduled batch dispatch to a whole data extension. For recurring, high-volume, list-based newsletters, Scheduled Automation with a Send Activity is the standard, performant pattern. Reference: Automation Studio Send Activity, Journey Builder vs. Automation Studio Use Cases.

Salesforce ' s documented deliverability guidance recommends separating transactional and commercial email traffic onto distinct Sender Authentication Packages (and correspondingly, distinct sending domains/IP reputations where applicable) because the two traffic types have fundamentally different engagement and complaint profiles — transactional messages (password resets, receipts) typically have very high open rates and near-zero complaints, while commercial/marketing messages carry more variable engagement and higher complaint risk. Mixing both traffic types under a single SAP/domain risks commercial-send reputation issues bleeding over and degrading deliverability for critical transactional messages, so maintaining separate SAPs isolates and protects each traffic type ' s sender reputation independently. Option A ' s specific 500,000-message shared-IP threshold is not accurate guidance tied to this scenario ' s core concern. Option C ' s blanket ' one dedicated IP per 100,000 messages ' ratio is an oversimplified and inaccurate rule; dedicated IP warm-up and volume thresholds depend on multiple deliverability factors beyond a fixed per-100,000 ratio. Option D ' s claim that a minimum monthly volume is required ' to maintain sender reputation ' inverts the actual guidance, which is generally about maintaining consistent (not necessarily minimum) sending volume and quality to build and preserve reputation over time. Reference: Sender Authentication Package Best Practices, Transactional vs. Commercial Sending.

The Contact Data View is the authoritative system data view that reflects the full Contact model in Marketing Cloud, including all contacts synchronized from connected Salesforce orgs and those created natively. A scheduled Automation Studio sequence — SQL Query Activity against the Contact Data View, followed by a Data Extract Activity configured to email the resulting file or a notification — satisfies a recurring, hands-off weekly report to the CMO. Option C is close in mechanics but targets the Subscriber Data View, which reflects the legacy All Subscribers list rather than the full Contact model; in a Contact Model-enabled account, this undercounts or misrepresents the true contact base. Option A references a ' Contact Extract Activity, ' which is not a standard Automation Studio activity name — Data Extract Activity is the correct term, and it operates on Data Extensions, not directly on a live count without a preceding query. Option B ' s ' Contacts Counts Standard Report ' is not an out-of-the-box Marketing Cloud report. Consultants should default to querying the correct data view for the object being counted, then automating the export/notification with Automation Studio rather than relying on manufactured report names. Reference: Marketing Cloud Data Views, Automation Studio Query and Extract Activities.

Salesforce Triggered Sends, configured through Marketing Cloud Connect, are declaratively set up on a Salesforce object and field using point-and-click Setup configuration (Triggered Send Definition mapped to a Salesforce workflow or process trigger on field change) — no Apex code is required. When the email address field on the Contact record changes, the configured trigger fires and Marketing Cloud sends the associated triggered email almost immediately, satisfying both the ' immediately after ' and ' without writing an APEX trigger ' constraints simultaneously. Journey Builder and Automation Studio (A) could theoretically be assembled to poll for changes, but that requires either a Salesforce Data Extension sync on a schedule (introducing latency, not immediacy) or a Salesforce Platform Event/Flow-based entry event, which is a heavier build than what ' s needed and isn ' t the direct, native answer to a simple field-change trigger. Salesforce Report Import (C) is a batch, schedule-driven mechanism entirely unsuited to real-time triggering. The Transactional Messaging API (D) is API-driven and requires an external system or Apex/Flow callout to invoke it — it is not itself a native, no-code response to a field change. Salesforce Triggered Send is precisely the declarative, native feature for this use case. Reference: Marketing Cloud Connect, Salesforce Triggered Sends.

A Salesforce Data Entry Source configured against the appointment date field (a date-based/date-triggered entry source) natively evaluates each record ' s scheduled date and injects the patient into the journey exactly one day before the appointment at the specified time, eliminating the need for a separate daily refresh automation. Once in the journey, an Email activity sends the reminder, and an Update Contact/Salesforce Write-Back activity updates the appointment record directly back in the CRM (Sales/Service Cloud) to reflect the reminder was sent — closing the loop where the source of truth actually lives. Option A is close but writes back to ' CRM ' generically through a Data Extension entry source, missing the more precise Salesforce Data Entry Source that natively supports date-based triggering off the CRM record itself. Option B relies on manually engineered AMPscript logic to update a Synchronized Data Extension, which is a read-optimized, one-way sync object not intended for write-back to Salesforce — updates must go through the CRM directly. Option C similarly targets the read-only Synchronized Data Extension for the write-back rather than the actual CRM record. The correct pattern uses Salesforce Data-based entry timing and a genuine CRM write-back activity. Reference: Journey Builder Salesforce Data Entry Source, Update Salesforce Data/Write-Back.

Journey Builder performs best when the heavy lifting of segmentation happens before contacts are evaluated for entry, not inside the journey itself. Performing large-scale segmentation in Automation Studio (B) offloads CPU-intensive filtering to SQL Query Activities, which are optimized for bulk processing across millions of rows, rather than relying on Journey Builder ' s per-contact entry evaluation engine. Creating a prefiltered, dedicated sendable copy of the source data extension for each journey (D) avoids lock contention and re-evaluation overhead that occurs when multiple journeys share a single large entry source, and it ensures each journey only processes the exact population it needs. Option A is a valid best practice for decision-split performance generally, but Attribute Groups govern contact-level data joins for Contact Data-based splits and does not address entry-source scale at 10 million records specifically — it ' s a secondary optimization, not one of the two primary levers for this scenario. Option C describes filtering directly on the entry source Data Extension, which still forces Journey Builder to evaluate the full underlying population against the filter at entry time, rather than pre-segmenting it, and is less efficient than doing that work in Automation Studio beforehand. Reference: Journey Builder Performance Best Practices, Automation Studio Segmentation.

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.

Because NTO is importing an entirely new dataset of customer records from a newly acquired company, and needs an ongoing, automatically-enforced safeguard ensuring that any email address matching a previously recorded opt-out is excluded from commercial sends — not just a one-time manual check — an Auto-suppression list, dynamically populated and refreshed against the known opted-out addresses, is the correct feature: once configured, it automatically applies to future qualifying sends without requiring the marketer to manually re-attach a static list to each individual send, providing durable, ongoing compliance protection as the newly imported and existing populations are merged. A standard Suppression list (C) is a static, manually-attached list that must be explicitly selected on each individual send — it does not automatically and continuously enforce itself across all future sends the way an auto-suppression list does, making it a less robust, more maintenance-dependent safeguard for this ongoing compliance concern. ' Exclusion Script ' (A) and ' Exclusion List ' (B) are not standard, documented Marketing Cloud feature names for this purpose. Reference: Auto-Suppression Lists, Opt-Out Compliance in Data Migrations.

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.

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.