Challenge 1: A Small Nonprofit's Static Site — Solution Walkthrough

Applying the framework:

  - Platform constraint: none stated — no existing Windows/.NET
    commitment, so IIS's own platform-fit advantage doesn't apply here.
  - Configuration model: the volunteer is comfortable editing config
    files directly, and there's only one person maintaining the site
    — no need for per-directory self-service overrides the way a
    multi-tenant shared host would need.
  - Concurrency profile: single low-traffic server, static content
    only — none of the high-concurrency, reverse-proxy-heavy demands
    that would push toward Nginx's own signature strengths.
  - Reverse-proxy/load-balancing needs: none — there's no backend
    application to proxy to at all.
  - Certificate management: not specified as a constraint either way.

Recommendation:

Either Apache or Nginx would serve this job well — this is a case
where the choice comes down to genuinely minor preference rather than
a clear-cut fit, since none of this scenario's constraints strongly
favor one over the other. If anything mildly tips the scale, Apache's
long-standing documentation and broad familiarity might suit a single
volunteer maintainer slightly better, but this is a soft preference,
not a strong recommendation the way Scenario 1-3 in this chapter were.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the decision framework is applied as an
actual set of questions — not simply pattern-matched to the chapter's
own three named scenarios — and that "the framework doesn't strongly
favor either" is itself a valid, honest conclusion when a scenario's
constraints genuinely don't point clearly one way.