Challenge 3: Why This Capstone Mirrors Web Servers Fundamentals' Own Shape — Solution Walkthrough

Summary:

Web Servers Fundamentals' own capstone applied a five-question
decision framework across three different named scenarios, since that
course was fundamentally comparative — choosing between Apache,
Nginx, and IIS for a given job. This course's own capstone does the
identical thing structurally: it applies Chapter 8's own five-question
framework across five different scenarios, choosing between the full
roster of editors and IDEs this course assembled, rather than
comparing exactly three fixed options.

Why this differs from Nginx In Depth and Android Studio's own
capstones:

Nginx In Depth's own capstone built one single cohesive production
configuration, since that course was a single-technology deep dive
with nothing left to compare once Nginx itself was already chosen.
Android Studio's own capstone instead followed one realistic narrative
session end to end, since that course taught a workflow of tools used
together in sequence. Neither of those shapes fits a course whose
entire purpose is comparing several genuinely different tools against
each other.

Why the scenario-based shape fits this course specifically:

This course, like Web Servers Fundamentals, is comparative at its
core — matching different tools to different jobs, not building one
tool's own configuration or walking through one tool's own workflow.
A multi-scenario capstone is the natural fit for demonstrating that
kind of comparative decision-making in action.

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