10 free sample questions from a bank of 100, with the correct answers and explanations. No signup required — start practising right now.
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.
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.
If the file is encrypted, look for File Transfer first, then pick a start time after the latest data refresh in the story.
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.
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.
When you see Send Flow plus Salesforce Report, look for Salesforce Data Extension plus ID field plus custom folder.
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.
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.
Custom object plus segment plus personalize equals Synchronized Data Extensions with a lookup to contact or lead.
The marketer needs email content rights plus reporting and subscriber management, so the least-privilege fit is Content Creator plus Data Manager, answer BC.
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.
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.
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.
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.
Consumers, retailers and wholesale buyers are distinct subgroups of contacts, so they belong in Data Designer as Populations, answer C.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
When the stem lists eight KPIs including block bounce and complaint rate, choose Account Send Summary.
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.
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.
Click then record then wait inside a journey equals Engagement Split followed by Update Contact.
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.
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.
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.
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.
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.