Quiz

2627 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 areas2627 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture77 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture85 Cost Architecture & FinOps82 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization82 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

45 questions in Architecture Decision-Making.

Quiz

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?

Three years of architectural decisions live in a wiki, in chat threads and in two shared documents. The team agrees to move decision records into the repository beside the code without a 300-page backfill. Give the sequence, and name the point of no return.

A decision must be made now and the information needed will not be available for six months. What should the approach be?

A sponsor wants a date for a programme with several unknowns. Refusing to estimate is not an option. How do you handle it?

An architectural decision must be made with genuinely insufficient information and the cost of delay is real. How should it be approached?

An architecture decision must be made when the workload, scale and requirements are genuinely unknown. What approach works?

How would you make the case for a two-sprint refactor to a product manager under delivery pressure?

Your team runs a large self-managed streaming cluster. Two engineers hold most of the operational knowledge. A managed alternative exists. How do you decide?

A B2B analytics company runs 40 services with 12 engineers. Deploys are independent, but a typical feature touches four services and takes three weeks to reach production. Review this architecture: what would you merge, what would you leave alone, and how would you argue it?

A platform must choose between a modular monolith and microservices for a new product line. What evidence should decide it?

A team of fifteen wants to start a new product as microservices. How do you advise?