Portfolio ↗

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.

  1. Partner & B2B Integration intermediate

    Partner integrations take four months from contract signature to production traffic. Engineering says the work is three days. Where does the time go and how do you cut it?

    2 min answer b2bonboardingdeveloper-experiencesandbox
  2. Partner & B2B Integration advanced

    You must make a breaking change to an API used by 5000 partner organisations. What is your plan?

    3 min answer b2bversioningdeprecationpartners
  3. Backward Compatibility advanced

    Salesforce scheduled the retirement of Platform API versions 21.0 through 30.0 for the Summer '23 release and later postponed it to Summer '25, having retired versions 7.0 through 20.0 in Summer '22. After retirement, REST calls on a retired version return 410 Gone. What does a postponement of that size tell you about deprecation as a mechanism, and what would you build so that yours does not slip?

    3 min answer salesforcedeprecationapi versioningsunset
  4. Backward Compatibility intermediate

    What happens if an enterprise software vendor adds a required field to a widely-integrated interface, believing it is a minor change?

    2 min answer backward-compatibilitybreaking-changeintegrationenterprise
  5. Backward Compatibility beginner

    Your API returns a JSON object. Which of these changes can break a client you have never met: adding a field, removing a field, changing a field's type, adding a value to an enum, reordering keys, or making an optional field always present?

    3 min answer backward compatibilityjsonenumsparsers
  6. Contract Testing intermediate

    A platform has many services and many external consumers. Integration tests are slow and flaky. What testing strategy actually gives confidence about compatibility?

    2 min answer hasuracontract-testingconsumer-drivenci
  7. Contract Testing advanced Multiple choice

    A platform with many services finds that integration tests are slow and flaky, yet removing them causes breakages between services. What testing approach resolves this, and what does it require organisationally?

    2 min answer contract-testingconsumer-drivenintegration-testsci
  8. Contract Testing advanced

    An organisation with hundreds of services finds integration bugs in production despite extensive testing. How do consumer-driven contract tests fit, and what do they not solve?

    3 min answer contract-testingpactintegrationci
  9. Contract Testing intermediate Multiple choice

    Before deploying, how do you know whether removing a response field will break any consumer?

    2 min answer contract-testingconsumer-drivencispotify
  10. Contract Testing advanced

    Integration failures between 30 services are found in a shared staging environment, days after merge. Propose a change.

    2 min answer contract-testingciintegrationorganisation
  11. API Error Handling intermediate

    A platform's plugin API returns generic 500 errors when anything goes wrong. Developers cannot tell whether to retry, fix their code, or contact support. Redesign the error model.

    2 min answer error-handlingapi-designretryabilitydeveloper-experience
  12. API Error Handling intermediate

    A public API's errors are a mixture of HTTP status codes, free-text messages and inconsistent bodies. Design an error contract that integrators can automate against, and explain what each part is for.

    2 min answer api-designerrorsretryabilityintegrators