Channel Management16% of the exam

Journey Builder entry sources, activities and settings

How Journey Builder admits contacts (entry sources, reusable entry events, the data extension snapshot at activation, Contact Data Event deprecation), when a Single Send journey is enough, what the Flow Control activities do, what Journey Settings, default personalization values and goals control, and how Journey Builder permissions and Sales and Service Cloud activities are granted.

Official exam objective
Explain the concepts and typical use cases of Journey Builder.

~8 min read · 12 practice questions ·

What the exam expects

  • Explain why every journey needs an entry source, when to make an entry event reusable, and why an active journey ignores fields added to its entry data extension.
  • Replace a Contact Data Event entry source with the Data Extension entry source.
  • Choose a Single Send journey for a one-off message, and the right Flow Control activity (a wait type, a split type or Join) for timing and branching.
  • Use Journey Settings for contact entry mode and the default email address or mobile number; set default attribute values so personalization is never blank; describe goals.
  • Grant Journey Builder access (General Access, View plus Automation Create, Edit; deny by default) and Sales and Service Cloud activity access.
  • Key terms: entry source (where contacts entering a journey come from); entry event (the action that prompts contacts to enter); Single Send journey (one message to one data source, scheduled or immediate); contact entry mode (when a contact may enter or re-enter); goal (a filter-based target that measures, and can end, a contact's journey).

Key facts

Entry source
Detail
Required in every journey
Entry data extension
Detail
Snapshot at activation; new fields need a new journey version
Contact Data Events
Detail
Not supported in an upcoming release; use the Data Extension entry source
Entry events
Detail
Journey-specific or reusable; in-use events can't be deleted
Single Send
Detail
Choose a message, data source and send time
Splits and Join
Detail
Engagement (open, click, bounce), Decision (Remainder path), Random (up to 10 paths); Join merges paths
Journey Settings
Detail
Gear icon: contact entry mode and default address
Blank personalization
Detail
Define a default value for every attribute
Goals
Detail
Optional; evaluated every 24 hours; not in Single Send
Create, Edit permission
Detail
Works only with General Access, View allowed; unset means Deny
CRM activity access
Detail
Grantable to any role except Marketing Cloud Engagement Administrator
Sources for this section (9)
  • Why doesn't a running journey see a field added to its entry data extension?
  • When is a Single Send journey the right choice?
  • Which setting decides whether a contact can re-enter a journey?
  • Why can a user with Automation Create, Edit still be unable to build journeys?
  • What should replace a Contact Data Event entry source in a new journey?

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 Administrator pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 20 lessons of the Marketing Cloud Engagement Administrator guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Inline practice questions and one-click topic practice (12 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Marketing Cloud Engagement Administrator exam