Exercise 2: Finding What's Holding a File Open — Possible Solution
====================================================================

WHY TASK MANAGER ALONE DOESN'T ANSWER THIS
------------------------------
Task Manager's own Processes tab shows resource usage grouped by app,
not which specific files a process currently has open. If nothing
obviously related is running as a visible app, Task Manager has no view
that connects a locked file back to the process actually holding it
open - it simply isn't built to answer that particular question.

THE TOOL THAT SOLVES THIS
------------------------------
Per this chapter, "Resource Monitor... goes further than Task Manager
in one specific, high-value way: its Disk tab shows exactly which
process has a given file open, by full file path - the direct answer
to 'why won't this file let me delete/rename it,' a question Task
Manager alone can't answer." Resource Monitor's Disk tab is built
specifically to answer this exact scenario.

HOW TO USE IT HERE
------------------------------
Opening Resource Monitor (resmon.exe) and checking its Disk tab's list
of open files by path would reveal exactly which process - by name and
PID - currently has the problem file open, even if that process isn't
an obviously related, visibly-named app (it might be a background
service, a previous instance of a program still running invisibly, or
an unrelated process that happened to open the file).

WHY THIS EXPLAINS THE "NO OBVIOUSLY RELATED APP" PART OF THE SCENARIO
------------------------------
The scenario specifically notes Task Manager shows nothing obviously
related - which fits exactly why Resource Monitor is needed rather than
Task Manager: the process holding the file open may not be an app
whose name would obviously connect to that specific file at a glance in
Task Manager's own Processes list, but Resource Monitor's Disk tab
identifies it directly by the file path itself, regardless of how
recognizable the process name is.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains specifically why Task Manager can't answer this question,
identifies Resource Monitor's Disk tab as the tool built for exactly
this scenario using this chapter's own wording, and connects that
capability directly to why it succeeds where Task Manager's own visible
app list fails.