Exercise 1: Checking dbservers Are Reachable via the ping Module — Possible Solution
====================================================================

ansible dbservers -i inventory -m ping

Explanation:

This follows the chapter's own ad-hoc command structure exactly: the
target group ("dbservers" instead of "all"), the -i flag pointing at
the inventory file, and -m ping selecting the built-in ping module.

-- What ping actually confirms, beyond a raw ICMP ping --
--
-- A raw ICMP ping only confirms that a host responds to network
-- packets at all -- it says nothing about whether Ansible could
-- actually manage that host. Ansible's own ping module goes several
-- steps further: it establishes a real SSH connection using whatever
-- credentials/keys are configured, confirms that connection succeeds
-- (not just that the network path exists), and then executes a small
-- Python-based check on the remote host to confirm Python itself is
-- present and working there -- since Ansible modules are executed as
-- Python code on the managed host. A host could easily respond to a
-- raw ICMP ping while still being completely unmanageable by Ansible
-- -- SSH might be misconfigured, credentials might be wrong, or
-- Python might be missing -- none of which a plain ICMP ping would
-- ever reveal. Ansible's ping module is really confirming "can I
-- actually manage this host," not just "is this host alive on the
-- network."

WHY THIS WORKS AS AN ANSWER
------------------------------
This writes the correctly targeted ad-hoc command using the chapter's
own established syntax, then explains specifically what layers of
manageability (SSH connectivity, Python availability) the ping module
verifies that a raw network-level ICMP ping never could.