Exercise 3: What the Worked Example's Error Body Revealed — Possible Solution
====================================================================

WHAT THE ERROR BODY DIRECTLY REVEALED
------------------------------
Per this chapter's worked example, the error body showed
"error": "pool_timeout" with the message "Could not obtain a database
connection within 30000ms" and "retryable": true - directly stating,
in plain terms, that this is a connection pool timeout and that it's
expected to be transient, without needing to grep any logs to find
this out.

THE FIRST AGREEING PIECE OF EVIDENCE: CHAPTER 1'S OWN PREVIEW
------------------------------
Chapter 1 previewed this exact error category directly - its own
example error message ("could not obtain connection from pool: timeout
after 30000ms") is effectively the same finding this chapter's worked
example confirms, tying the two chapters' running ticket together.

THE SECOND AGREEING PIECE OF EVIDENCE: THE FAILURE-RATE PATTERN
------------------------------
Per this chapter, the ticket was described as "intermittent 500s under
load" - matching this chapter's own "a small, intermittent percentage
fails" pattern, which it identifies as pointing toward "a
resource-contention or timing-sensitive cause - connection pool
exhaustion." The failure-rate pattern independently pointed toward the
same category of cause the error body then confirmed directly.

WHY THIS WORKS AS AN ANSWER
------------------------------
It states specifically what the error body revealed (pool_timeout,
retryable), and names two separate, independent pieces of supporting
evidence (Chapter 1's own preview and the intermittent failure-rate
pattern) that both pointed toward the same conclusion, rather than
treating the error body as the only evidence involved.