Portfolio ↗

Quiz

2948 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 areas2948 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking96 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

6 questions in Team Topologies.

  1. Team Topologies advanced

    A mobility platform's teams are organised by technical layer - mobile, backend, data, infrastructure. Why does that slow delivery, and what is the alternative?

    2 min answer olateam-topologiesconwaystream-aligned
  2. Team Topologies intermediate

    A platform company's teams are organised by technical layer - frontend, backend, database, infrastructure. What problems does this create, and what is the alternative?

    2 min answer team-topologiesstream-alignedhandoffsconways-law
  3. Team Topologies beginner Multiple choice

    A team of four engineers owns one service with a 24/7 paging rota. Leadership wants them to take on two more services of similar size. Which fact about the rota decides whether that is possible?

    3 min answer team-topologieson-callcognitive-loadownership
  4. Team Topologies advanced

    An organisation runs nine stream-aligned teams, a platform team of five and an enabling pair. Each stream team holds a standing weekly 90-minute sync with every other stream team it integrates with, which currently means fourteen standing pairs, plus a weekly architecture guild. Senior engineers report 9 to 11 hours a week in cross-team meetings and every interface is described as "agreed in the sync" rather than written down. Review this. What would you remove, what would you change and what would you leave alone?

    2 min answer team-topologiesinteraction-modescouplingcognitive-load
  5. Team Topologies advanced

    Leadership accepts that the current three-layer team structure is producing a tightly coupled system, and reorganises into cross-functional product teams in one step. What happens over the following six months?

    3 min answer conways lawreorganisationownershiptransition cost
  6. Team Topologies intermediate

    When should a capability be owned by a platform team rather than by a stream-aligned team?

    2 min answer team-topologiesplatformcognitive-loadself-service