Spatial Vocabulary for Architecture Diagrams
Practice the directional and relational vocabulary for narrating architecture diagrams in English.
0 / 33 completed
1 / 33
A request arrives at the top of the diagram and flows down to the database. How would you describe this?
Top-to-bottom flow is a common pattern in architecture diagrams representing request lifecycle from user to data store.
2 / 33
In a C4 diagram, you are describing the boundary box labeled Payment Service. Which sentence is most precise?
C4 model container descriptions should name the software element, its responsibility, and its external relationships.
3 / 33
Two services are connected by a solid arrow labeled REST/JSON. What does this communicate?
A labeled directed arrow in an architecture diagram shows the communication protocol and direction of the relationship.
4 / 33
A component sits outside the main system boundary box. How would you describe this in a diagram walkthrough?
In C4 and other architecture notations, elements outside the system boundary are external systems or third-party services.
5 / 33
You are narrating a sequence diagram. An actor on the left sends a message to a box on the right. What do you say?
Sequence diagram narration specifies who initiates the interaction, what operation is performed, and what happens next.
6 / 33
PR Description
During code review, Sarah writes the following PR description:
"Fixed a bug where user profiles weren't updating correctly after a successful login. The issue was traced to a missing validation step in the new authentication flow. Added a check for valid profile data before saving."This question tests understanding of describing architectural changes in a PR. The correct answer highlights that Sarah accurately explained her action: she implemented data validation. Options B and C are incorrect because they misrepresent the nature of the work (debugging vs. vague description). Option D is also wrong as it focuses on the database, not the user profile update.
7 / 33
Sarah's PR description highlights a key aspect of the diagram. Which term best describes the flow depicted by her statement about adding a validation step before saving user profile data? Consider how this relates to the architectural representation and potential dependencies shown in diagrams.
The correct answer is 'Input Validation'. Sarah's description clearly focuses on a check performed *before* data is saved – this directly relates to ensuring the integrity of the data flowing through the system. The other options—Data Transformation, Data Routing, and System Integration—refer to broader processes rather than the specific action of verifying user profile data before it's persisted. Misconceptions might include assuming 'System Integration' applies here because authentication is involved; however, validation is a core component of any well-designed system.
8 / 33
PR Description
During code review, Sarah writes the following PR description:
"Fixed a bug where user profiles weren't updating correctly after a successful login. The issue was traced to a missing validation step in the new authentication flow. Added a check for valid profile data before saving."This question tests understanding of describing architectural changes in a PR. The correct answer highlights that Sarah accurately explained her action: she implemented data validation. Options B and C are incorrect because they misrepresent the nature of the work (debugging vs. vague description). Option D is also wrong as it focuses on the database, not the user profile update.
9 / 33
Sarah's PR description highlights a key aspect of the diagram. Which term best describes the flow depicted by her statement about adding a validation step before saving user profile data? Consider how this relates to the architectural representation and potential dependencies shown in diagrams.
The correct answer is 'Input Validation'. Sarah's description clearly focuses on a check performed *before* data is saved – this directly relates to ensuring the integrity of the data flowing through the system. The other options—Data Transformation, Data Routing, and System Integration—refer to broader processes rather than the specific action of verifying user profile data before it's persisted. Misconceptions might include assuming 'System Integration' applies here because authentication is involved; however, validation is a core component of any well-designed system.
10 / 33
PR Description
During code review, Sarah writes the following PR description:
"Fixed a bug where user profiles weren't updating correctly after a successful login. The issue was traced to a missing validation step in the new authentication flow. Added a check for valid profile data before saving."This question tests understanding of describing architectural changes in a PR. The correct answer highlights that Sarah accurately explained her action: she implemented data validation. Options B and C are incorrect because they misrepresent the nature of the work (debugging vs. vague description). Option D is also wrong as it focuses on the database, not the user profile update.
11 / 33
Sarah's PR description highlights a key aspect of the diagram. Which term best describes the flow depicted by her statement about adding a validation step before saving user profile data? Consider how this relates to the architectural representation and potential dependencies shown in diagrams.
The correct answer is 'Input Validation'. Sarah's description clearly focuses on a check performed *before* data is saved – this directly relates to ensuring the integrity of the data flowing through the system. The other options—Data Transformation, Data Routing, and System Integration—refer to broader processes rather than the specific action of verifying user profile data before it's persisted. Misconceptions might include assuming 'System Integration' applies here because authentication is involved; however, validation is a core component of any well-designed system.
12 / 33
PR Description
During code review, Sarah writes the following PR description:
"Fixed a bug where user profiles weren't updating correctly after a successful login. The issue was traced to a missing validation step in the new authentication flow. Added a check for valid profile data before saving."This question tests understanding of describing architectural changes in a PR. The correct answer highlights that Sarah accurately explained her action: she implemented data validation. Options B and C are incorrect because they misrepresent the nature of the work (debugging vs. vague description). Option D is also wrong as it focuses on the database, not the user profile update.
13 / 33
Sarah's PR description highlights a key aspect of the diagram. Which term best describes the flow depicted by her statement about adding a validation step before saving user profile data? Consider how this relates to the architectural representation and potential dependencies shown in diagrams.
The correct answer is 'Input Validation'. Sarah's description clearly focuses on a check performed *before* data is saved – this directly relates to ensuring the integrity of the data flowing through the system. The other options—Data Transformation, Data Routing, and System Integration—refer to broader processes rather than the specific action of verifying user profile data before it's persisted. Misconceptions might include assuming 'System Integration' applies here because authentication is involved; however, validation is a core component of any well-designed system.
14 / 33
David: "The diagram shows a dependency between the `AuthenticationService` and the `UserProfileService`. The arrow indicates that the `AuthenticationService` initiates the process by sending a request to the `UserProfileService` to retrieve user data."David's statement correctly identifies that the arrow represents an initiated process. Importantly, it acknowledges the request-response nature of this dependency. The other options misinterpret the direction and type of interaction shown by the diagram.
15 / 33
Liam writes in a Slack channel: "Regarding the new API endpoint for user profile updates, the diagram shows that data flows *from* the client to the `ProfileManager` component and then to the database. We need to ensure this flow is properly documented."Liam's message accurately describes the flow of data as depicted in the architecture diagram. It correctly identifies the `ProfileManager`'s role and highlights the need for documentation, a common practice in software development. The other options misrepresent the direction or omit crucial components.
16 / 33
PR Description
"Implemented a new feature to handle user role assignments within the system. The diagram illustrates that after a user logs in, their role is retrieved from the `RoleService` and assigned to the relevant data model. This change ensures consistent role application across all services."The PR description accurately describes the flow illustrated in the diagram. It correctly identifies the `RoleService`'s role and how it impacts the data model. This demonstrates a solid understanding of architectural dependencies as shown visually.
17 / 33
Maria updates her daily stand-up: "I've been working on clarifying the flow of data between the `OrderProcessingService` and the `PaymentGatewayService`, as shown in the architecture diagram. Specifically, I've documented that the OrderProcessingService sends a request to the PaymentGatewayService via an HTTP POST endpoint."Maria's stand-up update effectively summarizes the key aspect of the architecture diagram – the data flow between services. It focuses on the core technical detail and aligns with the purpose of a stand-up update: quick communication about ongoing tasks. The other options introduce irrelevant or unnecessary details.
18 / 33
John writes in a code review comment: "The diagram shows that the `NotificationService` *depends on* the `UserService`. This means the NotificationService needs to call the UserService to retrieve user information before sending out notifications."John's comment correctly interprets the dependency represented by the arrow in the diagram. It highlights that the `NotificationService` relies on the `UserService` for user data, a fundamental concept in architectural diagrams and service interactions.
19 / 33
David: "The diagram shows a dependency between the `AuthenticationService` and the `UserProfileService`. The arrow indicates that the `AuthenticationService` initiates the process by sending a request to the `UserProfileService` to retrieve user data."David's statement correctly identifies that the arrow represents an initiated process. Importantly, it acknowledges the request-response nature of this dependency. The other options misinterpret the direction and type of interaction shown by the diagram.
20 / 33
Liam writes in a Slack channel: "Regarding the new API endpoint for user profile updates, the diagram shows that data flows *from* the client to the `ProfileManager` component and then to the database. We need to ensure this flow is properly documented."Liam's message accurately describes the flow of data as depicted in the architecture diagram. It correctly identifies the `ProfileManager`'s role and highlights the need for documentation, a common practice in software development. The other options misrepresent the direction or omit crucial components.
21 / 33
PR Description
"Implemented a new feature to handle user role assignments within the system. The diagram illustrates that after a user logs in, their role is retrieved from the `RoleService` and assigned to the relevant data model. This change ensures consistent role application across all services."The PR description accurately describes the flow illustrated in the diagram. It correctly identifies the `RoleService`'s role and how it impacts the data model. This demonstrates a solid understanding of architectural dependencies as shown visually.
22 / 33
Maria updates her daily stand-up: "I've been working on clarifying the flow of data between the `OrderProcessingService` and the `PaymentGatewayService`, as shown in the architecture diagram. Specifically, I've documented that the OrderProcessingService sends a request to the PaymentGatewayService via an HTTP POST endpoint."Maria's stand-up update effectively summarizes the key aspect of the architecture diagram – the data flow between services. It focuses on the core technical detail and aligns with the purpose of a stand-up update: quick communication about ongoing tasks. The other options introduce irrelevant or unnecessary details.
23 / 33
John writes in a code review comment: "The diagram shows that the `NotificationService` *depends on* the `UserService`. This means the NotificationService needs to call the UserService to retrieve user information before sending out notifications."John's comment correctly interprets the dependency represented by the arrow in the diagram. It highlights that the `NotificationService` relies on the `UserService` for user data, a fundamental concept in architectural diagrams and service interactions.
24 / 33
David: "The diagram shows a dependency between the `AuthenticationService` and the `UserProfileService`. The arrow indicates that the `AuthenticationService` initiates the process by sending a request to the `UserProfileService` to retrieve user data."David's statement correctly identifies that the arrow represents an initiated process. Importantly, it acknowledges the request-response nature of this dependency. The other options misinterpret the direction and type of interaction shown by the diagram.
25 / 33
Liam writes in a Slack channel: "Regarding the new API endpoint for user profile updates, the diagram shows that data flows *from* the client to the `ProfileManager` component and then to the database. We need to ensure this flow is properly documented."Liam's message accurately describes the flow of data as depicted in the architecture diagram. It correctly identifies the `ProfileManager`'s role and highlights the need for documentation, a common practice in software development. The other options misrepresent the direction or omit crucial components.
26 / 33
PR Description
"Implemented a new feature to handle user role assignments within the system. The diagram illustrates that after a user logs in, their role is retrieved from the `RoleService` and assigned to the relevant data model. This change ensures consistent role application across all services."The PR description accurately describes the flow illustrated in the diagram. It correctly identifies the `RoleService`'s role and how it impacts the data model. This demonstrates a solid understanding of architectural dependencies as shown visually.
27 / 33
Maria updates her daily stand-up: "I've been working on clarifying the flow of data between the `OrderProcessingService` and the `PaymentGatewayService`, as shown in the architecture diagram. Specifically, I've documented that the OrderProcessingService sends a request to the PaymentGatewayService via an HTTP POST endpoint."Maria's stand-up update effectively summarizes the key aspect of the architecture diagram – the data flow between services. It focuses on the core technical detail and aligns with the purpose of a stand-up update: quick communication about ongoing tasks. The other options introduce irrelevant or unnecessary details.
28 / 33
John writes in a code review comment: "The diagram shows that the `NotificationService` *depends on* the `UserService`. This means the NotificationService needs to call the UserService to retrieve user information before sending out notifications."John's comment correctly interprets the dependency represented by the arrow in the diagram. It highlights that the `NotificationService` relies on the `UserService` for user data, a fundamental concept in architectural diagrams and service interactions.
29 / 33
David: "The diagram shows a dependency between the `AuthenticationService` and the `UserProfileService`. The arrow indicates that the `AuthenticationService` initiates the process by sending a request to the `UserProfileService` to retrieve user data."David's statement correctly identifies that the arrow represents an initiated process. Importantly, it acknowledges the request-response nature of this dependency. The other options misinterpret the direction and type of interaction shown by the diagram.
30 / 33
Liam writes in a Slack channel: "Regarding the new API endpoint for user profile updates, the diagram shows that data flows *from* the client to the `ProfileManager` component and then to the database. We need to ensure this flow is properly documented."Liam's message accurately describes the flow of data as depicted in the architecture diagram. It correctly identifies the `ProfileManager`'s role and highlights the need for documentation, a common practice in software development. The other options misrepresent the direction or omit crucial components.
31 / 33
PR Description
"Implemented a new feature to handle user role assignments within the system. The diagram illustrates that after a user logs in, their role is retrieved from the `RoleService` and assigned to the relevant data model. This change ensures consistent role application across all services."The PR description accurately describes the flow illustrated in the diagram. It correctly identifies the `RoleService`'s role and how it impacts the data model. This demonstrates a solid understanding of architectural dependencies as shown visually.
32 / 33
Maria updates her daily stand-up: "I've been working on clarifying the flow of data between the `OrderProcessingService` and the `PaymentGatewayService`, as shown in the architecture diagram. Specifically, I've documented that the OrderProcessingService sends a request to the PaymentGatewayService via an HTTP POST endpoint."Maria's stand-up update effectively summarizes the key aspect of the architecture diagram – the data flow between services. It focuses on the core technical detail and aligns with the purpose of a stand-up update: quick communication about ongoing tasks. The other options introduce irrelevant or unnecessary details.
33 / 33
John writes in a code review comment: "The diagram shows that the `NotificationService` *depends on* the `UserService`. This means the NotificationService needs to call the UserService to retrieve user information before sending out notifications."John's comment correctly interprets the dependency represented by the arrow in the diagram. It highlights that the `NotificationService` relies on the `UserService` for user data, a fundamental concept in architectural diagrams and service interactions.
Frequently Asked Questions
What will I practice in "Spatial Vocabulary for Architecture Diagrams"?
This is an Architecture Diagrams exercise set. It walks through 33 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 33 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.