Sequence Diagram Vocabulary
Practice sequence diagram vocabulary: actors, lifelines, synchronous and asynchronous calls, return messages, and combined fragments like alt, loop, and opt.
0 / 26 completed
1 / 26
In a sequence diagram, what is a 'lifeline'?
A lifeline is the vertical dashed line that extends downward from each participant (actor or system) in a sequence diagram. It represents the participant's existence during the interaction. Activation boxes on the lifeline show when it's actively processing.
2 / 26
What is the difference between a synchronous and asynchronous call in a sequence diagram?
Synchronous calls use a solid filled arrowhead — the caller waits for a response. Asynchronous calls use an open (stick) arrowhead — the caller sends the message and immediately continues without waiting for a response.
3 / 26
What does the 'alt' combined fragment represent in a sequence diagram?
The 'alt' (alternative) combined fragment represents conditional branching. It's the UML equivalent of if/else — you divide the fragment into guards (conditions), and only the path whose guard is true executes. Example: [user authenticated] vs. [user not authenticated].
4 / 26
When would you use a 'loop' combined fragment in a sequence diagram?
The 'loop' fragment shows repetition — the contained interaction repeats while its guard condition is true, or for a specified number of iterations. Example: 'loop [for each order item] — call inventory check service.'
5 / 26
What does a 'return message' look like in a sequence diagram and what does it represent?
A return message is shown as a dashed arrow pointing back to the caller. It represents the response from a synchronous call — e.g., 'HTTP 200 OK with order data.' Return messages are optional but help make the flow explicit.
6 / 26
Sarah: 'Okay team, I've implemented the new user authentication flow. The API endpoint now returns a JSON payload with the access token and user details. I've documented it in the PR description using sequence diagrams to illustrate the interaction between the client and our backend service.'
Which of the following best describes what Sarah is illustrating within her PR description?
Sarah is using a sequence diagram to visualize the interaction. The diagram shows the order of messages – requests and responses – between the client (e.g., a web browser) and the server during user login. Options A and D are incorrect because they describe database details or security considerations, not the *flow* of the communication itself. Option B is also partially correct but misses the core purpose: sequence diagrams focus on *how* data moves, not just what parameters are involved.7 / 26
David: 'I've reviewed the PR and noticed a few areas for improvement. Specifically, the sequence diagram shows that the database query is executed synchronously within the service layer. This could lead to blocking and negatively impact performance if the database becomes overloaded. Consider using an asynchronous call to avoid this bottleneck.'David's comment isn't about *what* the sequence diagram shows in general; he's pinpointing a specific technical concern. The correct answer identifies that the diagram illustrates a potential performance issue (synchronous communication causing blocking) and suggests an alternative design choice – namely asynchronous communication. It's crucial to understand that sequence diagrams are used for analysis, not just documentation of the initial state. Options A and C misinterpret the purpose of the diagram, while option D is entirely irrelevant.
8 / 26
Mark is focusing on the potential for a bottleneck caused by the synchronous call. He's correctly identifying that the PaymentService will be blocked while waiting for the TransactionService to complete its task. This is a common misconception – sequence diagrams aren't about *design*, but about illustrating communication flow, and in this case, the diagram shows a vulnerable design pattern. The correct answer highlights the performance concern directly related to synchronous blocking.
9 / 26
PR Description:
During a code review of a pull request for a new microservice handling user profile updates, Liam presents the following sequence diagram. The diagram depicts a User interface sending a request to the ProfileService, which then synchronously calls the DataStoreService to retrieve and update the user's profile information before returning an acknowledgement response. After reviewing the diagram, Chloe asks: 'Can you explain what this diagram is illustrating in terms of the flow of data?'This question assesses understanding of synchronous communication and its implications. The correct answer (option 2) focuses on the key issue: the ProfileService is blocked while waiting for the DataStoreService to respond synchronously. This creates a potential bottleneck and can negatively impact performance if the DataStoreService becomes overloaded. Options A, C, and D misinterpret the diagram's purpose or suggest alternative approaches that don't directly address the synchronous blocking problem.
10 / 26
Sarah: 'Okay team, I've implemented the new user authentication flow. The API endpoint now returns a JSON payload with the access token and user details. I've documented it in the PR description using sequence diagrams to illustrate the interaction between the client and our backend service.'
Which of the following best describes what Sarah is illustrating within her PR description?
Sarah is using a sequence diagram to visualize the interaction. The diagram shows the order of messages – requests and responses – between the client (e.g., a web browser) and the server during user login. Options A and D are incorrect because they describe database details or security considerations, not the *flow* of the communication itself. Option B is also partially correct but misses the core purpose: sequence diagrams focus on *how* data moves, not just what parameters are involved.11 / 26
David: 'I've reviewed the PR and noticed a few areas for improvement. Specifically, the sequence diagram shows that the database query is executed synchronously within the service layer. This could lead to blocking and negatively impact performance if the database becomes overloaded. Consider using an asynchronous call to avoid this bottleneck.'David's comment isn't about *what* the sequence diagram shows in general; he's pinpointing a specific technical concern. The correct answer identifies that the diagram illustrates a potential performance issue (synchronous communication causing blocking) and suggests an alternative design choice – namely asynchronous communication. It's crucial to understand that sequence diagrams are used for analysis, not just documentation of the initial state. Options A and C misinterpret the purpose of the diagram, while option D is entirely irrelevant.
12 / 26
Mark is focusing on the potential for a bottleneck caused by the synchronous call. He's correctly identifying that the PaymentService will be blocked while waiting for the TransactionService to complete its task. This is a common misconception – sequence diagrams aren't about *design*, but about illustrating communication flow, and in this case, the diagram shows a vulnerable design pattern. The correct answer highlights the performance concern directly related to synchronous blocking.
13 / 26
PR Description:
During a code review of a pull request for a new microservice handling user profile updates, Liam presents the following sequence diagram. The diagram depicts a User interface sending a request to the ProfileService, which then synchronously calls the DataStoreService to retrieve and update the user's profile information before returning an acknowledgement response. After reviewing the diagram, Chloe asks: 'Can you explain what this diagram is illustrating in terms of the flow of data?'This question assesses understanding of synchronous communication and its implications. The correct answer (option 2) focuses on the key issue: the ProfileService is blocked while waiting for the DataStoreService to respond synchronously. This creates a potential bottleneck and can negatively impact performance if the DataStoreService becomes overloaded. Options A, C, and D misinterpret the diagram's purpose or suggest alternative approaches that don't directly address the synchronous blocking problem.
14 / 26
Sarah: 'Okay team, I've implemented the new user authentication flow. The API endpoint now returns a JSON payload with the access token and user details. I've documented it in the PR description using sequence diagrams to illustrate the interaction between the client and our backend service.'
Which of the following best describes what Sarah is illustrating within her PR description?
Sarah is using a sequence diagram to visualize the interaction. The diagram shows the order of messages – requests and responses – between the client (e.g., a web browser) and the server during user login. Options A and D are incorrect because they describe database details or security considerations, not the *flow* of the communication itself. Option B is also partially correct but misses the core purpose: sequence diagrams focus on *how* data moves, not just what parameters are involved.15 / 26
David: 'I've reviewed the PR and noticed a few areas for improvement. Specifically, the sequence diagram shows that the database query is executed synchronously within the service layer. This could lead to blocking and negatively impact performance if the database becomes overloaded. Consider using an asynchronous call to avoid this bottleneck.'David's comment isn't about *what* the sequence diagram shows in general; he's pinpointing a specific technical concern. The correct answer identifies that the diagram illustrates a potential performance issue (synchronous communication causing blocking) and suggests an alternative design choice – namely asynchronous communication. It's crucial to understand that sequence diagrams are used for analysis, not just documentation of the initial state. Options A and C misinterpret the purpose of the diagram, while option D is entirely irrelevant.
16 / 26
Mark is focusing on the potential for a bottleneck caused by the synchronous call. He's correctly identifying that the PaymentService will be blocked while waiting for the TransactionService to complete its task. This is a common misconception – sequence diagrams aren't about *design*, but about illustrating communication flow, and in this case, the diagram shows a vulnerable design pattern. The correct answer highlights the performance concern directly related to synchronous blocking.
17 / 26
PR Description:
During a code review of a pull request for a new microservice handling user profile updates, Liam presents the following sequence diagram. The diagram depicts a User interface sending a request to the ProfileService, which then synchronously calls the DataStoreService to retrieve and update the user's profile information before returning an acknowledgement response. After reviewing the diagram, Chloe asks: 'Can you explain what this diagram is illustrating in terms of the flow of data?'This question assesses understanding of synchronous communication and its implications. The correct answer (option 2) focuses on the key issue: the ProfileService is blocked while waiting for the DataStoreService to respond synchronously. This creates a potential bottleneck and can negatively impact performance if the DataStoreService becomes overloaded. Options A, C, and D misinterpret the diagram's purpose or suggest alternative approaches that don't directly address the synchronous blocking problem.
18 / 26
Sarah: 'Okay team, I've implemented the new user authentication flow. The API endpoint now returns a JSON payload with the access token and user details. I've documented it in the PR description using sequence diagrams to illustrate the interaction between the client and our backend service.'
Which of the following best describes what Sarah is illustrating within her PR description?
Sarah is using a sequence diagram to visualize the interaction. The diagram shows the order of messages – requests and responses – between the client (e.g., a web browser) and the server during user login. Options A and D are incorrect because they describe database details or security considerations, not the *flow* of the communication itself. Option B is also partially correct but misses the core purpose: sequence diagrams focus on *how* data moves, not just what parameters are involved.19 / 26
David: 'I've reviewed the PR and noticed a few areas for improvement. Specifically, the sequence diagram shows that the database query is executed synchronously within the service layer. This could lead to blocking and negatively impact performance if the database becomes overloaded. Consider using an asynchronous call to avoid this bottleneck.'David's comment isn't about *what* the sequence diagram shows in general; he's pinpointing a specific technical concern. The correct answer identifies that the diagram illustrates a potential performance issue (synchronous communication causing blocking) and suggests an alternative design choice – namely asynchronous communication. It's crucial to understand that sequence diagrams are used for analysis, not just documentation of the initial state. Options A and C misinterpret the purpose of the diagram, while option D is entirely irrelevant.
20 / 26
Mark is focusing on the potential for a bottleneck caused by the synchronous call. He's correctly identifying that the PaymentService will be blocked while waiting for the TransactionService to complete its task. This is a common misconception – sequence diagrams aren't about *design*, but about illustrating communication flow, and in this case, the diagram shows a vulnerable design pattern. The correct answer highlights the performance concern directly related to synchronous blocking.
21 / 26
PR Description:
During a code review of a pull request for a new microservice handling user profile updates, Liam presents the following sequence diagram. The diagram depicts a User interface sending a request to the ProfileService, which then synchronously calls the DataStoreService to retrieve and update the user's profile information before returning an acknowledgement response. After reviewing the diagram, Chloe asks: 'Can you explain what this diagram is illustrating in terms of the flow of data?'This question assesses understanding of synchronous communication and its implications. The correct answer (option 2) focuses on the key issue: the ProfileService is blocked while waiting for the DataStoreService to respond synchronously. This creates a potential bottleneck and can negatively impact performance if the DataStoreService becomes overloaded. Options A, C, and D misinterpret the diagram's purpose or suggest alternative approaches that don't directly address the synchronous blocking problem.
22 / 26
During a Slack discussion about the new user onboarding sequence, Emily says: 'I've added an interaction showing the User Service sending a request to the Profile Service for user details. The diagram clearly shows this is a synchronous call – it's important for immediate data retrieval.' Which of the following best describes Emily's concern regarding this interaction?
Emily is highlighting a potential bottleneck. Synchronous calls block the sender while waiting for the receiver, which can significantly impact performance if the Profile Service is slow to respond. This contrasts with asynchronous approaches that allow the User Service to continue processing other tasks.
23 / 26
Reviewing a PR for a new API endpoint, David comments: 'The sequence diagram depicts a request from the Client to the Gateway, followed by a direct synchronous call from the Gateway to the Business Logic. This seems inefficient – shouldn't we be using an intermediary layer to handle potential failures and retry logic?' What is David primarily questioning regarding this sequence diagram?
David correctly identifies a potential issue with the synchronous call. Direct synchronous calls can lead to blocking and prevent the Gateway from handling errors or retrying failed operations. Introducing an intermediary layer would allow for more robust error handling and improved resilience.
24 / 26
Liam is describing a sequence diagram in a PR description for a new microservice that manages user preferences. He states: 'The diagram shows the User Interface sending a request to the Preference Service which immediately updates the database.' What terminology best describes Liam's statement regarding the flow?
Liam's description highlights an 'immediate execution', which is a key characteristic of an idempotent operation. An idempotent operation can be executed multiple times without changing the state beyond the initial application. This contrasts with asynchronous messaging, which involves delayed communication.
25 / 26
During a standup meeting, Sarah explains her work on a new feature: 'I've added a sequence diagram to the PR showing the flow from the User Interface through the Authentication Service and then directly to the Data Access Layer. The diagram clearly demonstrates this synchronous interaction.' What potential issue is Sarah implicitly raising with this sequence diagram?
Sarah's emphasis on 'synchronous interaction' raises a critical concern. A direct synchronous call from the UI to the Data Access Layer can cause blocking if the Data Access Layer is slow or unavailable, leading to a poor user experience and potential performance bottlenecks.
26 / 26
Mark comments on a sequence diagram in a code review: 'I'm seeing that the diagram shows the Order Service directly invoking the PaymentService synchronously. This looks like it could lead to problems if the PaymentService is temporarily unavailable.' What is Mark's primary concern regarding this synchronous interaction?
Mark is correctly identifying a risk associated with synchronous calls. If the PaymentService becomes unavailable, the Order Service will block indefinitely, leading to an unresponsive system. This highlights the importance of implementing fault tolerance and handling potential service outages.
Frequently Asked Questions
What will I practice in "Sequence Diagram Vocabulary"?
This is an Architecture Diagrams exercise set. It walks through 26 scenario-based multiple-choice questions built around real usage of Architecture Diagrams terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 26 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Architecture Diagrams vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Architecture Diagrams exercises?
See the Architecture Diagrams exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Architecture Diagrams vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.