Quiz

2667 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 areas2667 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 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

1544 questions.

Quiz

An analytics platform's query costs are growing faster than its data. What are the drivers and controls?

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?

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 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.

A business-banking platform must expose payouts, balances, approvals and reconciliation to customer developers. How should the API surface be structured, and what determines what is exposed?

API traffic is dominated by a few automation-heavy customers whose bursts affect everyone. How do you introduce per-tenant quotas and priority without breaking existing integrations?

You must make a breaking change to an API used by 200 internal services and 40 external partners. Design the change and the migration.

A payments API must stay available on the highest-traffic commerce day of the year. How should rate limiting and load shedding be structured so that critical traffic survives while non-critical traffic is sacrificed?

A rate limiter protects an API from abuse, but enterprise customers have legitimate predictable bursts. How should quotas differ by tenant, endpoint, priority and available capacity?