MC-Con-201 Salesforce Certified Marketing Cloud Next Consultant Exam Topics and Questions

Marketing Cloud Next runs on Core, not the legacy Marketing Cloud stack, so the technical foundations matter from day one. You need to know what makes an environment ready, how Business Units and workspaces divide content and users, and how domain authentication keeps emails landing in inboxes instead of spam folders. Miss the setup detail and you will lose marks on scenarios that turn on provisioning order or permission scope.

– Environment requirements and provisioning

The exam expects you to understand the prerequisites before Marketing Cloud Next goes live. Core Org Edition requirements determine whether the instance can support the platform at all, and Data 360 provisioning is a separate step that candidates often assume happens automatically. Marketing Data Kit installation brings the schema and objects into place, but you need to know what it delivers and when permission sets must be assigned. The sequence matters. Provision in the wrong order and features stay locked. The exam tests whether you can identify what is missing when a scenario describes an incomplete environment or a user who cannot access expected functionality.

– Business Units, roles and workspace governance

Business Units partition content, users and sending reputation. The exam asks when they are required, not just allowed. Scenarios describe organizational structures, brand separation, or compliance boundaries, and you must decide whether a single unit suffices or multiple units are necessary. Roles control what users can do, and Enhanced CMS Workspaces control what content they can see and edit. Governance models fail when permissions are too broad or workspace boundaries are too narrow. Candidates lose marks by recommending Business Units where roles and workspaces would suffice, or by ignoring the reputational risk of mixing transactional and promotional sends in one unit.

– Domain authentication and authorization

Self-service domain authentication and domain authorization are not the same thing, and the exam tests the distinction. Authentication proves the sender owns the domain. Authorization allows Marketing Cloud Next to send on behalf of that domain. Both are necessary for branded, authenticated delivery, and both require DNS records. Scenarios describe delivery problems, authentication errors, or branding requirements, and you must identify which piece is missing or misconfigured. Candidates who treat domain setup as a checkbox step rather than a conditional troubleshooting skill will miss these items.

How Platform Setup & Governance is tested

At thirteen percent, this topic seeds the exam with items that check whether you understand the platform's boundaries before you configure anything on top of it. Expect scenarios that describe incomplete environments, missing permissions, or delivery failures tied to domain configuration. The demand is diagnostic: you are given symptoms and must identify the root cause in setup or governance. Items often hinge on sequence, such as whether Data 360 was provisioned before or after the Marketing Data Kit was installed, or whether a role grants the permission needed for a specific task. Candidates lose marks by assuming every feature is available out of the box, or by recommending Business Units when the scenario calls for workspace separation instead. The trap is treating setup as a one-time checklist rather than a troubleshooting skill that surfaces throughout the exam.

Once the platform is running, the next gate is consent. Marketing Cloud Next treats consent as a first-class platform object, not a custom field or an external system lookup. You need to know the consent object model, how records are created and updated, and how banners collect preferences on landing pages and external sites. The exam tests whether you can design a consent flow that meets both business requirements and compliance obligations.

How Consent is tested

Consent carries the same weight as platform setup, so expect multiple items across different scenario types. The exam presents business requirements that describe consent collection points, preference changes, and compliance constraints, then asks you to choose the right method for creating or updating consent records. You must distinguish between the platform consent objects and understand their relationships, because items often hinge on which object holds which piece of the consent picture. Consent banner configuration is another frequent focus: scenarios describe landing pages, external sites, and branding requirements, and you must determine how to configure the banner to capture the necessary preferences. Candidates lose marks by conflating consent capture with list subscription, or by choosing a manual update method when an automated one is required. The trap is assuming consent is a simple boolean when the platform models it as a structured, auditable object with specific lifecycle rules.

This is the heaviest topic on the exam, and it is where most candidates either prove their depth or run out of time. Data 360 is the engine that connects, harmonizes, unifies and activates customer data, and you need to understand the object model, how CRM data flows in, and how Identity Resolution links records into unified profiles. The exam also tests consumption entitlements, because design decisions that seem harmless can burn through platform limits fast.

– Data 360 objects and how they connect customer data

Data objects in Data 360 are not tables in the legacy sense. They represent customer data from multiple sources, and the platform uses them for segmentation and personalization. You need to know what each object type does, how objects relate to one another, and how the platform harmonizes data that arrives in different shapes. The exam tests whether you can look at a business requirement, identify which objects are needed, and explain how those objects support audience segmentation or content personalization. Candidates lose marks by treating Data 360 as a simple database when it is a modeling and unification layer with specific rules about how data is connected and activated.

– CRM data ingestion and Actionable Lists

CRM data flows into Marketing Cloud Next through standard and custom objects, and Actionable Lists are the mechanism that makes CRM records available for segmentation and activation. You must know how objects and records are ingested, what Actionable Lists contain, and when they are required. Scenarios describe CRM data structures, segmentation needs, and personalization requirements, and you must determine how to bring the right data in and make it usable. The exam tests whether you understand the relationship between CRM objects and Data 360 objects, and whether you can identify when an Actionable List is the correct tool. Candidates who assume all CRM data is automatically available for segmentation will miss these items.

– Identity Resolution and unified profiles

Identity Resolution links records from multiple data sources into a single unified profile. The exam expects you to configure it, not just describe it. You need to know which fields serve as matching keys, how conflicting data is resolved, and what happens when a match fails. Scenarios describe fragmented customer data, duplicate records, and cross-channel identity problems, and you must determine how to configure Identity Resolution to unify the profile. The trap is assuming Identity Resolution works automatically. It does not. You must tell the platform which fields to match on, and the exam tests whether you can make that decision given a business requirement and a data structure.

– Consumption entitlements and design impact

Data 360 is consumption-based, and design decisions affect how much capacity you burn. The exam tests whether you understand what counts against entitlements and how to evaluate design choices that trade functionality for consumption. Scenarios describe segmentation strategies, activation patterns, and data refresh frequencies, and you must identify which approach stays within limits and which does not. Candidates lose marks by designing solutions that work functionally but exceed consumption entitlements, or by failing to recognize when a design choice has a consumption cost. This is not a minor detail. It is a core design skill, and the exam treats it that way.

How Data Modeling, Identity Resolution & Segmentation is tested

At twenty-five percent, this topic is the center of gravity. Expect scenarios that give you a business requirement, a data structure, and a set of segmentation or personalization needs, then ask you to identify the right objects, configure Identity Resolution, or evaluate a design for consumption impact. The exam tests your ability to move from requirement to implementation, not your ability to define what Data 360 is. Items often present incomplete or conflicting data and ask how to unify it, or describe a segmentation need and ask which object or Actionable List satisfies it. Candidates lose marks by choosing the first plausible answer instead of the one that fits the data structure and the business constraint. The trap is treating this as a modeling exercise when it is a design and troubleshooting exercise. You must know what works, what breaks, and what burns through entitlements.

This is the heaviest topic, and it is where the exam tests whether you can build and orchestrate campaigns end to end. You need to know how to personalize content using Handlebars, AMPscript, merge fields, repeaters and content variations. You need to choose the right flow type, configure triggers, add the correct data source, and assemble flow elements into working automation. Activation templates and landing pages round out the topic. The exam assumes you have built these before.

– Personalization methods and channel content

Personalization in Marketing Cloud Next uses Handlebars, AMPscript, merge fields, repeaters, and content variations. Each has a purpose, and the exam tests whether you can choose the right one for a given scenario. Handlebars is the modern syntax. AMPscript persists for legacy compatibility and specific functions. Merge fields are simple token replacements. Repeaters handle dynamic lists. Content variations swap entire blocks based on conditions. Scenarios describe personalization requirements, data sources, and channel constraints, and you must determine which method delivers the outcome. Candidates lose marks by defaulting to one syntax when another is required, or by choosing a method that works in email but not in SMS or push.

– Flow types, triggers and configuration

Flows orchestrate campaigns, and the exam expects you to choose the correct flow type and configure its trigger conditions. Transactional flows, scheduled flows, and event-triggered flows each serve different use cases. Trigger conditions determine when a flow runs, and configuration settings control how it behaves. Scenarios describe marketing outcomes, timing requirements, and data availability, and you must determine which flow type and trigger configuration achieve the desired result. The trap is choosing a flow type that almost works but fails under a specific condition the scenario describes, such as a timing constraint or a data dependency.

– Data sources for messaging content

Flows need data to personalize messages, and you must choose the correct data source for each scenario. The exam tests whether you understand which data sources are available, what data they contain, and when each is appropriate. Scenarios describe personalization needs, data location, and real-time requirements, and you must identify the data source that supplies the necessary fields at the necessary time. Candidates lose marks by choosing a data source that contains the field but does not refresh in time, or by selecting a source that requires additional configuration the scenario does not allow.

– Flow elements, logic and automation

Flow elements are the building blocks of automation. You need to know what each element does, how elements connect, and how logic branches based on conditions. The exam presents scenarios that describe business processes, decision points, and messaging activities, and you must assemble the correct sequence of elements to automate the process. This is not drag-and-drop memorization. You must understand how data moves through a flow, how decisions are evaluated, and what happens when a condition fails. Candidates lose marks by choosing elements that perform similar but not identical functions, or by configuring logic that works for one path but breaks another.

– Activation templates and landing pages

Activation templates select the contact point value for each recipient, such as email address or mobile number. The exam tests whether you can configure templates to choose the correct field based on channel and data source. Landing pages require components and configuration, and scenarios describe business requirements for forms, content blocks, and consent capture. You must identify which components are needed and how they are configured. Candidates lose marks by assuming the default contact point is always correct, or by missing a landing page component the scenario requires.

How Campaign Design, Flow Orchestration & Content is tested

At thirty percent, this topic dominates the exam. Expect scenarios that describe a marketing outcome, a data structure, a timing requirement, and a set of constraints, then ask you to choose the correct personalization method, flow type, data source, or sequence of flow elements. The demand is practical: you must know what each tool does, when it applies, and how to configure it. Items often present plausible but incorrect answers that work in a different context but fail under the scenario's specific constraints. Candidates lose marks by choosing the first familiar option instead of the one that fits every requirement. The trap is assuming you can reason your way through these items without hands-on experience. You cannot. The exam tests configuration detail, not conceptual understanding.

AI features in Marketing Cloud Next automate campaign creation, audience segmentation, content generation, conversational messaging, and predictive insights. The exam tests whether you can choose the right AI feature for a given scenario, configure conversational messaging to handle customer engagement and response flows, and apply marketing agents to automate tasks that would otherwise require manual work. This is not theoretical. You need to know what each feature does and when it applies.

– Marketing agents and automation

Marketing agents automate campaign creation, audience segmentation, and content generation. The exam presents scenarios that describe repetitive tasks, segmentation needs, or content production requirements, and you must determine when a marketing agent is the correct tool and how to configure it. Candidates lose marks by choosing agents when manual configuration is more appropriate, or by failing to recognize when an agent can replace a multi-step manual process. The exam tests practical application, not feature awareness.

– Conversational messaging configuration

Conversational messaging supports customer engagement, response handling, and ongoing interactions across messaging channels. You need to know how to configure conversations, handle responses, and maintain context across multiple interactions. Scenarios describe customer engagement requirements, channel constraints, and response patterns, and you must determine how to configure conversational messaging to meet the need. The trap is assuming conversational messaging works like broadcast messaging. It does not. Context and response handling are part of the configuration, and the exam tests whether you understand how to build a conversation flow that adapts to customer input.

– Predictive AI feature selection

Predictive AI features analyze data and surface insights that inform campaign decisions. The exam tests whether you can determine which predictive feature applies to a given scenario. Scenarios describe business goals, available data, and desired outcomes, and you must choose the feature that delivers the prediction or insight the scenario requires. Candidates lose marks by choosing a feature that sounds relevant but does not match the data structure or the outcome, or by failing to recognize when a predictive feature is unnecessary because the data already provides the answer.

How Agentforce & AI Innovation is tested

At eleven percent, this topic appears often enough that you cannot afford to guess. The exam presents scenarios that describe automation opportunities, conversational engagement needs, or predictive insight requirements, and you must choose the correct AI feature and configuration. The demand is practical: you must know what each feature does, what data it requires, and when it applies. Items often present plausible but incorrect AI features that solve a different problem or require data the scenario does not provide. Candidates lose marks by choosing the newest or most impressive-sounding feature instead of the one that fits the scenario's constraints. The trap is treating AI features as interchangeable when each has specific use cases, data requirements, and configuration rules.

Analytics close the loop. Marketing Cloud Next provides pre-built dashboards and cross-platform reporting, and the exam tests whether you can choose the right dashboard for a reporting requirement and surface marketing data across Salesforce. This is the lightest topic, but the items still require you to know what each dashboard contains and how data flows between Marketing Cloud Next and the rest of the platform.

How Analytics & Performance Insights is tested

At eight percent, this topic seeds the exam with items that test whether you can match a reporting requirement to a pre-built dashboard, or determine how to surface marketing data in other Salesforce clouds. Scenarios describe reporting needs, stakeholder requirements, and data visibility constraints, and you must choose the dashboard or reporting method that satisfies the need. The demand is practical: you must know what each pre-built dashboard contains, what metrics it surfaces, and when it is the correct choice. Items often present dashboards that seem relevant but do not contain the specific metric or dimension the scenario requires. Candidates lose marks by choosing a dashboard based on its name rather than its contents, or by failing to recognize when data must be surfaced outside Marketing Cloud Next using cross-platform reporting. The trap is assuming all dashboards are interchangeable or that any dashboard can be customized to show any metric.