Docker DCA Exam Dumps

Environment variables cannot be used to schedule containers to meet the security policy requirements.Environment variables are used to pass configuration data to the containers, not to control where they run1.To schedule containers to run on separate nodes in a Swarm cluster, you need to use node labels and service constraints23.Node labels are key-value pairs that you can assign to nodes to organize them into groups4. Service constraints are expressions that you can use to limit the nodes where a service can run based on the node labels. For example, you can label some nodes asenv=devand others asenv=prod, and then use the constraint--constraint node.labels.env==devor--constraint node.labels.env==prodwhen creating a service to ensure that it runs only on the nodes with the matching label.Reference:

1: Environment variables in Compose | Docker Docs

2: Deploy services to a swarm | Docker Docs

3: How to use Docker Swarm labels to deploy containers on specific nodes

4: Manage nodes in a swarm | Docker Docs

[5]: Swarm mode routing mesh | Docker Docs

[6]: Docker Swarm - How to set environment variables for tasks on various nodes

= Mounting the configuration file directly into the appropriate pod and container using the .spec.containers.configMounts key is not a valid way to provide a configuration file to a container at runtime.The .spec.containers.configMounts key does not exist in the Kubernetes API1.The correct way to provide a configuration file to a container at runtime is to use a ConfigMap2. A ConfigMap is a Kubernetes object that stores configuration data as key-value pairs. You can create a ConfigMap from a file, and then mount the ConfigMap as a volume into the pod and container.The configuration file will be available as a file in the specified mount path3.Alternatively, you can also use environment variables to pass configuration data to a container from a ConfigMap4.Reference:

PodSpec v1 core

Configure a Pod to Use a ConfigMap

Populate a Volume with data stored in a ConfigMap

Define Container Environment Variables Using ConfigMap Data

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 usethe --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.Reference:

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

= The action of using--linkto access the container on the bridge network doesnotaccomplish the goal of creating a container that is reachable from its host's network.The--linkoption allows you to connect containers that are running on the same network, but it doesnotexpose the container's ports to the host1.To create a container that is reachable from its host's network, you need to use the--network hostoption, which attaches the container to the host's network stack and makes it share the host's IP address2.Alternatively, you can use the--publishor-poption to map the container's ports to the host's ports3.

: :Legacy container links | Docker Documentation:Networking using the host network | Docker Documentation:docker run reference | Docker Documentation