Portfolio ↗

Quiz

2627 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2627 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture77 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture85 Cost Architecture & FinOps82 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization82 AI-Era Architecture86 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture90 Data Platform Architecture88 Streaming & Real-Time Data93 Data Governance & Semantics81 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk88
Difficulty Any beginner intermediate advanced

8 questions in Architecture Communication.

  1. Architecture Diagrams beginner

    A reviewer looks at your architecture diagram and asks whether an arrow is a network call or a data flow, and whether it is synchronous. Why do most diagrams fail this question, and what must every box and line carry?

    2 min answer diagramsnotationreviewambiguity
  2. Architecture Communication beginner

    You have designed a system. Explain the same architecture to a CEO, an engineering manager and an engineer. What changes?

    2 min answer communicationstakeholdersinfluence
  3. Context Diagrams beginner

    A 40-engineer SaaS product has a context diagram with six external systems on it. Roughly how many outbound dependencies does a product that size actually have, how would you count them without guessing, and what does the real number change?

    3 min answer context diagramdependenciesinventoryvendors
  4. Context Diagrams beginner Multiple choice

    A team draws their payment provider inside the system boundary on their context diagram because the provider's SDK runs inside their own service. During the first incident the on-call engineer spends 20 minutes trying to restart something the team does not own. What does the boundary line on a context diagram actually mean?

    3 min answer context-diagramsystem-boundarydependenciesincident-response
  5. Context Diagrams beginner

    Why is the system context diagram usually the most valuable single diagram, and what is most often left off it?

    2 min answer context-diagramscopedependenciestwilio
  6. Facilitation beginner

    Two teams meet for 60 minutes to agree who will own a shared notification capability. Everyone is prepared and the discussion is civil, and the meeting ends with "let us take this offline". Why does naming the decision-maker before the session change the outcome mechanically rather than politically?

    2 min answer facilitationdecision-rightsconsensusmeetings
  7. Presentation Skills beginner Multiple choice

    Four minutes into a twenty-minute architecture slot a stakeholder asks a question that belongs on slide 14 and the discussion runs for eight minutes. You now have eight minutes and fourteen slides. What do you do?

    3 min answer presentationtime managementdecisionaudience
  8. Presentation Skills beginner

    You have to present the same architecture to the board on Tuesday and to the engineering teams on Wednesday. How do the two differ?

    1 min answer communicationdiagramsaudience