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

A platform's API is used more heavily than its web interface, and third-party tools built on it drive most adoption. What changes when the API is treated as the primary product rather than as an access mechanism?

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?

How do you know it is safe to remove a field from a public API, and what would you have needed to build to know that?

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?

An AI platform serves customers from individual developers to large enterprises, where a single request can be a thousand times more expensive than another. How should rate limiting be designed?

Design rate limiting for a multi-tenant API where a single customer's traffic spike currently degrades service for everyone.

A developer platform exposes both a resource-oriented API and a graph query API. What does each do well, and what breaks?

A marketplace of eBay's kind ranks its feed per user and re-ranks continuously as listings end and prices change, so an item's position can move within seconds. Users scroll infinitely on mobile. Which pagination approach should the API use?

A mobile client makes eleven requests to render one screen. What is the architectural problem, and what are the options?