Quiz
98 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 areas98
Architecture Fundamentals2
Distributed Systems26
Data Architecture23
Cloud Architecture4
Networking3
API & Integration Architecture1
Reliability & Resilience4
Observability3
Performance & Capacity Engineering3
Security Architecture3
Cost Architecture & FinOps3
Business Architecture2
Architecture Communication2
Enterprise Architecture1
Legacy Modernization2
AI-Era Architecture3
Software Architecture & Engineering3
Architecture Patterns3
Architecture Decision-Making6
The Architect's Meta-Skills1
6 questions in Architecture Decision-Making.
-
Architecture Decision-Making advanced
Netflix built its own CDN; Dropbox moved storage off S3. Both are usually wrong. What conditions made them right, and how do you test for those conditions?
2 min answer case-studybuild-vs-buynetflixdropbox -
Architecture Decision-Making intermediate
Security wants mandatory hardware keys for every login; the business says it will cost conversions. How do you resolve it architecturally rather than by picking a side?
2 min answer securityusabilityriskauthentication -
Architecture Decision-Making intermediate
The team can ship in six weeks with an approach that will need rework, or five months with one that will not. How do you decide, and what do you do either way?
2 min answer technical-debtdeliverytrade-offssequencing -
Architecture Decision-Making beginner
When is an architectural decision worth an ADR, and what makes an ADR useful two years later?
2 min answer adrdocumentationgovernance -
Architecture Decision-Making intermediate Multiple choice
When should a service call another synchronously, and when should it publish an event instead? Give me the deciding test, not a preference.
2 min answer syncasynccouplingavailability -
Architecture Decision-Making intermediate
You are reviewing a design for an internal tool with 200 users. It proposes Kubernetes, microservices, Kafka, a service mesh and CQRS. How do you handle the review?
2 min answer over-engineeringreviewpragmatismgovernance