Quiz

2868 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 areas2868 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

2868 questions.

Quiz

A multi-tenant SaaS platform cannot tell which customer caused a performance problem. What must be present in the telemetry, and what does that cost?

Etsy released StatsD in 2011: a small daemon that receives metric samples from applications over UDP, aggregates them in memory, and flushes to the metrics backend on a fixed interval. Why was UDP the right choice for that design, and what did it make permanently impossible?

Every service dashboard shows healthy metrics while users cannot complete a purchase. How is that possible and what would have detected it?

A company adopts micro-frontends across many teams. Two years later the product is slower, visually inconsistent and harder to change. What went wrong?

A front-end lead proposes micro-frontends so four teams can deploy independently. The application is a single React SPA. What is your assessment?

A team proposes micro-frontends. What genuinely justifies them, and what is the usual cost?

An organisation is considering micro-frontends so teams can deploy independently. What does this actually require, and when is it the wrong answer?

Three teams sharing one web application propose micro-frontends. Assess.

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?

Authentication, rate limiting and request tracing must behave identically across 60 services written in four languages, and the rules change roughly monthly. Where should that logic live?