Exercise 2: The Four Top-Level YAML Fields, Explained — Possible Solution
====================================================================

apiVersion: specifies WHICH VERSION of the Kubernetes API this
resource type belongs to. Different resource kinds (and sometimes
different versions of the same kind) are grouped under different API
versions -- this field tells Kubernetes which API group/version to
interpret the rest of the manifest against.

kind: specifies WHAT TYPE of resource this manifest describes -- Pod,
Deployment, Service, and so on (per the chapter, more resource kinds
are introduced across later chapters). This determines which fields
are valid and expected inside `spec` below, since different resource
kinds have entirely different configuration shapes.

metadata: holds IDENTIFYING INFORMATION about this specific resource
-- most importantly its `name` (used to reference it later via
kubectl), and `labels` -- key-value tags that, per the chapter,
"later chapters use to connect resources together" (for example,
Chapter 6's Services selecting pods by label). Metadata is about
WHICH resource this is and how it's identified/organized, not about
its actual behavior.

spec: holds the ACTUAL DESIRED CONFIGURATION for the resource -- for
a Pod, this means things like which containers to run, which images
they use, and which ports they expose. This is the field that
actually determines what the resource DOES once created, as opposed
to metadata's role of identifying and labeling it.

Summary of the distinction: apiVersion and kind together tell
Kubernetes WHAT KIND OF THING this is and how to interpret it;
metadata tells Kubernetes WHICH SPECIFIC instance this is and how to
find/organize it; spec tells Kubernetes WHAT IT SHOULD ACTUALLY DO.

WHY THIS WORKS AS AN ANSWER
------------------------------
This assigns each field a distinct, non-overlapping responsibility
directly from the chapter's own explanation, and adds a one-line
summary distinguishing "what kind of thing" (apiVersion/kind) from
"which specific instance, identified how" (metadata) from "what it
actually does" (spec) -- the conceptual grouping that makes the four
fields easy to remember together rather than as four unrelated items.