Docker Updated DCA Exam Questions and Answers by montague

The provided Kubernetes NetworkPolicy YAML configuration indicates that the policy applies to pods with the labeltier: backendin thedefaultnamespace1.The ingress rule allows traffic from pods with the labeltier: api1.Therefore, a request issued from a pod bearing thetier: apilabel to a pod bearing thetier: backendlabel will not be blocked by this networkPolicy1.This is because the networkPolicy explicitly allows ingress from pods with thetier: apilabel1. For more information on Kubernetes Network

The statement does not describe a node in the context of a swarm mode cluster. A node is a physical or virtual machine running Docker Engine 1.12 or later in swarm mode1. An instance of the Docker CLI connected to the swarm is not a node, but a client that can interact with the swarm through the Docker API2. The Docker CLI can be used to create a swarm, join nodes to a swarm, deploy services to a swarm, and manage swarm behavior3. References: How nodes work), Docker CLI), Swarm mode overview)

   = Using network connect to access the container on the bridge network does not accomplish creating a container that is reachable from its host’s network. The network connect command connects a container to an existing network, but it does not expose the container’s ports to the host1. The bridge network is the default network that Docker creates for containers, and it provides isolation from the host network2. To create a container that is reachable from its host’s network, you need to use the host network driver, which disables network isolation and uses the host’s network stack directly3. Alternatively, you can use the port mapping feature to publish specific ports of the container to the host4. References:

docker network connect | Docker Docs

Bridge network driver | Docker Docs

Host network driver | Docker Docs

Publish ports on the host | Docker Docs