Portfolio ↗

Quiz

2707 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 areas2707 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 Architecture96 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 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

1005 questions.

  1. Presenting to Engineers intermediate

    An architect's design is technically sound and the engineering team resists implementing it. What is usually the communication failure?

    2 min answer communicationbuy-inrationaleengineers
  2. Presenting to Engineers intermediate

    Six weeks after a design was agreed, three of its four key decisions are implemented differently and nobody raised it. The document has 18 comments with 16 of them from two people, 11 of 14 engineers opened it once, and the decision record was merged with two approvals in under four minutes. What do you conclude, which signal is misleading, and what would have caught this in week one?

    3 min answer design documentsreviewapprovalsdivergence
  3. Environment Parity intermediate

    A change passes every test in staging and fails immediately in production. Staging is a faithful copy of the topology. What are the most likely causes, and what would you change?

    2 min answer environmentsparitytesting
  4. Environment Parity intermediate

    Which dimensions of environment parity actually matter, and which are safe to differ?

    1 min answer parityenvironmentsconfigurationdeployment
  5. Environment Strategy intermediate

    An organisation has development, integration, staging, pre-production and production environments, and bugs still reach production. What should change?

    2 min answer freshworksenvironmentsparitytesting-in-production
  6. Environment Strategy intermediate

    An organisation maintains many long-lived environments and they have all drifted from production. What environment strategy works?

    2 min answer environmentsdriftephemeralparity
  7. Environment Strategy intermediate

    Six teams share one integration test environment. Bookings are made a week ahead and releases slip when someone overruns. How do you fix it?

    1 min answer environmentsdeliverytestingqueues
  8. 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
  9. 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
  10. 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
  11. 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
  12. Estimation intermediate

    An architect is asked how long a migration will take and has genuinely no basis for a number. How should estimation be approached so the answer is useful rather than either false precision or a refusal?

    2 min answer estimationuncertaintyrangesdecomposition