Quiz

2741 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 areas2741 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

2741 questions.

Quiz

A team proposes circuit breakers on every downstream call. What would you add, and why is the breaker not the most important control?

After adding circuit breakers, a partial outage now lasts three times longer than it used to. What is likely happening?

You maintain circuit breakers across 200 services. Configuration drift means half are misconfigured. What do you do?

Your circuit breaker opens during normal traffic spikes, causing outages it was meant to prevent. How do you configure it correctly?

A service calls a payment provider over HTTP. The provider occasionally returns 503 and occasionally times out. In a domain / application / adapter layering, which layer should own the retry and backoff policy?

A team adopts a layered architecture with strict dependency rules and finds every small change touches many files. Is the architecture wrong, or the application of it?

Review this design. Every repository method opens its own transaction and commits before returning. One use case calls four repositories and then publishes an event. Support reports occasional orders with a payment row and no shipment row. What would you change and what would you leave alone?

When is clean architecture over-engineering, and what is the signal that you have its costs without its benefits?

A quick-commerce app must feel instant while showing inventory that changes constantly. What caching strategy on the client?

A single-page application shows stale data after a user makes a change elsewhere in the product. How should client-side caching and invalidation be designed?