Portfolio ↗

Quiz

2827 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 areas2827 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns84 Architecture Decision-Making101 The Architect's Meta-Skills92 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

2827 questions.

  1. Environment Strategy intermediate

    Six teams share one staging environment. Booking it is a bottleneck and it is permanently broken by whoever deployed last. Design a way out.

    2 min answer environmentsplatformflow
  2. Environment Strategy intermediate

    You have one quarter to delete the shared staging environment that eight teams deploy into. Sequence the work so each step is reversible, say where the point of no return actually is, and name what cannot move.

    3 min answer environment-strategycontract-testingdecommissionsequencing
  3. Erasure vs Immutability advanced

    A brokerage must keep an immutable audit trail and honour erasure requests. How can both be true?

    2 min answer growwerasureimmutabilitypseudonymisation
  4. Erasure vs Immutability advanced

    A marketplace of eBay's shape has an append-only event log of roughly 8 billion events over six years with personal data inline in the payloads. A new erasure obligation lands and crypto-shredding is the chosen answer, but no per-subject keys exist yet. Sequence the migration under live traffic and name the point of no return.

    3 min answer crypto-shreddingevent-sourcingenvelope-encryptionobject-lock
  5. Erasure vs Immutability advanced

    An event-sourced system keeps an immutable log. A subject requests erasure. How is this resolved?

    1 min answer erasureimmutabilityevent-sourcingcrypto-shredding
  6. Erasure vs Immutability advanced Multiple choice

    Your core system is event-sourced. A customer exercises their right to erasure. The events are immutable by design. What do you do?

    2 min answer gdprevent-sourcingdesign
  7. Error Budgets advanced

    A platform has an error budget policy stating that feature work stops when the budget is exhausted. The budget is exhausted, and product leadership wants a major launch to proceed. How should this be resolved?

    2 min answer error-budgetspolicygovernancereliability
  8. Error Budgets advanced

    A team consistently ends every window with 90% of its error budget unspent. What does that tell you?

    2 min answer error-budgetsloover-investmentrisk
  9. Error Budgets advanced

    A team consistently exhausts its error budget and continues shipping features. What has gone wrong, and what would make the budget actually function?

    2 min answer crederror-budgetslogovernance
  10. Error Budgets beginner

    A team has a 99.9% availability SLO, giving about 43 minutes of error budget a month. Three weeks in, the budget is untouched. What does that actually permit the team to do, and what does an untouched budget indicate?

    3 min answer error budgetssloreliabilityrelease velocity
  11. Error Budgets advanced

    How does an error budget actually change behaviour, what makes it fail in practice, and what should happen when it is exhausted?

    3 min answer googlesresloerror-budget
  12. 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