Marketing Cloud Consultant MCE-Con-201 Salesforce Study Notes

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.

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.

Given the Marketing Cloud Connect integration is already in place and the requirement is prompt, near-immediate delivery when a new subscriber signs up on the website (implying the website submission creates or updates a corresponding Salesforce record, since Sales Cloud is the connected CRM), Salesforce Triggered Sends is the correct, native mechanism: configured declaratively against the relevant Salesforce object and field (such as a new Contact/Lead record being created), it fires the welcome email promptly upon that Salesforce-side event, leveraging the existing Connect integration rather than requiring a separate capture mechanism. Batch file drops to SFTP (A) and file imports to data extensions (B) are both inherently scheduled, delayed, batch-oriented processes that cannot deliver the ' promptly ' requirement, since they depend on periodic file processing rather than immediate, event-driven triggering. Smart Capture forms (C) are a native Marketing Cloud web-form capture tool, but the scenario specifically anchors the integration around Sales Cloud via Marketing Cloud Connect, making a Salesforce-side triggered mechanism the more directly applicable and efficient solution that leverages the existing architecture rather than introducing a parallel Marketing Cloud-native capture form. Reference: Salesforce Triggered Sends, Marketing Cloud Connect.

Synchronized Data Extensions are the native, near-real-time integration mechanism for bringing Salesforce objects — including custom fields on the standard Case object, such as the ' Contact Me ' checkbox — directly into Marketing Cloud through Marketing Cloud Connect, and critically, they support applying a filter condition (a Boolean filter on Contact Me equal to true) at setup, so only the relevant closed cases requesting follow-up are synchronized, rather than importing the full case volume and filtering afterward. This gives NTO an efficient, continuously-refreshing, pre-filtered dataset ready to drive the messaging campaign without manual, recurring import work. Option A ' s manual Report-and-Import-Wizard approach is a one-time, manually-triggered batch process lacking the ongoing, automatic refresh that Synchronized Data Extensions provide, making it poorly suited to a recurring campaign need. Option B references ' Salesforce Data Extensions ' paired with Filter Activities as if importing were a separate manual step requiring additional filtering logic downstream, which is less efficient than filtering directly at the sync configuration level. Option D incorrectly attributes data-import functionality to Journey Builder, which consumes already-available data extensions rather than performing the underlying Salesforce data import itself. Reference: Synchronized Data Extensions, Marketing Cloud Connect Filters.