Exercise 3: What Ansible's service Module Does With state:started + enabled:true — Possible Solution
====================================================================

Explanation:

Per the chapter's own explanation of what Ansible's service module
wraps underneath, this single Ansible task actually corresponds to
TWO separate systemctl actions being performed, matching the two
genuinely different axes this chapter's own compare-table
distinguishes:

1. state: started maps directly to systemctl start nginx -- with
   Ansible's own idempotency check (per ansible1-4's own material)
   first confirming, via the equivalent of systemctl status, whether
   nginx is already running before deciding whether start actually
   needs to be called at all. This controls whether nginx is running
   RIGHT NOW.

2. enabled: true maps directly to systemctl enable nginx -- creating
   the boot-time symlink tied to nginx's own [Install]/WantedBy= line,
   so that nginx will also start automatically at the NEXT reboot.
   This is a completely separate action from the first, controlling a
   different axis entirely (automatic-at-boot vs. running-right-now),
   exactly the distinction the chapter is explicit that "enabling a
   service does NOT start it immediately, and starting a service does
   NOT enable it."

Combined, this one Ansible task is really asking systemd to do both
things together -- ensure nginx is running now, AND ensure it will
keep running automatically after every future reboot -- which is
precisely the same combined outcome systemctl enable --now nginx
(this chapter's own tip-box) would produce if run directly, just
expressed through Ansible's own two separate parameters instead of
one combined flag.

WHY THIS WORKS AS AN ANSWER
------------------------------
This separates the two parameters (state: started and enabled: true)
into their own distinct systemctl equivalents, explicitly naming which
axis each one controls per the chapter's own compare-table, and
connects the combined effect back to the chapter's own enable --now
shortcut rather than treating the two parameters as one action.