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

1529 questions.

Quiz

A metadata-driven API layer generates queries over a customer's database. A customer writes a deeply nested query that produces a catastrophic join. Is that an abstraction failure, and what should the design do about it?

A team proposes wrapping every cloud provider SDK behind an internal abstraction so the company could migrate providers later. Evaluate the proposal.

Design the abstraction boundary for a "vote" on a large discussion platform where a handful of threads receive an enormous share of all votes. What should the interface promise, what must it hide, and what must it refuse to hide?

A platform must choose how much of the underlying infrastructure to abstract. What decides the level?

A platform team must decide how much to abstract the underlying infrastructure. What goes wrong at each extreme, and how do you choose?

An internal platform must decide how much of the underlying infrastructure to hide. What determines the right abstraction level, and what happens at each extreme?

Your platform abstracts Kubernetes entirely — teams write a short manifest and everything is generated. Now every production incident escalates to the platform team. What is happening?

Six weeks before launch, an accessibility audit returns 200 issues. The team's automated checks were green. Why, and what do you do?

Where should accessibility live architecturally so it is not a remediation project every year?

A platform builds an agent that plans and executes multi-step tasks against business systems. Which architectural constraints are non-negotiable?

A team is building an agent that plans and executes multi-step tasks. What architectural bounds must exist, and what usually goes wrong?

An agent that researches and summarises occasionally runs for 40 minutes and costs £30 for one request. How do you contain it?