Challenge 3: Three Different Capstone Shapes — Solution Walkthrough

Summary:

Web Servers Fundamentals' own capstone applied a decision framework
across three different named scenarios, since that course was
comparative — choosing between Apache, Nginx, and IIS. Nginx In
Depth's own capstone instead built one single, cohesive production
configuration, since that course was a single-technology deep dive
with nothing left to compare. This course's own capstone takes a third
shape again: a step-by-step narrative session — a bug report, followed
through to a committed fix — because this course teaches a workflow of
tools used together in sequence, not a static configuration or a
choice between alternatives.

Why this particular shape fits a debugging-workflow course:

A real debugging session genuinely has a natural temporal order —
confirm the environment is sound, rule out simpler explanations
first, investigate deeper, verify broadly, clean up, then commit —
and this capstone's own step-by-step shape lets each earlier chapter's
tool appear exactly where it would naturally get used in a real
investigation, rather than being demonstrated in isolation. A static
config or a multi-scenario comparison wouldn't capture that natural
sequencing the way a narrative walkthrough does.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the relationship between all three capstone
shapes across this Web Servers/Nginx/Android Studio sequence is
understood as a deliberate match between each course's own actual
teaching goal — comparison, deep-dive configuration, or workflow
sequencing — and the capstone format best suited to demonstrating it.