Portfolio ↗

Quiz

2908 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 areas2908 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture95 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

5 questions in Pragmatism.

  1. Pragmatism beginner

    A platform brief lists eleven non-functional requirements and marks every one of them "must" - 99.99% availability, p99 under 150 ms, zero data loss, seven-year audit retention, and seven more. What does that document actually constrain, and what is the single edit that makes it constrain anything?

    3 min answer requirementsnon-functionalprioritisationbeginner
  2. Pragmatism intermediate

    An architect must choose between the correct design and the one that ships in time. How should pragmatism be exercised without accumulating unmanageable debt?

    2 min answer linearpragmatismdebtreversibility
  3. Pragmatism advanced

    Where is the boundary between pragmatism and negligence in architectural decisions?

    2 min answer pragmatismshortcutsreversibilitydocumentation
  4. Pragmatism intermediate

    You inherit a well-designed plan for a new order-management platform: eight months, event-sourced, three services, a migration path off the legacy system. The business now needs working functionality in ten weeks for a contractual commitment. How do you sequence this so the ten-week work is not thrown away?

    3 min answer sequencingpragmatismlegacyincremental-delivery
  5. Pragmatism intermediate

    You review a design for an internal tool with 200 users: microservices, Kubernetes, event sourcing, CQRS, multi-region. How do you respond?

    2 min answer pragmatismreviewcomplexity