Practice C4 model diagram vocabulary: Context (L1), Container (L2), Component (L3), and Code (L4) diagrams, zoom in/out language, and describing system boundaries.
0 / 5 completed
1 / 5
In the C4 model, what does a Level 1 (Context) diagram show?
A C4 Level 1 (Context) diagram is the highest-level view — it shows your system as a single box, surrounded by the people and other systems that interact with it. It answers: 'What does this system do and who uses it?'
2 / 5
A C4 Level 2 (Container) diagram shows which level of detail?
A C4 Container diagram zooms into the system to show the major technical containers: web frontend, backend API, database, message broker, etc. 'Container' here means a deployable/runnable unit — not necessarily Docker.
3 / 5
When would you use a C4 Level 3 (Component) diagram?
A C4 Component diagram zooms into a specific container (e.g., the backend API) to show its internal components — controllers, services, repositories — and how they interact. Use it when you need to explain a container's internal architecture.
4 / 5
What does 'zoom in / zoom out' mean when presenting C4 diagrams?
'Zoom in / zoom out' is the C4 model's key navigation metaphor. You start at Context (big picture), zoom in to Containers (technical architecture), then Components (internal design). This lets you explain a system at any audience's level of detail.
5 / 5
How would you describe a 'boundary' in a C4 Context diagram?
In C4, a boundary (shown as a dashed box) separates your system from external actors. When presenting, you might say: 'Inside this boundary is our payment system. Outside, we have the customer's browser, the bank API, and the fraud detection service.'