Exercise 1: A Web Search for an Event ID Returns Unrelated Results — Possible Solution
====================================================================

WHAT MOST LIKELY WENT WRONG
------------------------------
Per this chapter's own warn-box, "Event IDs are only unique within a
given Source - Event ID 1000 logged by one app's source has no
necessary relationship at all to Event ID 1000 logged by a different
source." The most likely explanation is that the search was performed
using the Event ID number alone, without including the specific Source
that actually logged it - returning results about a completely
different Source's own unrelated event that happens to share the same
numeric ID.

WHY THE NUMBER ALONE ISN'T A RELIABLE SEARCH KEY
------------------------------
Per this chapter, "searching an Event ID number alone, without
including its Source, is a genuinely common way to land on someone
else's unrelated problem that just happens to share the same number."
Event ID numbers are assigned independently by whichever component or
application logs them - there's no central registry ensuring uniqueness
across every possible Source on the system, so collisions between
unrelated sources using the same number are expected, not a rare
coincidence.

THE FIX
------------------------------
Per this chapter, "the Event ID is the single most useful field for
research - searching a specific Event ID plus its Source name is
usually far more productive than searching the event's own free-text
description." Checking the event's own Source field (visible directly
in Event Viewer alongside the Event ID) and including that Source name
in the search - rather than the number alone - narrows results to the
actual relevant component rather than any other unrelated one that
happens to log the same ID.

WHY THIS MATTERS FOR SEARCH EFFICIENCY GENERALLY
------------------------------
Skipping the Source and searching the number alone doesn't just
occasionally fail - it's specifically named in this chapter as a
common, foreseeable mistake, meaning it's worth building "ID plus
Source" into the habit itself rather than treating each mismatch as a
surprising one-off.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the missing-Source search as the specific cause using
this chapter's own warn-box, explains why Event ID numbers collide
across unrelated sources in the first place, and gives the concrete fix
(searching ID plus Source together) directly from this chapter's own
guidance.