Administration and Program Setup
What the exam expects
Administration questions test whether you understand the consequences of a setting, not just where the toggle lives. Know the hierarchy: instance-level settings (Admin area) override or constrain workspace/partition-level behavior, and program-level settings apply only within that program's channels and tags. Be fluent in users and roles (role = permission set, user = person, workspace roles layered on top), workspaces and partitions (workspaces separate marketing assets; partitions separate people), and channels and tags (channels define program statuses and success; tags enable reporting across programs).
Traps
- Confusing workspace (asset segregation) with lead partition (person segregation). A user with workspace access still needs partition access to see people.
- Assuming deleting a program type or channel is harmless - in-use objects cannot be deleted, only deactivated/renamed.
- Forgetting that communication limits and subscription centers live in Admin and cascade to all programs.
- Mixing up program status (a channel step) with lifecycle stage (a field driven by scoring/lifecycle programs).
Rule of thumb
Before answering any admin question, ask: at what level is this configured, and who is affected? If the answer says "all workspaces," it is almost certainly an Admin-level setting.
Worked example
A client wants EU leads visible only to the EU team. You create a lead partition for EU people and a workspace for EU assets, then assign the EU role with both workspace and partition permissions. Creating only a workspace leaves the people visible to everyone - a classic distractor.