Exercise 1: What the Combined Filter Prevents — Possible Solution
====================================================================

WHAT THE FILTER ACTUALLY DOES
------------------------------
The query only matches a row where both item_id equals the requested id AND status equals "active". If a row with that id exists but its status is already "used", the query matches nothing at all, and the route returns a 404 rather than modifying anything.

WHAT WOULD GO WRONG WITHOUT THE status == "active" PART
------------------------------
Without that condition, the query would match the row purely by id, regardless of its current status. If a user clicked "Mark Used" twice on the same item - a double-click, a slow network causing a retry, or clicking again before the UI visibly updated - the second request would still find and update the row, overwriting used_at with a new, later timestamp even though the item was already genuinely marked used at an earlier, correct moment. The historical record of exactly when the item was actually used would silently become wrong.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that the combined filter makes the query only match a currently-active row, and correctly identifies the concrete consequence of dropping the status condition: a second click would still succeed and overwrite used_at with an incorrect, later timestamp instead of safely returning a 404.