Checklist progress
0/193Learned
Marketing Cloud Engagement Administrator
Study Checklist
Checklist progress
0/193Learned
Given a scenario, describe the configuration of Mobile Studio.
0/11
Given a scenario, describe the configuration of Email Studio.
0/12
Given a scenario, describe the configuration of Advertising Studio.
0/4
Explain the concepts and typical use cases of Journey Builder.
0/26
What is Journey Builder and how does it differ from Automation Studio for marketing use cases?
Learn this conceptWhat is the difference between a single-send journey and a multi-step journey in Journey Builder?
Learn this conceptWhat entry sources are available in Journey Builder?
Learn this conceptWhen should each Journey Builder entry source be used?
Learn this conceptWhat Journey Builder exit criteria options are available?
Learn this conceptHow does Goal configuration in Journey Builder affect contact exit from a journey?
Learn this conceptHow does configuring an exit condition differ from configuring a goal in Journey Builder?
Learn this conceptWhat are the three re-entry modes available in Journey Builder?
Learn this conceptWhat is the purpose of a Wait activity in Journey Builder?
Learn this conceptWhat wait types are available for the Wait activity in Journey Builder?
Learn this conceptHow does a Decision Split activity work in Journey Builder?
Learn this conceptWhat criteria can a Decision Split activity evaluate in Journey Builder?
Learn this conceptWhat is the purpose of the Engagement Split in Journey Builder?
Learn this conceptWhat is the Update Contact activity in Journey Builder and what data can it modify?
Learn this conceptWhat is the Salesforce activity in Journey Builder and what CRM actions can it trigger?
Learn this conceptWhat is the Einstein STO activity in Journey Builder and how does it optimize delivery timing?
Learn this conceptPrepare for the Exam
Study Community
Ask questions and get the latest info from other Marketing Cloud Engagement Administrator studiers. 593 members and growing.
Re-entry mode is a journey-level setting that controls whether a contact can enter a journey more than once. It determines if contacts can participate in the journey concurrently or consecutively based on their entry status. This configuration prevents over-communication by matching entry rules to specific campaign goals.