Data Modeling and Management21% of the exam
Data extensions, lists, suppression and Data Designer objects
Which data object fits a requirement: lists or data extensions, Data Designer attribute groups, populations and cardinality, publication, suppression and auto-suppression lists, filtered and random data extensions, and send logs.
Explain the various data objects in Marketing Cloud.
~8 min read · 22 practice questions ·
What the exam expects
- Choose between an Email Studio list and a data extension from export, data type, key, sharing and retention needs.
- Explain Data Designer objects: attribute groups, populations, links and cardinality, ranges and restrictions, and what can't be edited there.
- Pick a publication list, suppression list or auto-suppression list for an opt-out or do-not-contact requirement, and know each one's scope.
- Use filtered and random data extensions correctly, and recognize system data views that don't exist.
- Design a send log for send-time data.
- Decide when a custom preference center replaces the standard Profile and Subscription Centers, and how it records opt-outs.
- Key terms: data extension (table that stores subscriber or relational data); profile attribute (list attribute whose value is global); attribute group (several linked data extensions in Data Designer); population (primary set of contacts linked 1:1 on Contact Key); auto-suppression list (address list applied automatically by level and send classification); send log (data extension that records send-time data).
Key facts
List attribute types
- Detail
- Text, Numeric, Date, Boolean
Profile attribute values
- Detail
- Global across accounts
Lists
- Detail
- No automated export, no sharing, no retention
Root relationships
- Detail
- New ones must be created as populations
System attribute groups
- Detail
- Can't be modified
Data Designer record edits
- Detail
- First 200 records per data extension
_AllContacts
- Detail
- Not available; use a filtered mobile list
Enterprise auto-suppression list
- Detail
- Impacts the whole account
Random data extension
- Detail
- Up to 12 splits, plus Add Remainder
SendLog template
- Detail
- One data extension per account
LogUnsubEvent without a job context
- Detail
- No UnsubEvent; the subscriber is master-unsubscribed
Sources for this section (8)
- List vs. Data Extensionhelp.salesforce.com (opens in a new tab)
- Data Designerhelp.salesforce.com (opens in a new tab)
- Edit Data Extensions in Data Designerhelp.salesforce.com (opens in a new tab)
- AllContacts System Data Viewhelp.salesforce.com (opens in a new tab)
- Auto-Suppression Listshelp.salesforce.com (opens in a new tab)
- Create a Random Data Extensionhelp.salesforce.com (opens in a new tab)
- Send Logginghelp.salesforce.com (opens in a new tab)
- LogUnsubEventdeveloper.salesforce.com (opens in a new tab)
- Which fields does a suppression list contain?
- When does a subscriber land on a suppression list without any import?
- Why clear triggered send queues before enabling auto-suppression?
- How can a single record be added to a data extension outside an import?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Marketing Cloud Engagement Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 20 lessons of the Marketing Cloud Engagement Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (22 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both