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

84 questions in Software Architecture.

Quiz

What does hexagonal architecture give you that a conventional layered design does not?

A platform adopts microservices and now needs service discovery, distributed tracing, multiple pipelines, a message broker and complex local development. Which of these costs are inherent and which indicate a boundary problem?

A team adopted microservices and now every feature touches five services, five pipelines and a distributed debugging session. Which boundaries were justified, and when is consolidation the improvement?

An organisation cites Netflix as justification for adopting microservices. What is missing from the comparison?

Your organisation has grown to 2,000 microservices. Teams report that understanding and changing the system is now harder than before decomposition. What do you do?

A product team of fifteen engineers must choose between a modular monolith and services. What should decide it?

A productivity app keeps a full local database on each client and syncs deltas with the server. Why would a small team choose this over conventional REST, and how are optimistic updates, conflicts, permission changes and client schema migrations handled?

A team adopts a modular monolith. What must they do forever, and what happens if they stop?

A team chooses a modular monolith over microservices. What makes the module boundaries actually hold, and what signals indicate it is time to extract a service?

What mechanically enforces module boundaries in a monolith, and what happens without enforcement?

A team schedules a large refactoring project and it is repeatedly deprioritised. What approach actually gets refactoring done?

An enterprise software vendor of SAP's shape must replace a logging call used at 2,400 sites across 1,100 files owned by 40 teams. The codemod itself takes an afternoon to write. Sequence the change so it lands once and stays landed.