Salesforce Marketing Cloud Consultant Study Guide (Winter '26): Complete Exam Prep

Discovery and Architecture (28%)

This is the most consultant-oriented section — it tests your ability to gather requirements and make architectural decisions. Key areas: Account architecture: when to use a single business unit vs multiple business units (BUs) — multiple BUs isolate subscriber data, permissions, and sending domains per brand or region. Sender authentication: Private domain (SAP) vs Shared IP — private domain needed for high-volume, brand-sensitive senders; shared IP is fine for low-volume senders. Scalability design: understand how to design for millions of subscribers (data extension strategy, contact model planning, data retention). Estimate scope and effort for an MC implementation — the exam tests whether you can identify what is in scope, what is custom, and what is out-of-the-box.

Integration (24%)

Marketing Cloud Connect: the native Salesforce CRM integration. Setup requires a Connected App in Salesforce, the MC Connect permission set, and an API user. Objects that sync: Leads, Contacts, Users, and Campaigns. Synchronized Data Extensions (SDEs): pre-built data extensions that receive CRM data via MC Connect — they update on the MC Connect sync schedule. SDEs are used in Automation Studio and Journey Builder entry sources to target CRM-based audiences without manual imports. API integration: REST API for new integrations (JSON, OAuth 2.0 authentication), SOAP API for legacy systems (XML, user credentials authentication). Know the REST endpoints for subscriber management, data extension operations, and triggered sends.

Data Management (20%)

Data architecture decisions drive everything else in a Marketing Cloud implementation. Data extensions vs lists: lists are legacy and simpler; data extensions support multi-field subscriber attributes, SQL queries, and complex data models — the answer is almost always data extensions for any new implementation. Contact Builder: the data model layer — Contact objects, attribute groups, and population configuration. Know how to set up the Contact model so that data extensions link to the right Contact. Data retention: set retention periods per data extension (on send, fixed date, after X days). Subscriber management at scale: subscriber key strategy — using CRM Contact ID as the subscriber key enables seamless MC Connect data joining.

Account Management (16%)

Business units: child accounts within an MC organisation that have their own subscriber lists, permissions, and sending. Parent business unit admins can access child BUs; child BU users cannot access other BUs by default. Sender profiles: store the From name, From email, and Reply-To email used for sends. Send classifications: commercial (must honour unsubscribes) vs transactional (bypass unsubscribes — for legally required communications). Reply mail management (RMM): how Marketing Cloud handles replies to sends — unsubscribe replies, auto-replies, and manually managed replies. User roles: know the hierarchy — Account Administrator, Marketing Cloud Administrator, Marketing Cloud Viewer — and what each can do.

Messaging and Journeys (12%)

Journey Builder: event-driven, individual-level marketing automation. Entry sources: data extension entry (batch), API event entry (real-time trigger from external system), Salesforce entry (CRM object trigger), audience entry (Ad Studio). Journey canvases: Splits (engagement, decision, random), Waits, Messages (email, SMS, push), Updates (update data extension or Salesforce record). Goal definition: set a goal condition to measure journey effectiveness and optionally exit contacts who have achieved the goal. Know the difference between “goal exit” (contact leaves journey when goal achieved) and “evaluate goal at re-entry”.