Sign in
Home/Salesforce/Certified Marketing Cloud Administrator/Free questions

Certified Marketing Cloud Administrator — Free Practice Questions

10 free sample questions from a bank of 57, with the correct answers and explanations. No signup required — start practising right now.

1Northern Trail Outfitters wants a data model in Marketing Cloud which will prevent them from duplicating, or even triplicating, records. How should the unique identifier of the data model be set up if the MobilePush and Email channels are used within the same account?
  • Strategically control the Contact Key values and tie records together across channels using this key.
  • Use a third-party system to identify and delete duplicate Contact Keys.
  • Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel used.
Answer: A

Verdict: A - Strategically control the Contact Key values and tie records together across channels using this key

The short version

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.

Key concepts

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.

Why A is correct

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.

Why the others are wrong

  • B. "Use a third-party system to identify and delete duplicate Contact Keys" is a cleanup strategy, not a data model. Duplicates created inside Marketing Cloud have to be merged in Marketing Cloud; an external tool can find candidates but cannot make the platform treat them as one contact, so prevention -- which is what the stem asks for -- never happens.
  • C. "Use the auto-generated keys supplied by Marketing Cloud at time of record creation for each channel" is precisely what creates the duplicates. Keys generated per channel mean the same person has a different SubscriberKey in each channel, so the model cannot tie the records together and duplicate, triplicate rows accumulate in All Subscribers.

Marketing-Cloud-Administrator exam tip

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.

2What are entry source types for Journey Builder?
  • Data Extension, Audience Studio, API Event, Date Based Event
  • Data Extension, CloudPages, Email List, API Event
  • Data Extension, Email List, API Event, Date Based Event
Answer: A

Verdict: A - Data Extension, Audience Studio, API Event, Date Based Event

The short version

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.

Key concepts

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.

Why A is correct

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.

Why the others are wrong

  • B. "Data Extension, CloudPages, Email List, API Event" substitutes CloudPages and Email List, neither of which is a Journey Builder entry source type. CloudPages is a landing-page and microsite hosting product you can link to from journey content, and Email List is a legacy audience structure, not an entry source you configure in Entry Source Administration.
  • C. "Data Extension, Email List, API Event, Date Based Event" is the closest distractor: it has three correct entries and one wrong one. Email List is not an entry source type -- the platform's list-based equivalent is an audience, not a classic list -- so this set cannot be the complete list of entry sources.

Marketing-Cloud-Administrator exam tip

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.

3A Marketing Cloud admin is configuring a journey using Path Optimizer. They want to hold back 60% of the contacts until a winner has been selected. What is required to configure the Holdback percentage?
  • No more than two paths
  • Evaluation period must be 72 hours
  • Run Once schedule type
Answer: C

Verdict: C - Run Once schedule type

The short version

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.

Key concepts

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.

Why C is correct

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.

Why the others are wrong

  • A. "No more than two paths" is simply false. Path Optimizer supports up to ten paths, and the two-to-eight path variants in other dumps of this question were never a documented ceiling.
  • B. "Evaluation period must be 72 hours" is invented. The period is user-configurable from 1 hour to 99 days, so a 72-hour window is a choice, not a prerequisite for the holdback field.

Marketing-Cloud-Administrator exam tip

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.

4Northern Trail Outfitters is migrating from a small, in-house email solution to Marketing Cloud. What should the Marketing Cloud admin consider when sending from the new IP Address?
  • Building desirable sending history and data will be variable based on list size and engagement.
  • The IP address is on reserve, is already in use, and has an email sending history.
  • Sending ISPs notification of the new IP Address.
Answer: A

Verdict: A - Building desirable sending history and data will be variable based on list size and engagement

The short version

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.

Key concepts

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."

Why A is correct

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.

Why the others are wrong

  • B. "The IP address is on reserve, is already in use, and has an email sending history" is the opposite of the documented behaviour. Trailhead: the purchased IP is "unused, with no email sending history or sender reputation". That is the whole reason warming is required.
  • C. "Sending ISPs notification of the new IP Address" is not a mechanism that exists. There is no ISP notification step in IP warming; the levers are gradual volume, authentication records (SPF/DKIM), list quality and engagement. Announcing yourself to a mailbox provider is not a thing you can do from Setup.

Marketing-Cloud-Administrator exam tip

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.

5Northern Trail Outfitters wants to deploy sends through Journey Builder to business users who spend their day in Sales Cloud, without granting access to Marketing Cloud directly. What feature should be used?
  • Marketing Cloud Connect
  • Distributed Sending
  • Distributed Marketing
Answer: A

Verdict: A - Marketing Cloud Connect

The short version

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.

Key concepts

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.

Why A is correct

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.

Why the others are wrong

  • B. Distributed Sending only changes who a child BU may send for. It has nothing to do with Sales Cloud, and it does not put any user interface in front of CRM users.
  • C. Distributed Marketing restructures the account's brand and sending architecture: a parent BU onboards brands, child BUs share its send classes and content, and one sending identity covers them. It solves multi-brand governance, not "give the sales team access to marketing", which is why a 100% vote for it is a misread of the stem.

Marketing-Cloud-Administrator exam tip

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.

6Northern Trail Outfitters wants to segment audiences based on Sales Cloud data. Where would their Cloud admin configure Sales Cloud Objects to be synced and leveraged in Marketing Cloud?
  • Contact Builder > Data Sources
  • Setup > Data Management > Synchronized Data Extensions
  • Contact Builder > Data Extensions > Synchronized Data Extensions
Answer: A

Verdict: A - Contact Builder > Data Sources

The short version

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.

Key concepts

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.

Why A is correct

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.

Why the others are wrong

  • B. "Setup > Data Management > Synchronized Data Extensions" is where you can refresh or reconfigure the already-created synchronized data extensions, and where the general sync schedule options live. It is not the place you define which Sales Cloud objects and fields Marketing Cloud should bring in, so a new object cannot be added from there.
  • C. "Contact Builder > Data Extensions > Synchronized Data Extensions" is the output of the configuration, not the configuration itself. That folder only lists the synchronized data extensions Marketing Cloud has already created from a data source, which is exactly the trap: you cannot create a sync from the screen that only displays existing syncs.

Marketing-Cloud-Administrator exam tip

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.

7Northern Trail Outfitters wants to leverage the REST API for an external application they plan to build. Where should their Marketing Cloud admin set up permissions to allow REST authentication?
  • Data Management
  • Installed Packages
  • Salesforce Integration
Answer: B

The short version

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.

Key concepts in this question

  • Installed Packages: Setup area (Apps > Installed Packages) where API integrations and apps are created and permissioned.
  • API integration component: The package component that issues client ID/secret and defines REST/SOAP permission scopes.
  • REST authentication: OAuth 2.0 token flow against the package credentials.

Why B is correct

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.

Why the others are wrong

  • A. Data Management covers FTP accounts, file locations, and data configuration, not API credential issuance.
  • C. Salesforce Integration configures Marketing Cloud Connect to Sales/Service Cloud, not third-party REST authentication.

Certified-Marketing-Cloud-Administrator exam tip

Think packages = keys: any external app needing the API starts in Setup > Apps > Installed Packages.

8To prevent retention of stagnant data, Northern Trail Outfitters wants any inactive data stored in data extensions to be cleared after 12 months. What action should be taken?
  • Apply a Row Based Retention to each data extension as it is created, set to 12 months
  • Configure the business unit data retention setting to 12 months
  • Set inactive data to be automatically cleared after one year, but is recoverable
Answer: A

Verdict: A - Apply a Row Based Retention to each data extension as it is created, set to 12 months

The short version

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.

Key concepts

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.

Why A is correct

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.

Why the others are wrong

  • B. "Configure the business unit data retention setting to 12 months" describes a control that does not exist in that form. Retention is not configured once per business unit; it is a property of each data extension, and there is no account or BU-level retention switch that would clear rows across every extension.
  • C. "Set inactive data to be automatically cleared after one year, but is recoverable" contradicts the requirement. Deleting the rows after 12 months is the point -- a retention policy that leaves the data recoverable is not clearing anything, and no Marketing Cloud retention mode stores expired rows for later recovery.

Marketing-Cloud-Administrator exam tip

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.

9Northern Trail Outfitters (NTO) uses Sender Authentication Package (SAP) for branding purposes. Their German business unit is configured with the SAP domain de.ntomarketing.com. The German NTO team is preparing for a campaign and wants to use customized CloudPages with the domain de-special.ntomarketing.com. How could the Marketing Cloud admin meet this requirement?
  • CloudPages must use the SAP domain.
  • Purchase a new SAP for de-special.ntomarketing.com.
  • Purchase a new Private Domain for use in CloudPages.
Answer: C

Verdict: C - Purchase a new Private Domain for use in CloudPages

The short version

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.

Key concepts

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.

Why C is correct

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.

Why the others are wrong

  • A. "CloudPages must use the SAP domain" is the constraint that creates the problem, not the solution. The SAP domain is already taken by the existing branding, and view-as-webpage links and images can only point at that one domain, so this option cannot deliver the second domain the team is asking for.
  • B. "Purchase a new SAP for de-special.ntomarketing.com" cannot be done inside that business unit. A business unit supports only one SAP for branding, so a second SAP in the same unit is not a valid configuration; the extra domain has to come from private domain management.

Marketing-Cloud-Administrator exam tip

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.

10Northern Trail Outfitters wants to copy journeys across business units. What could be used to replicate journey structure so it can be easily recreated in another account?
  • Journey Extracts
  • Package Manager
  • Journey Templates
Answer: B

The short version

B — Package Manager replicates journeys across business units. It bundles a journey plus dependencies and deploys the bundle to another business unit or account.

Key concepts in this question

  • Package Manager: Deployment tool that packages journeys, automations, data extensions, and assets.
  • Journey structure replication: Copying canvas, activities, and dependencies rather than rebuilding by hand.
  • Cross-BU deployment: Moving the bundle into another business unit in the enterprise.

Why B is correct

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.

Why the others are wrong

  • A. Journey Extracts is not a Marketing Cloud deployment mechanism for copying journeys.
  • C. Journey Templates provide reusable starting layouts, not cross-BU deployment of a built journey with dependencies.

Certified-Marketing-Cloud-Administrator exam tip

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.