10 free sample questions from a bank of 57, with the correct answers and explanations. No signup required — start practising right now.
Verdict: A - Strategically control the Contact Key values and tie records together across channels using this key
The Sendable Data Model has exactly one identity per contact. If that identity is the Contact Key you control, the same person resolves to one record across MobilePush and Email; if you let the platform invent keys per channel, you get duplicates.
The ContactKey is the field Marketing Cloud uses to recognise a subscriber, and the Sendable Data Model in Contact Builder is how you nominate which field plays that role. Choosing the ContactKey from the outset is what lets MobilePush, Email Studio and Journey Builder activities treat records from different channels as one person. When keys are auto-generated per channel at record creation, the same subscriber arrives as two identities -- and Marketing Cloud's documented behaviour is that a second subscriber record is appended to All Subscribers if the SubscriberKey is not already there.
The requirement is prevention of duplication at the data-model level across MobilePush and Email. Controlling the ContactKey values yourself and linking records with that key is the only way to guarantee one identity per person, because the model is defined once, before any channel starts writing rows. Strategic control also lets the key match the CRM identifier so journeys and sends reconcile.
Data-model questions hinge on identity. Decide the ContactKey deliberately and reuse it across every channel; auto-generated per-channel keys are the root cause of duplicate subscribers, not the cure.
Verdict: A - Data Extension, Audience Studio, API Event, Date Based Event
Journey Builder entry sources come in two families: things that push contacts in (data extension, audience, API event) and things that happen on a schedule (date based event). All four in option A are real entry source types.
Journey Builder's entry sources break down as follows. A Data Extension Entry Source reads rows from a sendable data extension, re-entering the journey when new records appear. Salesforce Data Extension / Audience entry sources read from Contact Builder audiences built on synced Salesforce objects. API Event entry sources fire when an external system calls the REST API to inject a contact into the journey. Date Based Event entry sources fire once, or on a recurring schedule, with no subscriber payload. Salesforce data, streaming and event sources extend the same idea.
Every item in this option is a genuine entry source type in Journey Builder: a data extension, an audience built in Audience Studio, an API event, and a date based event. That combination covers the full range the question is testing -- record-driven, CRM-driven, system-driven and time-driven entry -- which is what makes it the right list rather than a plausible-looking mix.
Learn entry sources as two families: push sources (data extension, audience, API event) and time sources (date based event). Classic Email List and CloudPages are not entry sources.
Verdict: C - Run Once schedule type
A holdback reserves a slice of the audience and only releases it once a winner is chosen. That arithmetic needs one fixed audience and one evaluation, which is what the Run Once schedule type gives you.
Path Optimizer splits a journey into as many as ten competing paths and either picks the winner automatically on an engagement metric or lets an admin choose it manually. Two knobs govern the test: the evaluation period (engagementPeriod, configurable in hours or days, minimum 1 hour, maximum 99 days) and the holdback percentage (holdbackPercentage). Because holdback reserves part of the audience for later release, the journey has to enter evaluation as a single, known population.
Salesforce documents Path Optimizer as splitting a journey "into as many as 10 paths", so a path-count ceiling is not a real constraint. The same doc says the evaluation period "can be configured in hours or days with a minimum of 1 hour and a maximum of 99 days", which rules out any fixed 72-hour requirement. The only setting that actually gates the holdback field is the journey's Run Once (single evaluation) schedule type: with a repeating or continuous schedule the population keeps changing and a fixed holdback percentage, and a consistent winner, could not be computed.
When a Path Optimizer question mentions holdback or winner selection, think about what the test needs to know in advance: a single known audience. That is the Run Once / single-evaluation shape, and it is the same reason the multi-select variant of this question asks for a schedule type plus a winner evaluation criterion.
Verdict: A - Building desirable sending history and data will be variable based on list size and engagement
A dedicated IP arrives cold. Mailbox providers throttle anything from an address with no history, so the admin's real work is ramping volume and letting engagement build the reputation -- and how long that takes depends on list size and how engaged the list is.
IP warming is "the process of gradually increasing the volume of mail sent by a new IP address" until mailbox providers have a picture of the mail coming from it. Trailhead is explicit that a new IP is "unused, with no email sending history or sender reputation" and that "there is no such thing as a pre-warmed IP". Ramp duration is not fixed: "Factors such as your overall list size, list quality, send frequency, and subscriber engagement can influence the amount of time it takes."
Option A restates the documented reality. Reputation is accumulated through sending history, and Salesforce says the time it takes to reach it is "variable based on list size and engagement" -- which is why warming schedules are tiered by engagement or opt-in recency instead of a fixed calendar. The admin's planning question after a migration is exactly this one: how much can I send, and how long until the IP is warm.
Treat "new IP" questions as reputation questions. Mailbox providers watch unknown senders, so the answer is almost always about building sending history from engaged subscribers -- never about an administrative notification step that has no corresponding feature.
Verdict: A - Marketing Cloud Connect
When the audience spends its day in Sales Cloud and must never be given a Marketing Cloud login, you extend Marketing Cloud into the CRM with the connector, not by reshaping the account. That is Marketing Cloud Connect.
Three similarly named features cause the confusion. Marketing Cloud Connect (MCC) connects a Marketing Cloud account to a Sales or Service Cloud org, letting CRM users work with campaign members, send from approved content and see tracking without holding Marketing Cloud seats. Distributed Marketing lets child business units share the parent BU's brand, send classes and content so several brands appear to come from one sender. Distributed Sending lets a child BU send on behalf of another BU using that BU's sender profiles and send classes.
The requirement is "business users who spend their day in Sales Cloud, without granting access to Marketing Cloud directly". MCC is documented as the integration for exactly that: the setup path is "Connect your Marketing Cloud Engagement account to the corresponding Sales or Service Cloud org at the account level", and the business units assigned to the MCC API user determine "which business units are available for use within Sales or Service Cloud". CRM users get campaign and send functionality from inside the CRM; no Marketing Cloud licence is consumed.
Anchor on the phrase "without granting access to Marketing Cloud directly". Connect = CRM integration. Distributed = the account's own multi-BU sending architecture. If the users live in Sales Cloud, it is Connect; if the brands live in child BUs, it is Distributed Marketing.
Verdict: A - Contact Builder > Data Sources
Sales Cloud objects are brought into Marketing Cloud as Contact Builder data sources. Once they are synced, the synchronized data extensions show up underneath that source, not somewhere you create them.
Contact Builder holds three things: the Sendable Data Model (attribute groups, data extensions and relationships), Data Sources, and Data Extensions. For Salesforce data, the flow is: setup the synchronized data sources from Setup, then in Contact Builder > Data Sources choose which Salesforce objects and fields to sync. Marketing Cloud creates synchronized data extensions underneath the source, and only those can then be dragged into Data Designer for the sendable data model.
The question asks where to configure Sales Cloud objects "to be synced and leveraged". Configuration of the sync lives in Contact Builder > Data Sources, which is the screen that lists each connected CRM object, its fields, and the refresh. Everything downstream -- the synchronized data extensions, the attribute groups, the relationships used by Journey Builder and Email Studio -- is generated from that choice.
Data source first, then data extensions. Contact Builder > Data Sources creates and configures the sync; the synchronized data extensions underneath it are a read-only consequence of that setup.
B — Installed Packages is where REST API access is provisioned. The admin creates an installed package with an API-integration component to issue the client ID and secret.
REST API credentials come from an API integration added to an installed package, and the permission scopes granted there control what the external application can do. Salesforce documents that you obtain the client ID and secret by adding an API integration to the installed package and authenticate with those credentials. Neither Data Management nor Salesforce Integration issues REST credentials.
Think packages = keys: any external app needing the API starts in Setup > Apps > Installed Packages.
Verdict: A - Apply a Row Based Retention to each data extension as it is created, set to 12 months
Retention in Marketing Cloud is set on the data extension, one object at a time. A row-based retention of 12 months clears rows older than a year as they age, which is what "cleared after 12 months" requires.
Data extension retention has two independent flags. Auto Delete removes the data extension itself once it is empty of records. Row Based Retention deletes rows a set number of months after they were last updated, which prunes stale records while leaving the structure (and its field definitions, automations and links) intact. Both live on the data extension's properties, and retention can be reset on import if you want the clock to restart with each update.
The requirement is specific: inactive data held in data extensions should be cleared after 12 months. Row Based Retention measured in months does precisely that, and setting it as each extension is created makes the policy repeatable instead of an after-the-fact cleanup project. It is also the retention option that keeps the extension usable, so downstream automations, queries and journey entry sources keep working.
Retention questions: row-based retention prunes rows and keeps the extension; auto delete removes the extension when empty. Both are per data extension, never a business-unit-wide setting.
Verdict: C - Purchase a new Private Domain for use in CloudPages
A business unit can only have one Sender Authentication Package, so de.ntomarketing.com is already spoken for by view-as-webpage links and images. A private domain is the separate mechanism that lets the German team host CloudPages on de-special.ntomarketing.com.
Marketing Cloud has two independent domain concepts. A Sender Authentication Package (SAP) is the branded sending identity for a business unit: it carries the custom domain, its subdomains, and the from-address and link-wrapping behaviour, and it is what makes view-as-webpage links and embedded images resolve to that domain. There is one SAP per business unit. Private domains are managed separately (Private Domain Management) for the account and a business unit can hold several; they are used for sending from additional addresses and can be assigned for link wrapping and hosted content.
The SAP for the German unit is already configured against de.ntomarketing.com, and a business unit supports only one SAP, so the SAP cannot be re-pointed or duplicated for a second custom domain within the same unit. A private domain is the supported way to add a second, separately managed domain and point hosted content such as CloudPages at it, which is what the de-special.ntomarketing.com requirement needs.
One SAP per business unit, many private domains per account. When a team needs a custom domain beyond the SAP, the answer is a private domain -- not a second SAP.
B — Package Manager replicates journeys across business units. It bundles a journey plus dependencies and deploys the bundle to another business unit or account.
Package Manager exists to bundle journeys or automations with all their dependencies and deploy them to other business units, which is exactly the replicate-and-recreate requirement. Journey Templates save a layout for reuse but do not transport dependencies across business units, and there is no Journey Extracts deployment product.
Copying built journeys between BUs = Package Manager; starting new ones from a layout = template.
Want the full bank of 57 questions for Certified Marketing Cloud Administrator? See all practice exams.