Exercise 3: Explaining the Missing Production-HA Setup — Possible Solution
====================================================================

Honest answer:

This capstone's own scope note is explicit that a production-grade,
highly-available deployment of Prometheus, Loki, and Jaeger themselves
was deliberately left out -- not because it isn't important, but
because it's a genuinely separate concern from what an 11-chapter
course teaching the observability tooling itself can reasonably cover
in full. Running each of these tools as a single, non-replicated
instance is fine for learning how the pipeline fits together end to
end -- which is this capstone's actual goal -- but a real production
deployment would need its own dedicated attention: replicated
Prometheus instances (or a remote-write setup to something like
Thanos/Cortex/Mimir, which obs1-3 already named as out of scope for
this course specifically), a properly replicated Loki deployment, and
similar HA considerations for Jaeger's own storage backend. That's a
legitimately large topic in its own right -- closer to its own course
than a single capstone chapter's worth of material -- so it's named
directly as a genuine next step here, rather than silently glossed
over as if the capstone's own single-instance setup were already
production-ready.

WHY THIS WORKS AS AN ANSWER
------------------------------
This gives a direct, honest answer rather than deflecting, explicitly
citing the chapter's own scope note and obs1-3's earlier
out-of-scope statement about long-term storage, and explains why HA
deployment is a genuinely separate, larger topic rather than an
oversight.