MCE-Con-201 Questions and Answers

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.

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.

This is a direct restatement of Q16 ' s underlying mechanism: the Event Notification Service is Marketing Cloud ' s real-time, webhook-based method for pushing granular send-status events — including Sent and NotSent outcomes — to an external, subscribed endpoint as they occur, rather than requiring the analytics team to poll or wait for a batch process. Given the explicit legal-obligation framing, where the team needs assured, immediate visibility into whether a transactional message actually reached the recipient, a push-based, real-time notification mechanism is the only option among those listed that genuinely delivers status ' in real time ' rather than on a delay. Platform Events API (A) is a Salesforce Sales/Service Cloud pub/sub messaging framework for custom Salesforce-side event architectures — it is not the native Marketing Cloud mechanism for transactional send-status notifications. ' Data Retrieves on the Send Object ' (B) is not a defined, real, real-time Marketing Cloud feature or standard terminology. Data View Export ' with every send ' (D) describes a batch or scheduled extraction pattern that, even if run frequently, introduces polling latency and operational overhead incompatible with genuine real-time delivery, unlike a push-based webhook subscription. Reference: Event Notification Service, Transactional Messaging.

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.

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 SMS/MMS Activity within Journey Builder includes a native, dedicated Blockout Window configuration in its Delivery Options, allowing the consultant to define a specific time range (here, 1 a.m. to 6 a.m.) during which the activity will not deploy a message even if a subscriber otherwise qualifies to receive it during that window — this is a documented, purpose-built feature designed for exactly the scenario described, avoiding messages landing during undesirable overnight hours. When a send is scheduled to fall within the configured blockout window, Journey Builder simply skips that send for the affected subscriber rather than delaying or queuing it, cleanly meeting the customer ' s stated preference. Options A and B, both proposing scheduled batch processes to build a suppression list around midnight, are unnecessarily complex, indirect workarounds for a requirement the platform already solves natively and more precisely within the SMS activity ' s own configuration — they also introduce timing gaps and added maintenance overhead. Option D, using a Journey Goal to exit subscribers, addresses journey completion/exit logic generally and is not designed to selectively block a single activity ' s send during specific hours while otherwise allowing the journey to continue. Reference: SMS/MMS Activity Blockout Window.

MobileConnect Demographics is the data structure specifically associated with SMS/MMS subscriber records in Mobile Studio, holding attribute fields (such as first name, custom demographic values, and other subscriber-specific data points) that can be directly referenced via personalization strings within SMS message content, making it the correct, native data source for personalizing text messages sent through MobileConnect. This keeps SMS personalization scoped to the same channel-specific data structure that governs SMS subscriber records generally, ensuring the fields referenced in message content are actually populated and available for that channel ' s sends. ' Data relationships in Email Studio ' (B) pertains to email-content personalization patterns and email-specific data modeling, not to the MobileConnect subscriber data structure that governs SMS content rendering. GroupConnect (C) is Marketing Cloud ' s product for group and social messaging apps (such as LINE or WeChat integrations), a distinct channel from standard SMS/MMS and not the data source for MobileConnect personalization specifically. MobilePush (D) is the channel and data structure for app push notifications, a separate messaging channel from SMS, with its own distinct subscriber/device data model rather than being the source for SMS personalization. Reference: MobileConnect Demographics, SMS Personalization.

Given the explicit statement that immediate ingestion is not required — the data only needs to be available in time for a daily scheduled send — and that submissions arrive at an extremely high frequency (thousands per minute), a daily bulk export from the external system to SFTP, followed by a scheduled Automation Studio import, is by far the most efficient and appropriately-scaled architecture: it avoids the overhead, cost, and API rate-limit risk of processing potentially hundreds of thousands of individual real-time API calls per day when a single, efficient nightly batch transfer accomplishes the same business outcome with far less operational complexity and infrastructure load. Option B, pushing each individual record via a real-time API call on every form submit, is a significant over-engineering of the requirement given real-time delivery was explicitly stated as unnecessary, and would introduce meaningful API volume and rate-limiting concerns at the stated submission frequency. Option C, recreating the external form natively inside Marketing Cloud, is an unnecessary architectural change that abandons existing, presumably functional external infrastructure without clear justification. Option D misapplies a Journey Data Source, which is designed for individual, real-time journey-entry-triggering events, not for bulk batch contact acquisition feeding a scheduled send. Reference: Automation Studio Batch Import, SFTP-Based Data Ingestion.

When a journey spans multiple channels — email, SMS, and push — the Contact Key must serve as a single, stable, channel-agnostic identifier tying together all of a person ' s separate channel-specific addresses (email address, mobile number, device/app identifier), because none of those individual channel addresses is guaranteed to be unique, permanent, or even present for every contact at all times. A generated, non-changing identifier such as a GUID is the documented Salesforce best practice for Contact Key precisely because it remains constant even if a subscriber ' s email address, phone number, or device changes over time, ensuring the same underlying individual is consistently recognized and correctly tracked across all channels throughout the onboarding journey without risk of fragmenting into multiple disconnected records. Using Email Address as Contact Key (B) or a phone number field (C) ties the core identifier to a single, mutable channel value that may not exist for every contact (a contact may lack a phone number, breaking SMS-based identification) and can change over time, causing tracking and deduplication problems in exactly the kind of multi-channel journey described. A shared field like Physical Address (D) is neither guaranteed unique per individual nor a standard identifier practice. Reference: Contact Key Best Practices, Multi-Channel Journeys.

Because the data extension is continually appended to via API over time — rather than being a static, one-time-loaded population — the journey ' s Contact Evaluation setting must be configured to ' Evaluate new records only, ' which ensures Journey Builder only evaluates and processes rows that are newly added to the data extension since the last evaluation cycle, correctly picking up each day ' s newly-added payment-reminder subscribers without repeatedly re-processing or re-sending to records that were already added and evaluated on prior days. Setting this to ' Evaluate all records ' (option C) would cause the journey to re-evaluate the entire historical dataset on every cycle, risking duplicate sends to subscribers who were already processed and potentially already received their reminder, which directly undermines correct, one-time-per-cycle processing of a continually-growing data extension. Journey Settings around ' re-entry ' (option D) govern whether the same contact can enter the journey again after completing or exiting a previous run — a related but distinct concern from which specific rows in a growing data extension get evaluated in the first place. Option B ' s ' Use email attribute from Contacts ' setting concerns how the recipient ' s email address is resolved, not which records are evaluated for entry. Reference: Journey Builder Contact Evaluation Settings, Data Extension Entry Sources.

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.

Salesforce Triggered Sends built on a custom object require two specific technical prerequisites beyond the standard point-and-click Triggered Send Definition setup. First, because custom objects are not natively wired into Marketing Cloud Connect ' s out-of-the-box trigger framework the way standard objects like Opportunity or Case are, an Apex Trigger must be created on the custom object to invoke the Marketing Cloud Connect API and initiate the triggered send when a record is created or updated — this is a documented implementation requirement for custom-object triggered sends. Second, the custom object must contain a Lookup field to Lead or Contact, since the Triggered Send needs a resolvable path to a recipient ' s email address; without a direct Lookup relationship, Marketing Cloud Connect cannot determine who the message should go to. A generic hierarchical relationship ' from Contact to Shipment ' (A) is vague and doesn ' t specify the required Lookup field type needed for send resolution. Placement on the Account Related List (C) is a UI/page-layout consideration with no bearing on whether the trigger mechanism or recipient resolution functions correctly. Reference: Marketing Cloud Connect Triggered Sends on Custom Objects.

The Transactional Messaging API is the correct recommendation because it uniquely satisfies both explicit requirements simultaneously: the message is dispatched as fast as possible through a direct, synchronous API call initiated the moment the password-reset request occurs on the web server, and critically, the API call itself returns a real-time send-status response back to the calling web server, satisfying the requirement that ' their web server should receive a notification when the email is sent ' — a synchronous confirmation mechanism that a standard Triggered Send Definition (C) does not provide in the same direct, immediate way, since Triggered Sends fire based on a configured trigger without returning an inline API response to the calling system. A Multi-Step journey with an API Event entry source (B) introduces journey-evaluation timing overhead and, like Triggered Send Definitions, does not natively provide the synchronous, per-call send-status confirmation back to the web server that the Transactional Messaging API ' s request/response model delivers. An Email Send Activity (D) in Automation Studio is a batch, scheduled mechanism entirely unsuited to the fast, individual, event-driven, confirmation-requiring nature of this password-reset use case. Reference: Transactional Messaging API.

When roughly half of a large contact base will qualify for journey entry, pre-segmenting the population in Automation Studio via a SQL Query Activity — and landing the result in a dedicated, purpose-built Data Extension used as the entry source — is the performance-conscious, best-practice approach. This offloads the filtering computation to SQL processing rather than making Journey Builder ' s entry-evaluation engine repeatedly scan and filter a large, unfiltered source at entry time, which becomes a meaningful bottleneck as volume grows. Option A, applying a filter directly on the Data Extension Entry Source inside Journey Builder, still forces the journey engine to evaluate the filter against the full underlying population on each entry-evaluation cycle rather than working from an already-narrowed set, making it less efficient at scale. Option B ' s Contact Data Entry Source is suited to smaller, attribute-driven contact segments and doesn ' t scale as predictably for large filtered cohorts as a pre-built query result. Option C ' s Import Activity is meant for ingesting external files, not for filtering existing internal data — a Query Activity is the correct tool for that. The ' query first, then feed a clean Data Extension into the journey ' pattern is the standard exam answer for filtering at meaningful scale. Reference: Journey Builder Entry Source Best Practices, Automation Studio Query Activity.

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.

Send Logs, once enabled through Send Logging, provide a unified, cross-channel record of send activity that spans email, SMS, and push notifications, giving the consultant a single, queryable structure to build reporting that covers all three channels together rather than needing to separately reconcile disparate channel-specific data sources. This cross-channel breadth is precisely what the requirement calls for, since the scenario explicitly asks about send data spanning SMS, Push, and email together, not just one channel in isolation. The Sent Data View (B) is scoped specifically to email send activity and does not natively capture SMS or Push send events in the same structure, making it insufficient on its own for a unified, cross-channel query. Tracking Extracts (C) similarly focus primarily on email delivery and engagement tracking data and are not the standard mechanism for consolidated multi-channel (SMS/Push/email) send reporting. Contact History (D) is not a defined, standard Marketing Cloud reporting object for this purpose in this context. When a scenario explicitly spans multiple messaging channels and asks for a single queryable send-data source, Send Logs is the correct, unifying answer among the choices presented. Reference: Send Logging, Cross-Channel Reporting.

The Business Unit-level Email setting ' Subscribers will be unsubscribed from this business unit only ' is the direct, native, low-effort configuration that satisfies this exact requirement: it scopes an unsubscribe action taken within the children ' s fashion business unit to that business unit alone, leaving the subscriber ' s opt-in status intact across all other business units, including the parent Enterprise business unit — with no custom development, attribute engineering, or filter-building required, which aligns with the customer ' s minimal technical resources. This is a single checkbox-level setting change, making it by far the lowest-effort, most maintainable solution among the options. ' Use separate Subscription Center for this business unit ' (A) affects which subscription-preference page a subscriber sees when managing their preferences, not whether an unsubscribe event is scoped to one business unit versus propagating account-wide — it solves a different problem. Option B describes manually engineering a custom filter against the All Subscribers list to track unsubscribes, and option D proposes custom attribute-based tracking — both are unnecessarily complex, developer-dependent workarounds for a requirement natively solved by a single setting. Reference: Business Unit Email Settings, Unsubscribe Scope Configuration.

Because newly registered users have no pre-existing Salesforce Contact record and their device is explicitly stated to remain unassociated with a proper ContactKey for up to 24 hours after registration, MobilePush will, during that unassociated window, necessarily create a new, temporary contact record in Marketing Cloud to track that device ' s push registration and interactions — since the platform requires some contact-level record to associate a registered device with, even before the eventual Salesforce ContactKey linkage completes. This means the consultant must flag that newly registered users will generate additional (initially unmatched) Contact records in Marketing Cloud during that gap period, a consideration with implications for contact-count licensing, deduplication planning, and eventual merge/reconciliation logic once the 24-hour Salesforce association process completes. Existing users who log in with credentials already tied to a Salesforce record (option D) are immediately and correctly matched to their existing ContactKey upon login, so they do not generate additional contacts. Option B ' s ' 48 hours ' figure does not match the 24-hour window explicitly stated in the scenario. Option C incorrectly generalizes the issue to all mobile app users, when it specifically and only affects newly registered users during the unassociated window, not those logging in with pre-existing credentials. Reference: MobilePush ContactKey Association, Mobile App Registration Flows.

Because the new dataset is refreshed independently, on its own separate feed cadence, from the main contact data, it should live in its own dedicated data extension rather than being merged directly into the core contact record. In Data Designer, this new data extension is then linked (related) to the existing contact-based data extensions through a defined relationship on a common key, allowing the data to be joined for segmentation, personalization, and decision-split logic while preserving each source ' s independent update lifecycle. This relational approach is precisely what Data Designer is built for — modeling one-to-one or one-to-many relationships between separately-maintained data extensions without collapsing them into a single monolithic table. Option A ' s ' new population ' terminology does not correspond to a real Data Designer configuration concept — Data Designer works in terms of related data extensions, not ' populations. ' Option B unnecessarily specifies a ' Salesforce data extension ' (implying a synchronized object from a connected org), which is not indicated anywhere in the scenario and adds an unsupported assumption. Option D, adding attribute fields directly to the contact record, would break the independent-feed requirement, since the contact data extension and the new dataset are updated on different schedules and by different sources. Reference: Data Designer, Data Extension Relationships.

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.

The Web Analytics Connector is Salesforce ' s native product for capturing website behavioral events — page views, purchases, and other on-site interactions — and making that data available as a Journey Builder entry event source, allowing contacts who complete a specific behavior (in this case, a purchase without a subsequent review) to be automatically evaluated and injected into a journey based on that real website activity. This is precisely the native, purpose-built pathway for behavior-triggered journey entry driven by web analytics events, matching the stated requirement to have Journey Builder ' automatically inject ' qualifying contacts. Google Analytics 360 (B) is a third-party analytics platform; while it can track similar on-site behavior, it does not natively integrate as a documented Journey Builder entry event source in the way the Web Analytics Connector does. Data Studio (C) is not a Salesforce Marketing Cloud product name relevant to this ecosystem. Audience Studio (D) is Salesforce ' s data management platform (DMP), oriented toward broader audience segmentation and activation across paid media channels, not toward capturing individual on-site purchase/review behavior for direct journey-entry triggering. Consultants should map any ' trigger a journey based on specific website behavior ' requirement directly to the Web Analytics Connector. Reference: Web Analytics Connector, Journey Builder Entry Events.

A Triggered Send Definition backed by a dedicated Triggered Send Data Extension is the correct architecture here: the developer ' s API call posts the form submission data into the data extension, which fires the associated triggered send within minutes, satisfying the near-immediate delivery requirement. Because the message content lives in Content Builder as a standard editable email, marketing users can update creative, imagery, and copy independently at any time without needing the developer to touch the API integration or trigger logic — the two concerns are cleanly separated. The developer ' s involvement is limited to the one-time API integration that posts data into the data extension, not to ongoing content changes. Option B, invoking WSProxy via SSJS, is a legacy, code-heavy pattern that couples send logic to hand-written script, working against the requirement that non-developers control creative independently. Options C and D, hourly-scheduled Automation Studio activities, cannot meet the ' within a few minutes ' delivery SLA, since they only evaluate and send on a fixed hourly cadence rather than immediately upon form submission. Triggered Send Data Extensions are the standard, exam-tested pattern for fast, API-driven, marketer-editable transactional-style emails. Reference: Triggered Send Definitions, Triggered Send Data Extensions.

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.

Marketing Cloud ' s Package Manager is the AppExchange-listed extension product specifically built to bundle and migrate Marketing Cloud assets — including data extensions, journeys, automations, and related configuration — across separate Marketing Cloud accounts representing different environments (development, UAT, production), which directly addresses the deployment pipeline NTO has established across its three isolated account environments. Because entirely separate Marketing Cloud accounts (rather than Business Units within one account) don ' t share a native built-in migration path the way Change Sets do within a single Salesforce org, a dedicated tool purpose-built for cross-account Marketing Cloud asset migration is required, and Package Manager fills that role. Change Sets (D) are a Salesforce Sales/Service Cloud deployment mechanism for metadata migration between connected Salesforce orgs and sandboxes — they do not migrate Marketing Cloud-native objects like journeys and data extensions between separate Marketing Cloud accounts. The Ant Migration Tool (B) is likewise a Salesforce Salesforce.com metadata deployment utility for Apex/Visualforce-style development, unrelated to Marketing Cloud asset migration. ' Configuration Manager ' (C) is not a recognized Salesforce Marketing Cloud product name. Reference: Marketing Cloud Package Manager, Multi-Environment Deployment Strategy.