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

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 payments API has thousands of integrators on many SDK versions. How should versioning, deprecation, compatibility testing and migration tooling be designed?

A public API must keep every historical version working for thousands of integrators while the team keeps shipping breaking changes. Compare date-pinned per-account versioning with URL versioning and feature flags.

An enterprise platform supports many years of API versions simultaneously because customers integrate deeply and upgrade slowly. What does that policy cost, and what would you do differently?

You are designing a public payments API. Consumers are numerous, unknown and unmotivated to migrate. How do you handle breaking changes?

Your mobile app's API has 14 versions in the field, the oldest three years old. Product wants to remove support. How do you decide?

A grocery platform integrates with retail partners whose inventory data varies in freshness, completeness and reliability. How should the integration be designed so one partner's bad data does not degrade the whole platform?

An enterprise integration platform connects to many customer identity systems with different reliability and behaviour. How should directory sync, SSO and webhook processing be isolated?