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

51 questions in API & Integration.

Quiz

An order service publishes events consumed by six teams. Every consumer immediately calls back for order details. What is wrong and what do you change?

You operate webhook delivery for 50000 integrators. One endpoint is down for two days. Design the delivery system.

A commerce platform moves its primary API from REST to GraphQL. What genuinely improves for third-party developers, and what new problems does the platform acquire?

A shared API is a bottleneck for four client teams. Does a flexible query language fix it?

A team is about to launch a public GraphQL API. What must be in place before it goes live?

A gRPC client fleet calls a backend behind a layer-4 load balancer. After scaling the backend from 10 to 40 pods, the original 10 carry almost all the traffic and the new pods sit idle. Separately, calls have started failing with UNAVAILABLE after quiet periods. Diagnose both.

You must remove a field from a protobuf message used by dozens of deployed services. Walk through the safe sequence.

A card-issuing platform exposes an API where duplicate requests would move money twice. What is the complete idempotency contract, including the cases most implementations miss?

A payment API supports idempotency keys. Duplicate charges still occur occasionally. The server implementation is correct. Where is the bug?

A payment integration retries on timeout. Finance reports occasional double charges. The provider supports idempotency keys and they are being used. Diagnose.

A payments API must guarantee that a network retry never charges a customer twice. Design the mechanism end to end.

A payments flow in a mobility app creates duplicate charges when the mobile network drops the response and the client retries. Design the idempotency mechanism and identify where teams most often get it wrong.