Exercise 3: Why Reading the Full Error Message Saves Time — Possible Solution
====================================================================

Per the chapter, a full "access denied" error typically contains three
genuinely useful pieces of information:

1. THE SPECIFIC ACTION that was denied (e.g. `s3:GetObject`) -- rather
   than guessing "something about permissions," this tells you EXACTLY
   which capability is missing, immediately narrowing which part of a
   policy needs attention rather than reviewing an entire policy
   document broadly.

2. THE SPECIFIC RESOURCE the action was attempted against -- the exact
   identifier, not just a general category like "a bucket." This
   immediately answers whether the issue is a missing permission
   ENTIRELY, or a resource-level SCOPING mismatch (per this chapter's
   debugging-order step 4) -- an allow that exists, but for a
   different resource than the one actually being accessed.

3. SOMETIMES, WHICH SPECIFIC POLICY OR BOUNDARY caused the denial --
   when available, this skips several steps of the chapter's own
   debugging order entirely, pointing directly at the exact policy
   document (or org-level boundary) responsible, rather than requiring
   a full manual walk through every attached policy one at a time.

Why skipping this and guessing instead wastes time:

Without this information, a support engineer or user is left
reviewing policies broadly, guessing at which action or resource might
be the problem, and potentially checking irrelevant policies or
resources entirely -- exactly the "assuming a cause and starting to
make changes" behavior the chapter's own tip-box warns against. The
error message frequently already contains the answer to "what specific
thing failed" -- reading it first converts a broad, uncertain
investigation into a targeted one from the very first step.

WHY THIS WORKS AS AN ANSWER
------------------------------
This directly maps each piece of information the chapter names to the
SPECIFIC debugging-order step it lets you skip to or narrow
immediately, rather than vaguely asserting that reading errors is
"good practice" -- showing concretely how each detail shortens the
investigation described earlier in the chapter.