Exercise 1: Symptom-Out vs. Bottom-Up — Possible Solution
====================================================================

WHAT NETWORKING FUNDAMENTALS' BOTTOM-UP APPROACH IS FOR
------------------------------
Per this chapter, a networking course works "bottom-up - physical layer,
then link, then network, then up" because the goal is to build and
configure a network correctly from scratch. Getting an early layer
wrong causes problems in everything built on top of it, so reviewing
each layer in full, in order, is the right discipline when nothing
exists yet.

WHY THAT SAME DISCIPLINE DOESN'T FIT A SUPPORT TICKET
------------------------------
Per this chapter, a support engineer isn't starting from nothing - "the
network already works for almost everyone else." Reviewing every layer
in full for one user's single complaint would mean re-checking things
that are almost certainly fine, which wastes time the bottom-up
approach doesn't need to worry about when building something new.

WHY IT'S A DIFFERENT JOB, NOT JUST A FASTER VERSION
------------------------------
"Faster version of the same thing" would imply skipping steps of the
same bottom-up review to save time. But this chapter's actual method is
different in kind: starting from the reported complaint itself and
using scoping questions (one user or many, one destination or
everywhere, etc.) to narrow down which single layer is worth checking -
never intending to review every layer at all. The direction of the
investigation itself is reversed, not merely shortened.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the real reason for each approach's own direction (
building something new vs. diagnosing something that mostly already
works), and correctly explains that the support approach doesn't skip
steps of the bottom-up method - it uses an entirely different starting
point and narrowing process, which is why the chapter treats it as a
genuinely different job rather than a quicker version of the same one.