Quiz

2707 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 areas2707 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 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 Architecture90 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

2707 questions.

Quiz

A team generates its entire API reference from code annotations and deletes the hand-written guide. Six months later integrators are opening more support tickets, not fewer, and every one of them is technically answerable from the reference. What did generation buy, and what did it destroy?

A workspace platform's API is well designed but developers repeatedly build integrations that break under real conditions. What is missing from the documentation, and what should be added?

Why is documenting an API's failure and retry semantics more important than documenting its success behaviour?

Your platform has 60 internal APIs. Teams repeatedly rebuild capabilities that already exist because they cannot find or understand them. What do you build?

A developer platform's API gateway has accumulated business logic and become a bottleneck for every team. What should be moved out, and what belongs there?

A public API is being overwhelmed by a handful of clients. Where should rate limiting live, which algorithm, and how should limits differ across users, tenants, endpoints and infrastructure?

An API gateway has accumulated authentication, rate limiting, routing, response transformation, request validation and some business logic. Which of these belong there?

A multi-product SaaS company exposes REST APIs, webhooks, an app marketplace, OAuth-scoped integrations and embedded plugins. Which integration surface creates the most long-term architectural constraint, and why?

An authentication provider's API is on the critical path of thousands of applications. What does that dependency position demand architecturally?

You are designing APIs for a platform with a web app, a mobile app, internal service-to-service traffic and third-party partners. What do you expose, and where?

You run a communications API of Twilio's shape, whose customers' businesses stop when you are degraded. An enterprise customer wants a contractual per-endpoint p99 latency SLA written into their renewal. Walk me through your answer.