Portfolio ↗

Quiz

2667 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 areas2667 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 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

53 questions in Architecture Communication.

  1. Architecture Diagrams intermediate

    A design tool's architecture document contains fourteen diagrams and reviewers still ask basic questions. What makes a diagram earn its place?

    2 min answer diagramsclaritynotationfigma
  2. Architecture Diagrams intermediate Multiple choice

    A team brings one target-state container diagram to the review of a six-month datastore migration. The review approves it. Three months in, rollback is impossible because both the old and the new store hold rows nothing else has. Which artefact should the review have required?

    3 min answer diagramsmigrationrollbackreview
  3. Architecture Reviews intermediate

    The business has selected a SaaS product. You are asked to review the integration architecture after the contract is signed. What do you do?

    2 min answer vendorintegrationreviewrisk
  4. C4 Model intermediate

    A team adopts a layered diagram model and produces every level for every part of the system. What has gone wrong, and how should the model be used?

    2 min answer c4diagramsgranularitymaintenance
  5. C4 Model intermediate

    A team produces detailed component diagrams for every service and they are all stale within a sprint. Which diagram levels are worth maintaining by hand?

    2 min answer postmanc4diagramsmaintenance
  6. C4 Model intermediate Multiple choice

    If you could maintain only one architecture diagram, which would it be and why?

    2 min answer c4context-diagramaltitudemaintenance
  7. Architecture Communication intermediate

    An architect presents the same architecture deck to executives, engineers and a security review board, and each audience is dissatisfied. What is wrong with the approach?

    2 min answer communicationaudiencealtitudeatlassian
  8. Architecture Communication intermediate

    In a design review, a respected senior engineer proposes an approach you believe is wrong. The room defers to them. How do you handle it?

    2 min answer communicationdisagreementinfluencereview
  9. Context Diagrams intermediate

    What belongs on a context diagram that most teams leave off?

    2 min answer context-diagramdependenciesfailure-behaviourscope
  10. Data-Flow Diagrams intermediate

    A data-flow diagram in your compliance pack was drawn eight months ago and is signed off. A reviewer asks how you know it is still accurate. What would you change about how it is produced, and what would you keep doing by hand?

    2 min answer data flowlineageautomationcompliance
  11. Data-Flow Diagrams intermediate

    A platform must demonstrate to a reviewer where personal data goes. Which diagram serves this, and what must it include that a component diagram does not?

    2 min answer data-flowprivacyresidencytrust-boundaries
  12. Writing Decision Records intermediate

    A team writes architecture decision records that nobody reads. What makes an ADR useful, and what should it deliberately not contain?

    2 min answer linearadrdocumentationrationale