Quiz

2777 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 areas2777 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 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 Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

1029 questions.

Quiz

An internal API is fast in isolation but a page that uses it takes 2 seconds for users in Asia while taking 200 ms in the origin region. The backend is equally fast for both. Diagnose and fix.

A platform company's teams are organised by technical layer - frontend, backend, database, infrastructure. What problems does this create, and what is the alternative?

When should a capability be owned by a platform team rather than by a stream-aligned team?

A team's backlog contains fifty technical debt items. How should they be triaged, and which category is most often mis-sorted?

A team's technical debt backlog contains hundreds of items and never shrinks. How should debt be managed?

Engineering says the codebase is full of technical debt. The business hears "we want to stop delivering and tidy up". How do you reframe it?

An engineer moves into a technical leadership role and finds their old approach no longer works. What changes?

What distinguishes technical leadership from technical seniority, and how is it measured?

A team wants to change how search results are ranked on a consumer travel site. The change sits behind a flag and can be reverted in minutes and the guardrail metrics already exist. Which written artefact should they produce to get a decision?

An engineer's technical proposal for a significant change is repeatedly deferred without a decision. How should the proposal be restructured?

An engineer's technical proposal is repeatedly sent back for more detail and still not approved. What is usually wrong with its structure?

A language runtime used by 180 of 240 services leaves vendor support in 14 months. Services are owned by 40 teams with their own roadmaps, and the upgrade is mostly mechanical but breaks in about 15% of cases. Which approach gets the estate upgraded?