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

A commerce platform runs a very large monolith serving enormous traffic and chooses not to decompose it into microservices. What must be true for that to be the right choice?

Knight Capital lost roughly $460M in 45 minutes in 2012 after a deployment reached seven of eight servers. Which architectural failures made that possible, and which one would you fix first?

Uber reached roughly 2,200 microservices and found the estate incomprehensible. Their fix was not consolidation. What was it, and why does it generalise?

You need to ship a rewrite of the pricing engine. Same inputs, same expected outputs, completely new implementation. How do you release it?

A developer-tools vendor of JetBrains' shape publishes a plugin API used by several thousand third-party plugins it does not control and cannot enumerate. An architect proposes consumer-driven contract tests. Which approach actually protects a release?

Consumer-driven contract testing is technically sound but adoption stalls. What organisational conditions does it require?

How does contract testing let two teams deploy independently, and what does it not tell you?

A reviewer rejects a change for violating the single responsibility principle. When is that a substantive objection and when is it cargo cult?

After a refactor replaced a list implementation with an immutable one, a nightly job starts failing with an unsupported-operation error on a line nobody has edited in two years. Every type matches and the compiler was happy. What broke, and what is the design fix?

Which SOLID principle has genuine architectural consequences, and which one most often produces harm?

Which SOLID principle produces the most practical benefit in a large codebase, and which is most often misapplied?

A team's backlog contains fifty technical debt items. How should they be triaged, and which category is most often mis-sorted?