Practice English vocabulary for facilitating Event Storming workshops: domain events, commands, aggregates, bounded contexts, and hot spots.
0 / 22 completed
1 / 22
What is the purpose of 'the Event Storming workshop maps the domain'?
Event Storming is a collaborative modeling workshop invented by Alberto Brandolini. Participants use colored sticky notes to map out domain events, commands, and actors across the full business process on a large wall or virtual board.
2 / 22
In Event Storming, what does 'the sticky note represents a domain event'?
In Event Storming notation, orange sticky notes represent domain events — meaningful things that happened, expressed in past tense. They are the backbone of the model and drive the discovery of the full business process.
3 / 22
What does 'the command triggers the event' mean in Event Storming?
In Event Storming, commands (blue stickies) represent decisions or actions — typically expressed in imperative form. Commands cause aggregates to process them, resulting in domain events being emitted.
4 / 22
A facilitator says 'we identified 3 aggregates in the payment bounded context'. What does this mean?
Aggregates (yellow stickies) are consistency boundaries identified during Event Storming — they group related commands and events. Finding 3 aggregates means the team discovered 3 distinct domain objects that enforce business rules.
5 / 22
What is 'the hot spot' in Event Storming notation?
Hot spots (often pink stickies) are used by facilitators to flag areas where participants have questions, disagreements, or uncertainty. They are parking-lot markers to revisit rather than blockers that slow the workshop down.
6 / 22
Sarah: 'Okay team, let's focus on the *business* events. We need to capture everything that *happens* within this order processing API – from the initial product selection to fulfillment and payment confirmation. I want each sticky note to clearly state the event name and a brief description of what caused it.'
Which phrase best captures Sarah's intention regarding the vocabulary used during the Event Storming session?
Sarah is prioritizing the *business* events, which is core to Event Storming. The goal isn't simply to list API calls, but to understand the flow of value creation within the order processing system – what actually *happened* from a user's perspective. This distinction between technical and business events is crucial for effective modeling and communication during the workshop.
7 / 22
During an Event Storming session for a new e-commerce API, Mark says, 'Let's use terms like 'Order Placed' and 'Payment Received'. We need to be very specific about the *actions* that lead to each event.' Which of the following best captures Mark's intention regarding the vocabulary being used in this Event Storming session?
Mark is emphasizing clarity and actionable language. The core purpose of Event Storming is to collaboratively understand the system's behavior by mapping out events—specifically, what *triggered* them and what *resulted* from them. Using terms like 'Order Placed' and 'Payment Received' directly addresses this need for triggering/consequence understanding, which is critical for effective communication and subsequent development.
8 / 22
During a code review session, David says to his teammate Emily, 'I'm seeing that you're using the term 'transaction' throughout this API. While technically accurate, it's too abstract for our Event Storming – we need to focus on *observable* events like 'Order Created', 'Payment Authorized', and 'Shipment Confirmed'. Using more granular event names will make the system's behavior much clearer.' Which of the following best describes David's intention regarding terminology in this context?
David is advocating for more concrete and observable language when defining events within the Event Storming process. He's correcting a potential misconception that 'transaction' is an appropriate term—it's too high-level. Using specific event names like 'Order Created' provides greater clarity about what actually *happened* in the system, aligning with the core principles of domain event modeling and making it easier to understand the flow of events.
9 / 22
Sarah: 'Okay team, let's focus on the *business* events. We need to capture everything that *happens* within this order processing API – from the initial product selection to fulfillment and payment confirmation. I want each sticky note to clearly state the event name and a brief description of what caused it.'
Which phrase best captures Sarah's intention regarding the vocabulary used during the Event Storming session?
Sarah is prioritizing the *business* events, which is core to Event Storming. The goal isn't simply to list API calls, but to understand the flow of value creation within the order processing system – what actually *happened* from a user's perspective. This distinction between technical and business events is crucial for effective modeling and communication during the workshop.
10 / 22
During an Event Storming session for a new e-commerce API, Mark says, 'Let's use terms like 'Order Placed' and 'Payment Received'. We need to be very specific about the *actions* that lead to each event.' Which of the following best captures Mark's intention regarding the vocabulary being used in this Event Storming session?
Mark is emphasizing clarity and actionable language. The core purpose of Event Storming is to collaboratively understand the system's behavior by mapping out events—specifically, what *triggered* them and what *resulted* from them. Using terms like 'Order Placed' and 'Payment Received' directly addresses this need for triggering/consequence understanding, which is critical for effective communication and subsequent development.
11 / 22
During a code review session, David says to his teammate Emily, 'I'm seeing that you're using the term 'transaction' throughout this API. While technically accurate, it's too abstract for our Event Storming – we need to focus on *observable* events like 'Order Created', 'Payment Authorized', and 'Shipment Confirmed'. Using more granular event names will make the system's behavior much clearer.' Which of the following best describes David's intention regarding terminology in this context?
David is advocating for more concrete and observable language when defining events within the Event Storming process. He's correcting a potential misconception that 'transaction' is an appropriate term—it's too high-level. Using specific event names like 'Order Created' provides greater clarity about what actually *happened* in the system, aligning with the core principles of domain event modeling and making it easier to understand the flow of events.
12 / 22
Sarah: 'Okay team, let's focus on the *business* events. We need to capture everything that *happens* within this order processing API – from the initial product selection to fulfillment and payment confirmation. I want each sticky note to clearly state the event name and a brief description of what caused it.'
Which phrase best captures Sarah's intention regarding the vocabulary used during the Event Storming session?
Sarah is prioritizing the *business* events, which is core to Event Storming. The goal isn't simply to list API calls, but to understand the flow of value creation within the order processing system – what actually *happened* from a user's perspective. This distinction between technical and business events is crucial for effective modeling and communication during the workshop.
13 / 22
During an Event Storming session for a new e-commerce API, Mark says, 'Let's use terms like 'Order Placed' and 'Payment Received'. We need to be very specific about the *actions* that lead to each event.' Which of the following best captures Mark's intention regarding the vocabulary being used in this Event Storming session?
Mark is emphasizing clarity and actionable language. The core purpose of Event Storming is to collaboratively understand the system's behavior by mapping out events—specifically, what *triggered* them and what *resulted* from them. Using terms like 'Order Placed' and 'Payment Received' directly addresses this need for triggering/consequence understanding, which is critical for effective communication and subsequent development.
14 / 22
During a code review session, David says to his teammate Emily, 'I'm seeing that you're using the term 'transaction' throughout this API. While technically accurate, it's too abstract for our Event Storming – we need to focus on *observable* events like 'Order Created', 'Payment Authorized', and 'Shipment Confirmed'. Using more granular event names will make the system's behavior much clearer.' Which of the following best describes David's intention regarding terminology in this context?
David is advocating for more concrete and observable language when defining events within the Event Storming process. He's correcting a potential misconception that 'transaction' is an appropriate term—it's too high-level. Using specific event names like 'Order Created' provides greater clarity about what actually *happened* in the system, aligning with the core principles of domain event modeling and making it easier to understand the flow of events.
15 / 22
Sarah: 'Okay team, let's focus on the *business* events. We need to capture everything that *happens* within this order processing API – from the initial product selection to fulfillment and payment confirmation. I want each sticky note to clearly state the event name and a brief description of what caused it.'
Which phrase best captures Sarah's intention regarding the vocabulary used during the Event Storming session?
Sarah is prioritizing the *business* events, which is core to Event Storming. The goal isn't simply to list API calls, but to understand the flow of value creation within the order processing system – what actually *happened* from a user's perspective. This distinction between technical and business events is crucial for effective modeling and communication during the workshop.
16 / 22
During an Event Storming session for a new e-commerce API, Mark says, 'Let's use terms like 'Order Placed' and 'Payment Received'. We need to be very specific about the *actions* that lead to each event.' Which of the following best captures Mark's intention regarding the vocabulary being used in this Event Storming session?
Mark is emphasizing clarity and actionable language. The core purpose of Event Storming is to collaboratively understand the system's behavior by mapping out events—specifically, what *triggered* them and what *resulted* from them. Using terms like 'Order Placed' and 'Payment Received' directly addresses this need for triggering/consequence understanding, which is critical for effective communication and subsequent development.
17 / 22
During a code review session, David says to his teammate Emily, 'I'm seeing that you're using the term 'transaction' throughout this API. While technically accurate, it's too abstract for our Event Storming – we need to focus on *observable* events like 'Order Created', 'Payment Authorized', and 'Shipment Confirmed'. Using more granular event names will make the system's behavior much clearer.' Which of the following best describes David's intention regarding terminology in this context?
David is advocating for more concrete and observable language when defining events within the Event Storming process. He's correcting a potential misconception that 'transaction' is an appropriate term—it's too high-level. Using specific event names like 'Order Created' provides greater clarity about what actually *happened* in the system, aligning with the core principles of domain event modeling and making it easier to understand the flow of events.
18 / 22
During a Slack discussion about modeling the user registration flow, Liam says, 'Let's represent each step – like 'User Enters Email' and 'Password Set' – as a distinct event. We should avoid using terms like 'transaction,' which are too low-level for our Event Storming scope.' Which of the following best explains Liam's statement?
Liam correctly identifies that 'transaction' is too technical. He's emphasizing the importance of focusing on observable *business* events – changes in state that directly affect users or business processes. Using 'transaction' obscures this value flow and isn't relevant to the Event Storming goal.
19 / 22
In a PR description for a new API endpoint related to order updates, Alex writes: 'The system handles a 'PaymentProcessed' event, triggering the next stage in the fulfillment workflow.' What does Alex *primarily* mean when referring to this 'event'?
Alex is using 'event' to describe a *business* change – the order state now reflects successful payment. The term emphasizes that something has fundamentally shifted due to the payment processing, not just a technical operation or data structure. Using 'event' focuses on what matters to the business.
20 / 22
During an Event Storming session for a new mobile app feature, Sarah says, 'We need to identify the *root cause* events – those that directly led to the problem.' What is Sarah referring to when she uses the phrase 'root cause' in this context?
In Event Storming, 'root cause' refers to the *most recent* event in a chain of actions. It's the immediate trigger that directly led to the problem being investigated. This helps focus on understanding the immediate context and preventing similar issues.
21 / 22
David is facilitating an Event Storming session for a new e-commerce platform. He asks: 'Let's consider how we might represent the 'Order Shipped' event.' Which of the following options best describes the *essential* information to capture when defining this event?
When defining a business event like 'Order Shipped,' David is focusing on observable outcomes – what *happened* to the order. The timestamp and carrier information are crucial for tracking and understanding the delivery process. Technical details of API calls are irrelevant to the business meaning.
22 / 22
In a standup update, Maria says: 'We've triggered the 'User Profile Updated' event after the user changed their address.' What is Maria primarily communicating regarding the 'User Profile Updated' event?
Maria is describing an *action* – the user changing their address – that *caused* the 'User Profile Updated' event. Events represent changes in state driven by actions, and this phrasing clarifies the relationship between the two.
What does the "Event Storming Facilitation Vocabulary" exercise cover?
Practice English vocabulary for facilitating Event Storming workshops: domain events, commands, aggregates, bounded contexts, and hot spots.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Event Storming Facilitation Vocabulary"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Event-Driven Architecture Language exercises?
Browse the full Event-Driven Architecture Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.