Portfolio ↗

Quiz

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

2741 questions.

  1. Cluster Architecture advanced

    A Kubernetes upgrade to 1.24 removes a deprecated node label. Within minutes the cluster's pod network loses all routes and stays down for over five hours, and the configuration responsible is not in any repository. What kind of dependency is this, and how would you have found it beforehand?

    3 min answer redditkubernetesupgradecalico
  2. Cluster Architecture advanced

    A platform must decide between one large cluster and many small ones. What are the trade-offs?

    2 min answer browserstackclustersisolationefficiency
  3. Cluster Architecture advanced

    How many Kubernetes clusters should an organisation run, and what decides the boundaries?

    2 min answer kubernetesclustersblast-radiusisolation
  4. Cluster Architecture advanced

    How should compute clusters be structured for a platform running many teams' workloads with very different profiles?

    2 min answer clusterscellsisolationnode-pools
  5. Cluster Architecture advanced

    Your platform team of five spends nearly all its capacity upgrading control planes across 38 Kubernetes clusters. How did this happen and how do you fix it?

    2 min answer platformkubernetesconsolidationoperations
  6. Code Review intermediate

    A 40-engineer platform organisation requires two approvals on every pull request. Median time from ready-for-review to merge is 26 hours. A staff engineer proposes one approval plus mandatory post-merge review for low-risk changes. What is gained, what is paid, and when does the bill arrive?

    2 min answer code reviewlead timechange failure ratecodeowners
  7. Code Review intermediate

    A platform's code review process is slow and catches few defects. What should change?

    2 min answer code-reviewsizelatencyautomation
  8. Code Review beginner Multiple choice

    A team reviews small changes carefully and approves large ones within minutes. Why does defect detection collapse as a change grows, and which single intervention recovers the most of it?

    2 min answer code reviewdefect detectionbatch sizeattention
  9. Code Review intermediate

    A team's code review process is slow and catches few real problems. What should change?

    1 min answer postmancode-reviewfeedbackautomation
  10. Code Review intermediate

    Code review latency in your team averages one day. What do you change and what do you measure?

    2 min answer code-reviewlatencybatch-sizeflow
  11. Coexistence Patterns advanced

    A migration will take eighteen months, during which old and new systems both serve production. How should the coexistence period be designed?

    2 min answer digitcoexistenceroutingconsistency
  12. Coexistence Patterns advanced

    During a multi-year migration, old and new systems must coexist. Which coexistence patterns are sustainable and which accumulate debt?

    2 min answer coexistencedual-writeownershipreconciliation