1. Architecture Decision Records intermediate Multiple choice

    A 60-engineer platform organisation of nine teams is introducing decision records and leadership asks what a healthy annual volume looks like so they can tell whether the practice is working. Roughly how many records should they expect per year?

    2 min answer adrdecision-recordsestimationgovernance
  2. Architecture Decision Records intermediate

    A team writes decision records diligently and nobody reads them. What is wrong with the practice rather than the format?

    2 min answer adrdiscoverabilityrationalepractice
  3. Architecture Decision Records intermediate

    An interviewer asks you to pick an architectural decision your team made in the last year and write its decision record on the whiteboard, then hands you a fact partway through that would have changed the choice. What is being assessed, and how should you work through it?

    3 min answer adrdecision-recordsinterviewcontext
  4. Architecture Decision Records intermediate

    Review this decision log. It holds 140 records over four years in the repository. 31 are marked superseded and 9 of those name no successor. Two records state conflicting positions on the same message bus and both read "accepted". The template has a Consequences heading that is empty in 96 records. A new engineer asked what the current position on async messaging is and spent half a day finding out. What would you change, what would you remove, and what would you leave alone?

    3 min answer adrsupersessiondecision-lognavigability
  5. Architecture Decision Records intermediate

    Your team writes ADRs and nobody reads them. What is wrong with them?

    2 min answer documentationdecisionspractice