# ADR Writing Quiz

## Question 1

What is the primary purpose of an ADR?

A) To document every code change
B) To capture the reasoning behind significant architecture decisions
C) To replace design documents
D) To track project milestones

<!-- ANSWER: B -->
<!-- EXPLANATION: ADRs document why we made important architectural decisions. They preserve context for future readers who would otherwise wonder "why did we do this?" -->

## Question 2

Which section of an ADR describes the options and constraints that led to the decision?

A) Decision
B) Consequences
C) Context
D) Status

<!-- ANSWER: C -->
<!-- EXPLANATION: Context explains the forces, options, and constraints. It sets the stage so readers understand why the decision mattered. -->

## Question 3

When should you use the status "Superseded"?

A) When the decision was never implemented
B) When the decision is replaced by a newer ADR
C) When the decision is temporarily paused
D) When the decision is under review

<!-- ANSWER: B -->
<!-- EXPLANATION: Superseded means another ADR has replaced this one. You should link to the new ADR. Use Deprecated when the decision is no longer followed but not replaced. -->

## Question 4

A common pitfall when writing ADRs is:

A) Writing them too early
B) Writing them too late, after memory has faded
C) Using too many bullet points
D) Including code samples

<!-- ANSWER: B -->
<!-- EXPLANATION: Write ADRs when you make the decision. If you wait, you forget nuances, options considered, and tradeoffs. Late ADRs are often incomplete or inaccurate. -->

## Question 5

Where should ADRs typically be stored?

A) In a separate wiki
B) In the project repository (e.g., docs/adr/)
C) In email threads
D) In a project management tool

<!-- ANSWER: B -->
<!-- EXPLANATION: Storing ADRs in the repo keeps them versioned, co-located with code, and discoverable. They travel with the project and are easy to find. -->

## Question 6

Why is it important to document negative consequences in an ADR?

A) To discourage future changes
B) To provide honest tradeoffs for future readers making related decisions
C) To satisfy auditors
D) To reduce the document length

<!-- ANSWER: B -->
<!-- EXPLANATION: Negative consequences help future readers understand tradeoffs. If they face similar choices, they know what downsides to watch for. Honesty builds trust. -->
