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

78 questions in API & Integration.

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

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?