Explanation
Using either EXPOSE or -publish to access the container on the bridge network will not accomplish the goal of creating a container that is reachable from its host's network. EXPOSE is a way of documenting which ports a container listens on, but it does not open any ports to the host1. -publish (or -p) is a way of mapping a host port to a container port, but it does not change the network mode of the container2. By default, Docker containers use the bridge network, which isolates them from the host network3. To create a container that is reachable from its host's network, you need to use the --network host option when running the container4. This will make the container share the host's network stack and have the same IP address as the host4. References:
* 1: Difference Between "expose" and "publish" in Docker | Baeldung on Ops
* 2: Deploy services to a swarm | Docker Docs
* 3: Bridge network | Docker Docs
* 4: Host network | Docker Docs

Explanation
A node is a physical or virtual machine running Docker Engine in swarm mode1. A node can be either a manager or a worker, depending on its role in the cluster1. A physical machine participating in the swarm is a node, regardless of its role or availability2. References:
* How nodes work | Docker Docs
* Manage nodes in a swarm | Docker Docs

Explanation
= Creating a collection for each application is not a way to accomplish this. A collection is a term used by Ansible to describe a package of related content that can be used to automate the management of Kubernetes resources1. A collection is not a native Kubernetes concept and does not group resources together within the cluster. To group Kubernetes-specific resources, such as secrets, for each application, you need to use namespaces. A namespace is a logical partition of the cluster that allows you to isolate resources and apply policies to them2. You can create a namespace for each application and store the secrets and other resources in that namespace. This way, you can prevent conflicts and limit access to the resources of each application. To create a namespace, you can use the kubectl create namespace command or a yaml file2. To create a secret within a namespace, you can use the kubectl create secret command with the --namespace option or a yaml file with the metadata.namespace field3. References:
* Kubernetes Collection for Ansible - GitHub
* Namespaces | Kubernetes
* Secrets | Kubernetes
* Managing Secrets using kubectl | Kubernetes

Explanation
The command docker inspect nodes will not list all nodes in a swarm cluster from the command line. This is because docker inspect requires one or more names or IDs of the objects to inspect1. To list all nodes in a swarm cluster, you need to use the command docker node ls2, which will display information such as node ID, hostname, status, availability, and role3. References:
* docker inspect | Docker Docs
* docker node ls | Docker Docs
* How to list nodes in a Docker swarm cluster