Exercise 1: Matching Capstone Pieces to Their Source Chapter — Possible Solution
====================================================================

(a) The database's Secret-mounted password.
    -> CHAPTER 7 (ConfigMaps & Secrets). Specifically the Secret
    material and the "mounting as a volume" consumption method --
    per Chapter 7, secrets are commonly mounted as files rather than
    environment variables specifically because file-based mounts are
    less prone to leaking than env vars, which is exactly why the
    capstone's database Secret is described as mounted rather than
    injected as an environment variable.

(b) The backend's liveness/readiness probes.
    -> CHAPTER 11 (Health Checks & Self-Healing). The backend's
    `/healthz` and `/ready` endpoints directly mirror Chapter 11's own
    concrete example of an application exposing two separate health
    endpoints with distinct meanings -- liveness for "should this be
    restarted," readiness for "should this currently receive traffic."

(c) The Ingress routing rules.
    -> CHAPTER 9 (Ingress & Exposing Services Externally). The
    `/api` vs. `/` path-based routing, both sharing the single
    `shop.example.com` host, is a direct application of Chapter 9's
    own path-based routing example -- one shared external entry point
    routing to multiple internal Services (Chapter 6) based on URL
    path.

WHY THIS WORKS AS AN ANSWER
------------------------------
Each answer identifies the specific chapter AND names the specific
concept from that chapter (mounted-Secret leak-resistance for (a),
the two-endpoint liveness/readiness pattern for (b), path-based
routing for (c)) that the capstone's own worked example directly
reused, rather than just naming a chapter number without connecting it
back to the actual concept being applied.