Quiz

2948 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 areas2948 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking96 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 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

2948 questions.

Quiz

One customer generates 60% of your event volume. Their partition's consumer cannot keep up and the rest idle. What are your options?

A collaboration product is sharding its database. Options are hash of message ID, hash of user ID, or workspace ID. Which and why?

A marketplace's product database has become the bottleneck for a read-heavy workload. The team proposes sharding immediately. What lower-complexity options should be exhausted first, and in what order?

A messaging platform stores messages partitioned by channel identifier. Some channels are enormously more active than others. Fix the partitioning.

A multi-tenant SaaS platform runs thousands of tenants on a shared relational database, but a handful of tenants now hold most of the data. Should it use shared tables, tenant partitioning, dedicated databases, sharding or a hybrid?

A workspace product stores every document as a tree of small "block" rows in one enormous table. Growth makes the table unmanageable. Design the sharding strategy - and identify the choice that is effectively irreversible.

Your geospatial data is partitioned by city. One city generates 40% of all traffic. What are your options?

An experienced architect recognises a familiar pattern and proposes the solution that worked before. What are the risks, and how are they managed?

An interviewer asks which architectural analogy you reach for too often. Assume you genuinely do not know the answer. How would you find it from your own written record, and what would you do with the finding?

Pattern recognition is what makes an experienced architect fast. What is its characteristic failure and how do you guard against it?

A team says the golden path cannot support their workload and wants to build their own deployment tooling. How do you respond?