Exercise 3: The Course's Most Recurring Idea — Possible Solution
====================================================================

The single idea that recurs most often across the entire course is the
DESIRED-STATE-VS-ACTUAL-STATE COMPARISON, first introduced in Chapter 1
as the property that makes Terraform declarative rather than
imperative, and then reappearing, in genuinely different forms, at
nearly every later chapter: Chapter 2's "No changes" output demonstrating
it concretely for the first time; Chapter 5's formal definition of state
as the record that makes the comparison possible at all; Chapter 5's own
three-way drift-detection comparison (configuration, state, and a real
infrastructure refresh); Chapter 6's locking, which exists specifically
to keep concurrent writes from corrupting that same comparison's
source of truth; and Chapter 9's import workflow, which is itself
nothing more than iterating against `plan` -- the exact comparison --
until configuration and reality finally agree.

Why understanding this deeply matters more than memorizing any
individual command: nearly every command in this course (`plan`,
`apply`, `import`, `state mv`, even `fmt`/`validate` as pre-checks
before a plan can be trusted) is really just a different interface onto
this one underlying mechanism -- computing or acting on a difference
between what's declared and what's real. A person who has memorized
`terraform apply` as "the command that makes things happen" without
understanding WHY it's safe to re-run repeatedly will be confused the
first time a plan does something unexpected (drift, a `count`/`for_each`
reordering surprise from Chapter 3, a workspace mix-up from Chapter 8).
A person who understands the underlying comparison can reason through
any of those situations from first principles, because they all reduce
to the same question: what does the desired state say, what does actual
state say, and why do they currently differ.

WHY THIS WORKS AS AN ANSWER
------------------------------
This names one specific, well-supported idea (not a vague "declarative
infrastructure is good") and traces it through concrete instances
spanning the whole course to justify calling it the most recurring
one, then explains the "why it matters more than syntax" question in
terms of transferring to genuinely new, unexpected situations -- the
actual reason deep conceptual understanding outlasts memorized
commands.