Portfolio ↗

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

1544 questions.

  1. Rate Limiting advanced

    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?

    2 min answer rate-limitingtoken-bucketfairnessquotas
  2. Rate Limiting advanced

    Design rate limiting for a multi-tenant API where a single customer's traffic spike currently degrades service for everyone.

    2 min answer rate-limitingmulti-tenantfairnesstoken-bucket
  3. API Shapes for UI advanced

    A developer platform exposes both a resource-oriented API and a graph query API. What does each do well, and what breaks?

    1 min answer api-designgraphqlrestcaching
  4. API Versioning advanced

    A payments API has thousands of integrators on many SDK versions. How should versioning, deprecation, compatibility testing and migration tooling be designed?

    2 min answer razorpayversioningdeprecationcompatibility
  5. API Versioning advanced

    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.

    3 min answer stripeapi-versioningbackward-compatibilitytransformations
  6. API Versioning advanced

    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?

    2 min answer versioningdeprecationbackward-compatibilityenterprise
  7. API Versioning advanced

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

    2 min answer stripeapi-designversioningcompatibility
  8. Application Performance Monitoring advanced

    In a multi-tenant platform, aggregate application performance metrics look healthy while specific tenants experience severe slowness. What must performance monitoring do differently?

    2 min answer apmmulti-tenancysegmentationoutliers
  9. Application Performance Monitoring advanced

    Review this instrumentation. A checkout service emits about 400 spans per request, every span carries roughly 30 attributes including the full request body, tracing runs at 100% with no sampling, and the team reports that they cannot find anything in the traces. What would you remove, what would you change, and what would you keep even though it looks excessive?

    3 min answer tracingapminstrumentationsampling
  10. Application Architecture advanced

    A global employment platform must handle country-specific rules that differ in every dimension. How should the architecture accommodate that variation?

    2 min answer remotedeeljurisdictionvariation
  11. Application Architecture advanced Multiple choice

    An enterprise platform serving many countries keeps hitting jurisdiction-specific rules - different approval chains, retention periods, mandatory fields and tax treatments - that vary independently of each other. Which accommodation holds up as the number of jurisdictions grows?

    2 min answer saplocalisationrule-enginevariability
  12. Application Architecture advanced Multiple choice

    An enterprise platform's application architecture must serve tenants ranging from small businesses to very large enterprises. Should one architecture serve all of them?

    2 min answer application-architecturemulti-tenancytieringsalesforce