So what I'm doing in this ad hoc ansible command is saying
Ansible target the control host group in my inventory and run
the win_ping connectivity test module.
And this is exactly the result that we want to see,
that the connection test was success and the response to the ping was pong.
So that's just an Ansible thing.
Now one thing I want to say about this technique is
we could also use ad hoc commands, although it's not the ansible command.
It's ansible playbook when you want to invoke a playbook.
But truly ad hoc commands are like what you're doing here,
ansible host or host group, and then you're invoking a module of some type.
Now, win_ping is an example of a self‑contained utility module.
In most cases, the modules are builder modules,
and you use them, the parts and pieces within them,
you use them in your playbooks, you see.
So it's a question of flexibility.
And speaking of flexibility,
we could adjust that command with ‑i to point to a totally different
inventory as far as that goes because maybe we've got need for Ctrl+Z
and Ctrl+Z is not in my default inventory, so I can override that.
And you can just add on here.
So again,
it's a question of looking up ansible ‑‑help and starting to dive in and
read it because it's super useful documentation in Ansible.