Exercise 2: Why an App's Own Log Branch Reveals More Than the General Application Log — Possible Solution
====================================================================

WHAT THE GENERAL APPLICATION LOG ACTUALLY CONTAINS
------------------------------
Per this chapter's own compare-table, Windows Logs' Application
category covers "Application, Security, Setup, System, Forwarded
Events - five broad, system-wide categories," used for "general system
health... install/update history." It's a shared space every
application on the machine can write to, which necessarily keeps
entries relatively general.

WHAT APPLICATIONS AND SERVICES LOGS OFFER INSTEAD
------------------------------
Per the same table, this is "a separate, much larger tree - one branch
per installed app or Windows component, often further split into
Operational/Admin/Analytic/Debug channels," used for "diagnosing one
specific app or component's own detailed behavior, when the general
System/Application log doesn't have enough detail."

WHY THIS PRODUCES MORE DETAIL FOR A SPECIFIC CRASH
------------------------------
Per this chapter, "a crash visible only as a generic entry in the
Application log often has a much richer, more specific trail waiting in
that same app's own dedicated branch." Because the general Application
log is shared across every app on the system, an app logging there
typically writes only a brief summary entry, reserving more detailed,
step-by-step diagnostic information for its own dedicated branch under
Applications and Services Logs - a space built specifically for that
one app's own use, with no need to stay brief the way a shared log
does.

WHY THIS MATTERS PRACTICALLY WHEN TROUBLESHOOTING ONE APP
------------------------------
Per this chapter, this dedicated branch is "worth checking there first
for anything app-specific, rather than assuming the general log tells
the whole story." Someone troubleshooting a specific application's
crash who only checks the general Application log risks stopping at a
vague summary entry, missing a much more specific, actionable trail
sitting one level deeper in that same app's own log branch.

WHY THIS WORKS AS AN ANSWER
------------------------------
It contrasts what each log category actually contains using this
chapter's own compare-table, explains the structural reason
(shared-vs-dedicated space) that produces less detail in the general
log, and connects that reasoning to this chapter's own practical
recommendation to check the app-specific branch first.