Exercise 1: Deleting a Dashboard Doesn't Delete the Data — Possible Solution
====================================================================

Explanation:

Grafana itself never stores metrics data -- it's purely a
query-and-render layer sitting on top of one or more data sources.
Every value a panel displays is fetched, live, from wherever it
actually lives -- Prometheus, in this course's case, which holds all
the real time-series data in its own local storage per obs1-3.
Deleting a dashboard only deletes Grafana's own record of which
panels existed, which queries they ran, and how they were laid out on
screen -- it's deleting a saved VIEW into the data, not the data
itself.

This reveals that Grafana and Prometheus have a genuinely one-way,
loosely coupled relationship: Grafana depends entirely on Prometheus
to have any data to show, but Prometheus has no dependency on Grafana
at all and keeps collecting and storing metrics regardless of whether
any dashboard ever queries them. If Grafana itself were lost entirely
-- the whole application, every dashboard, every configured data
source -- nothing about the underlying metrics history in Prometheus
would be affected; a new Grafana instance could be pointed at the
same Prometheus data source and, once dashboards were rebuilt or
re-provisioned, would show exactly the same historical data as
before.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains the deletion behavior by tracing exactly what a
dashboard actually is (a saved view/query definition) versus what a
data source actually holds (the real data), then generalizes that
distinction into the one-way dependency relationship between Grafana
and Prometheus the chapter's own opening section describes.