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

Certified Marketing Cloud Consultant — Free Practice Questions

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

1A bank wants to send out a series of emails to new customers that open a checking or savings account. The emails will be used to educate and inform customers regarding their current account and other bank offerings. ✑ Data for the campaign will be in two data extensions: Customer and New Accounts. ✑ The Customer data extension is currently used for multiple campaigns and is updated at 1:00 a.m. ✑ The New Accounts data is encrypted and will be placed on the SFTP at 10:00 p.m. Which automated workflow meets the customers' requirements?
  • A scheduled automation which starts at 2:00 a.m. and executes Data Extract Activity > Import File Activity > SQL Query Activity > Wait Activity > Send Email Activity.
  • A drop automation which executes File Transfer Activity > Import File Activity > SQL Query Activity > Wait Activity > Send Email Activity.
  • A scheduled automation which starts at 2:00 a.m. and executes a File Transfer Activity > Import File Activity > SQL Query Activities > Wait Activity > Send Email Activity.
  • A scheduled automation which starts at 12:00 a.m. and executes a File Transfer Activity > Import File Activity > SQL Query Activities > Wait Activity > Send Email Activity.
Answer: C

The short version

C — Scheduled 2 a.m. automation with File Transfer, Import, SQL, Wait and Send wins. It is the only sequence that waits for both the 10 p.m. encrypted SFTP drop and the 1 a.m. Customer refresh, decrypts the file, then joins the two data extensions before sending the education series.

Key concepts in this question

  • Scheduled automation: runs at a fixed clock time, ideal when multiple upstream feeds must be ready first.
  • File Transfer Activity: decrypts files on the SFTP, a mandatory first step for encrypted sources.
  • Import plus SQL join: Import File Activity loads New Accounts into a staging data extension, then SQL Query Activities join it to the Customer data extension to build the sendable audience.
  • Wait plus Send sequence: Wait Activities space the onboarding education emails over days or weeks, while Send Email Activities execute each message against the joined audience.

Why C is correct

C starts at 2 a.m., which is after both critical dependencies are met, namely the New Accounts file placed at 10 p.m. and the Customer data extension refresh at 1 a.m. It includes a File Transfer Activity to decrypt and retrieve the encrypted file, followed by Import File Activity and SQL Query Activities to stage and join the data correctly. That yields a complete current audience for the Wait and Send steps.

Why the others are wrong

  • A. Omits File Transfer Activity, so the encrypted SFTP file can never be decrypted and imported successfully.
  • B. Uses a file-drop trigger that fires when the 10 p.m. file lands, before the 1 a.m. Customer update is complete, producing stale joins.
  • D. Starts at midnight, also before the 1 a.m. Customer refresh finishes, so the join misses the latest customer records.

Certified-Marketing-Cloud-Consultant exam tip

If the file is encrypted, look for File Transfer first, then pick a start time after the latest data refresh in the story.

2A user in Marketing Cloud needs to send an email to a Salesforce Report via a Send Flow process. How should the consultant meet this requirement?
  • Assign the integrated user the Marketing Cloud for AppExchange User permission in Sales Cloud.
  • Create data validation rules for the integrated user in Sales Cloud.
  • Create a Salesforce Data Extension for the user to select during a Send Flow.
  • Add custom VisualForce Page to the page layouts in Marketing Cloud.
Answer: C

The short version

C — Salesforce Data Extension carries a Salesforce Report into Send Flow. Send Flow sends Marketing Cloud email from inside Sales or Service Cloud to a report audience, staging members as a Salesforce Data Extension chosen during the flow.

Key concepts in this question

  • Marketing Cloud Connect Send Flow: guided send launched from CRM that builds and dispatches a Marketing Cloud email without leaving Sales or Service Cloud.
  • Salesforce Report as audience: supported Send Flow source when the report returns Contact ID or Lead ID values for identity resolution.
  • Salesforce Data Extension: sendable extension linked to a Salesforce report or campaign that materializes CRM membership for sending and tracking writeback.
  • Folder prerequisites: reports for Connect sends must live in a custom shareable folder the sender can access, since standard folders and joined reports are not supported.

Why C is correct

C is correct because the documented pattern surfaces the report through a Salesforce Data Extension picked during Send Flow. The report supplies ID-keyed rows, Connect maps them into the extension, and the send executes against it so tracking associates back to CRM. Vendor material confirms sending from within Sales Cloud to a report through Connect, with Contact ID or Lead ID fields required and storage in a custom folder.

Why the others are wrong

  • A. AppExchange User permission enables the connector user but does not place a report audience into a send.
  • B. Validation rules enforce data quality on save and do not resolve a report into sendable subscribers.
  • D. A Visualforce page in layouts changes presentation only and creates no report-backed audience.

Certified-Marketing-Cloud-Consultant exam tip

When you see Send Flow plus Salesforce Report, look for Salesforce Data Extension plus ID field plus custom folder.

3A user in the MC wants to use Salesforce custom object data for segmenting and personalization. How should the consultant approach this requirement?
  • Map the custom objects to the profile center and use the email editor to insert the custom data. Create a user-initiated send to associate the email to the largest audience and return tracking data.
  • Sync contact and custom objects with Data Stream and send from Synchronized Data Extension with Salesforce email send. Ensure there is a lookup relationship to a contact or lead record.
  • Create a custom report type that contains the contact or lead ID, email address, and custom object data, then from the marketing cloud, import into a Salesforce Data extension. Use AMPscript in the email to call data.
  • Export report data from the sales cloud and import into a marketing cloud synchronized data extension. Use a filter activity to produce a sendable data extension. Create an email send activity in Automation Studio.
Answer: B

The short version

B — Synchronize Salesforce contact and custom objects with Data Stream and send with Salesforce send. That path brings custom object data natively into Marketing Cloud for segmentation and personalization, preserves the lookup to contact or lead, and keeps tracking aligned with the CRM.

Key concepts in this question

  • Marketing Cloud Connect and Data Stream: the native integration streaming Salesforce objects into Synchronized Data Extensions.
  • Synchronized Data Extensions: read-only mirrored tables maintaining CRM values for filters, journeys and sends.
  • Lookup relationship requirement: custom objects must relate to contact or lead to resolve identity and lookups.
  • Salesforce send context: sending via Synchronized Data Extension preserves identity, reporting and unsubscribe linkage.

Why B is correct

B uses the supported native mechanism instead of fragile manual exports, bringing both contact identity and related custom object rows into Marketing Cloud with relationship integrity intact. The lookup to contact or lead lets AMPscript, filters and Decision Splits traverse from subscriber to custom rows for true one-to-one personalization. Salesforce-context sending preserves tracking and compliance at scale.

Why the others are wrong

  • A. Misuses the profile center mapping and user-initiated send idea, which does not model custom object relationships or segmentation logic.
  • C. Relies on a manual custom report type export and import, creating stale data, extra maintenance and broken relationship handling.
  • D. Exports a report into a synchronized data extension, which misunderstands the object, since synchronized tables are system-managed and cannot be loaded by import.

Certified-Marketing-Cloud-Consultant exam tip

Custom object plus segment plus personalize equals Synchronized Data Extensions with a lookup to contact or lead.

4A marketer wants to create and edit email content, as well as generate reports and manage subscriber data. Using the principle of least privilege, which two pre-defined roles should be assigned? (Choose two.)
  • Administrator
  • Data Manager
  • Content Creator
  • Analyst
Answer: B, C

The short version

The marketer needs email content rights plus reporting and subscriber management, so the least-privilege fit is Content Creator plus Data Manager, answer BC.

Key concepts in this question

Classic Email Studio roles split duties by function: Content Creator covers content creation and editing, Data Manager covers everything else except content including lists, subscribers and data, and Analyst covers only the Tracking and reporting area. Administrator grants the full set and violates least privilege. Least privilege means assigning only roles whose combined permissions cover every listed duty and nothing material beyond that.

Why BC is correct

Content Creator supplies the create-and-edit email content permission the stem requires. Data Manager supplies subscriber and list management plus the data-side access behind generating reports, which is the remaining half of the stem. Salesforce own role example maps a technical marketer who must create and manage assets in Content Builder and run reports as needed to Content Creator plus Data Manager. Together B and C cover all three duties with no administrator-level excess.

Why the others are wrong

Option A, Administrator, grants far more than the listed duties and directly violates the least-privilege instruction, so it is never right when narrower roles suffice. Option D, Analyst, grants Tracking-area reporting but provides neither email content creation nor subscriber management, leaving two of three duties uncovered. Any pairing with A is over-privileged and any pairing built on D for the data half fails.

Certified-Marketing-Cloud-Consultant exam tip

When a stem lists content work plus subscriber or data work, choose Content Creator plus Data Manager. Reserve Analyst for duties limited to viewing tracking and reports, and treat Administrator as a distractor whenever the question says least privilege.

5Northern Trail Outfitters (NTO) uses Marketing Cloud to connect with its individual consumers, retailers and wholesale buyers, and its corporate apparel customers. Marketing Cloud is currently configured with data extensions containing Store, Order, Product, and Contact information. NTO is in the process of implementing Data Designer and linking its data extensions. How should consumers, retailers, and wholesale buyers be defined in Data Designer?
  • Many-to-Many Relationship
  • One-to-One Relationship
  • Population
  • One-to-Many Relationship
Answer: C

The short version

Consumers, retailers and wholesale buyers are distinct subgroups of contacts, so they belong in Data Designer as Populations, answer C.

Key concepts in this question

Data Designer separates two ideas: attribute groups, which link data extensions back to the contact through Contact Key with a cardinality such as one-to-one, one-to-many or many-to-many, and populations, which declare that a set of contacts is special because its members share a theme and often different identifiers. Populations live in their own data extensions and tell the platform that groups like customers versus employees, or staff versus patients versus vendors, must be handled separately.

Why C is correct

NTO must market differently to individual consumers, retailers and wholesale buyers, and each group plausibly carries different basic contact information and keys. That is precisely the populations use case: categorize distinct subgroups of contacts, then segment from there. Salesforce guidance gives the matching pattern of an office creating separate populations for staff, patients and vendors, which maps directly onto NTO defining one population per buyer type before linking Store, Order and Product data around them.

Why the others are wrong

Options A, B and D are relationship cardinalities, not contact groupings: many-to-many, one-to-one and one-to-many describe how many rows on one side of a link may match rows on the other side inside an attribute group. None of them declares a subgroup of contacts. Choosing a cardinality answers how tables join, while the question asks how buyer types are defined, so every cardinality option misses the point.

Certified-Marketing-Cloud-Consultant exam tip

Subgroups of WHO get populations, while joins between tables get cardinalities. Whenever a stem names distinct audiences such as customers and employees or buyers and sellers, look for Population before considering any one-to-many or many-to-many relationship answer.

6A financial company wants to use Marketing Cloud to send late payment notices to accounts whose payment due date lapsed the previous week. The company has shared the following: ✑ Payments.csv will arrive on the Enhanced SFTP each Monday at 1 a.m. ✑ Payments.csv will be encrypted. ✑ Payments.csv will contain data from the previous week. ✑ Late payment notices will be sent each Monday at noon. ✑ They need to receive a file containing customers who opened or clicked on the late payment notice email within five days after send. Which automation sequence represents a viable solution?
  • File Transfer > Import File > Filter > Wait > Send Email > Wait > SQL Query > Data Extract > File Transfer
  • Import File > File Transfer > SQL Query > Wait > Send Email > Wait > SQL Query > Data Extract > File Transfer
  • File Transfer > Import File > Filter > Wait > Send Email > SQL Query > Wait > Data Extract > File Transfer
  • File Transfer > File Transfer > Import File > SQL Query > Wait > Send Email > SQL Query > File Transfer
Answer: A

The short version

Banked B imports before decrypting, which fails on an encrypted file, so File Transfer first, then Import, Wait to noon, Send, Wait five days, SQL on opens and clicks, Extract and Transfer, answer A.

Key concepts in this question

Stages: File Transfer moves and decrypts or unzips into the Safehouse, Import File loads the prepared file into a data extension, Filter or Query segments the audience, Wait pauses to send time, Send fires, a second Wait holds five days, SQL reads _Open and _Click, Extract writes the file, and Transfer exports it.

Why A is correct

A begins with File Transfer to decrypt Payments.csv, then Import, then Filter, then Wait to noon, then Send Email, then Wait five days, then SQL Query to pull customers who opened or clicked within five days, then Data Extract and File Transfer to return that file. C queries before the five-day Wait and misses late engagement, B imports before decrypting, and D omits the Extract plus export pairing.

Why the others are wrong

B is wrong because Import File cannot read an encrypted file before File Transfer decrypts it, so the automation fails on step one. C is wrong because it runs SQL Query immediately after Send and only then Waits, which misses late opens and clicks that occur during the five-day window the customer explicitly requires. D is wrong because double File Transfer without Data Extract plus File Transfer at the end does not produce the required open and click extract file, and it skips the Wait sequencing that enforces noon send and five-day capture.

Certified-Marketing-Cloud-Consultant exam tip

When the stem says encrypted, put File Transfer before Import every time, and when it says within N days after send, put Wait N days before the SQL against _Open and _Click, then Extract and Transfer. Eliminate any option that imports first or queries before the wait, then check that the tail is SQL, Extract, Transfer in that order.

7Northern Trail Outfitters (NTO) account will be used for email communications with its clients and employees. They want to send from two different subdomains, so they have delegated e.nto.com as their SAP domain and mail.nto.com as an additional Private Domain. Which statement describes how this will impact the account?
  • Links within emails will be wrapped with the same subdomain used for the From Address within the Sender Profile.
  • Links within emails will be wrapped with e.nto.com, and images within Content Builder will use e.nto.com.
  • Links within emails will be wrapped with mail.nto.com, but images within Content Builder will use e.nto.com.
  • Links within emails will be wrapped with e.nto.com, but images within Content Builder will use mail.nto.com.
Answer: B

The short version

One SAP per business unit owns link and image wrapping, while an extra Private Domain only authenticates the From address, so links and Content Builder images stay on e.nto.com even when sending from mail.nto.com, answer B.

Key concepts in this question

Sender Authentication Package is the branding bundle of Private Domain plus link and image wrapping plus dedicated IP plus Reply Mail Management. Only one SAP branding domain can exist per business unit. A separate Private Domain only authenticates the From address.

Why B is correct

B states that links wrap with e.nto.com and Content Builder images use e.nto.com, which is exactly what happens when e.nto.com is the SAP domain and mail.nto.com is only a sending Private Domain. The SAP domain continues to brand every tracked URL and hosted image, while mail.nto.com merely appears in the From header via the Sender Profile. Any answer claiming the wrap follows the From subdomain misunderstands the single-wrapping-domain limit.

Why the others are wrong

A is wrong because it claims links wrap with the same subdomain used for the From Address, which would require two simultaneous SAP wrapping domains in one business unit, a configuration Salesforce does not support. C is wrong because it splits the wrap between mail.nto.com for links and e.nto.com for images, yet both link and image wrapping come from the same SAP domain and cannot split across domains. D reverses that split and is wrong for the same reason, since no Private Domain send changes image hosting away from the SAP domain.

Certified-Marketing-Cloud-Consultant exam tip

Memorize the split: SAP equals From plus links plus images, separate Private Domain equals From only. Whenever a stem adds a second sending subdomain to a unit that already has SAP, keep links and images on the SAP domain and let the new domain affect only the From address. Choose the option that leaves wrapping unchanged.

8Analyst of Northern Trail Outfitters (NTO) marketing team needs to pull email metrics for an upcoming quarterly company meeting. These metrics need to be reported per email campaign for each of NTO's Business Units: * Number of Sends * Delivery Rate * Overall Bounce Rate * Block Bounce Rate * Open Rate * Click Rate * Complaint Rate * Unsubscribe Rate Which email report should NTO's Marketing Analyst pull from Marketing Cloud to get this information?
  • Campaign Email Tracking Report
  • Account Send Summary Report
  • Email Send Report
  • Email Performance Over Time Report
Answer: B

The short version

B — Account Send Summary aggregates standard email KPIs per job across business units. It is built to show sends, delivery, bounce detail, opens, clicks, complaints and unsubscribes together for quarterly rollups.

Key concepts in this question

  • Account Send Summary Report: standard report summarizing send performance by job and business unit with the full KPI set.
  • Bounce decomposition: overall bounce rate plus block bounce detail, separating hard failures from blocks, holds and technical rejects.
  • Engagement and list-health rates: open rate, click rate, complaint rate and unsubscribe rate that leadership expects beside delivery.
  • Campaign versus account scope: campaign tracking shows one campaign only and omits several aggregate bounce and complaint fields needed here.

Why B is correct

B is correct because the requested list maps to the Account Send Summary grain: sends, delivery rate, overall bounce, block bounce, open, click, complaint and unsubscribe rates per campaign for each business unit. Vendor material confirms B and notes Campaign Email Tracking covers only a specific campaign and lacks overall bounce, block bounce and complaint rate. Email Send and Performance Over Time views do not provide that complete cross-business-unit KPI table in one pull.

Why the others are wrong

  • A. Campaign Email Tracking is scoped to one campaign and omits overall bounce, block bounce and complaint metrics.
  • C. Email Send Report focuses on send-job detail rather than the full account KPI summary across business units.
  • D. Performance Over Time emphasizes date trends rather than the per-campaign KPI matrix required here.

Certified-Marketing-Cloud-Consultant exam tip

When the stem lists eight KPIs including block bounce and complaint rate, choose Account Send Summary.

9A pharmaceutical company is hosting a monthly event and will be sending an invitation to new local contacts. The customer would like to automatically update a data extension to determine who will be attending. ✑ The data extension will hold each contact's response as well as the time stamp of the click. ✑ The contact will receive an email two days after the click event. ✑ Both emails should be sent via Journey Builder. What is the optimal solution to record the click activity prior to sending the second email?
  • Leverage the Decision Split and create a Custom Activity.
  • Use a landing page to record the click and trigger an email.
  • Leverage the Engagement Split and the Update Contact Activity.
  • Use a landing page to record the click in the data extension.
Answer: C

The short version

C — Engagement Split plus Update Contact Activity records the click inside Journey Builder. The split detects the invitation click natively, then the update step stamps the response and time into the data extension so the two-day follow-up can branch correctly.

Key concepts in this question

  • Journey Builder email engagement: native click and open signals evaluated without custom code.
  • Engagement Split: the canvas control routing contacts by prior-message open or click.
  • Update Contact Activity: the journey step that writes attribute values back to contact data or a data extension, ideal for persisting RSVP flags and timestamps.
  • Wait and second send timing: a two-day delay after the click event before the second email, keeping both sends inside one governed journey version.

Why C is correct

C keeps the entire monthly invitation and reminder flow inside Journey Builder, avoiding fragile handoffs to outside pages or custom development. The split detects the click and the update step persists response plus timestamp. That stored timestamp then drives the two-day wait and the second send, satisfying the requirement to record click activity natively prior to follow-up.

Why the others are wrong

  • A. Pairs a Decision Split with a Custom Activity, adding unnecessary code when native engagement detection plus an update step already exists.
  • B. Introduces a landing page as a trigger mechanism, which complicates the flow and does not provide the native split and update pattern requested.
  • D. Uses only a landing page to log the click, bypassing Journey Builder engagement evaluation and the clean two-day second-send orchestration.

Certified-Marketing-Cloud-Consultant exam tip

Click then record then wait inside a journey equals Engagement Split followed by Update Contact.

10Which three statements are correct about Data Designer? (Choose three.)
  • Each attribute group contains one data extension, and each data extension can include up to 50 attributes.
  • Each attribute group can contain multiple lists, and each list can include multiple attributes.
  • Data extensions can be linked to either the contact record or different data extensions, including data extensions from other attribute groups.
  • Each attribute group can contain multiple data extensions, and each data extension can include multiple attributes.
  • Data extensions should be linked directly to the contact record prior to being linked to different data extensions.
Answer: C, D, E

The short version

Lists cannot back attribute groups, so B is false, while one or more data extensions per group plus link to contact first plus link to contact or other extensions makes C, D and E true, answer CDE.

Key concepts in this question

Contact Builder Data Designer organizes contact data into attribute groups made of linked data extensions. Each group draws from one or more extensions with attributes mapping to fields. Best practice anchors the model on the contact record, then links remaining extensions outward.

Why CDE is correct

C is correct because extensions link either to the contact record or to different extensions, which is how purchase and product tables chain together around a master extension. D is correct because each group can contain multiple extensions and each extension carries multiple attributes, directly restating that a group gets data from one or more extensions. E is correct because effective organization starts by linking an extension to the contact record before linking other extensions outward, preventing orphan branches.

Why the others are wrong

A is wrong because it caps each group at one data extension, contradicting the one-or-more rule and the multi-table customer, purchase and catalog pattern. B is wrong because attribute groups use data extensions only, and vendor prose plus Trailhead confirm lists cannot serve as attribute sets, so any answer containing B fails. Any pair built on A or B therefore misstates the model, which is why banked BCE must drop B and add D to reach CDE.

Certified-Marketing-Cloud-Consultant exam tip

For Data Designer choose-N questions, first strike any option mentioning lists, then strike any option limiting a group to one extension, then keep the link-to-contact-first plus multi-extension plus extension-to-extension chain. The phrase link to contact record is the anchor signal, and multiple extensions per group is the second giveaway.

Want the full bank of 100 questions for Certified Marketing Cloud Consultant? See all practice exams.