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

78 questions in API & Integration.

Quiz

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.

A financial-data aggregator normalises hundreds of external bank APIs behind one interface. Where should the abstraction stop, and what happens when a provider does not fit?

A travel platform aggregates supply from hundreds of partners with wildly different protocols, latencies and reliability. Which integration patterns apply, and what is the most common structural mistake?

A core mainframe system with no API supports nightly batch file exchange only. The business needs near-real-time order status. Design the integration.

A modern service must read from a legacy system that offers only nightly batch files and a synchronous interface that cannot handle concurrent load. What integration approach fits?

An insurance platform must integrate with a legacy policy administration system with a rigid data model and batch-only interfaces. How should the boundary be designed?

The system of record updates nightly and cannot be changed. Product teams need to build against it. Design the integration.