Debugging Methodology — question 4 of 10
Write a real answer. It is graded against the question's rubric, and the mastery movement is computed by the same engine the product uses. Scoring here is deterministic rather than model-written, so this page costs nothing to run and nothing is saved. In a track built from your own posting, the same rubric is graded by the model, which is what produces feedback about your reasoning rather than about coverage.
A board resets itself at unpredictable times — sometimes within an hour, sometimes not for a full day, with no obvious pattern. Before you touch the schematic, swap a capacitor, or change any code, what do you need to establish first, and specifically what would you do to try to make this failure happen more often and more predictably?