DCA Exam Dumps : Docker Certified Associate (DCA) Exam

The set of commands docker container inspect and docker port cannot identify the published port(s) for a container. The docker container inspect command returns low-level information on a container, such as its ID, name, state, network settings, mounts, etc1. However, it does not show the port mappings between the container and the host2. The docker port command lists the port mappings or a specific mapping for a container, but it requires the container name or ID as an argument3. Therefore, to identify the published port(s) for a container, you need to use both commands together, such as docker port $(docker container inspect -f '{{.Name}}' CONTAINER)4. References:

docker container inspect | Docker Docs

How to inspect a running Docker container - Stack Overflow

docker port | Docker Docs

List port for Docker container using command line - Stack Overflow

= The conditions are not sufficient for Kubernetes to dynamically provision a persistentVolume, because they are missing a StorageClass object. A StorageClass object defines which provisioner should be used and what parameters should be passed to that provisioner when dynamic provisioning is invoked. A persistentVolumeClaim must specify the name of a StorageClass in its storageClassName field to request a dynamically provisioned persistentVolume. Without a StorageClass, Kubernetes cannot determine how to provision the storage for the claim. References:

Dynamic Volume Provisioning | Kubernetes

Persistent volumes and dynamic provisioning | Google Kubernetes Engine …

Dynamic Provisioning and Storage Classes in Kubernetes or Dynamic Provisioning and Storage Classes in Kubernetes

Label constraints can be used to schedule containers to meet the security policy requirements. Label constraints allow you to specify which nodes a service can run on based on the labels assigned to the nodes1. For example, you can label the nodes that are intended for development with env=dev and the nodes that are intended for production with env=prod. Then, you can use the --constraint flag when creating a service to restrict it to run only on nodes with a certain label value. For example, docker service create --name dev-app --constraint 'node.labels.env == dev' ... will create a service that runs only on development nodes2. Similarly, docker service create --name prod-app --constraint 'node.labels.env == prod' ... will create a service that runsonly on production nodes3. This way, you can ensure that development and production containers are running on separate nodes in a given Swarm cluster. References:

Add labels to swarm nodes

Using placement constraints with Docker Swarm

Multiple label placement constraints in docker swarm