Will this action upgrade Docker Engine CE to Docker Engine EE?
Solution: Manually download the 'docker-ee' package
Answer : B
= Manually downloading the 'docker-ee' package will not upgrade Docker Engine CE to Docker Engine EE. Docker Engine CE and Docker Engine EE are two different products with different installation methods and features.Docker Engine CE is a free and open source containerization platform, while Docker Engine EE is a subscription-based enterprise-grade platform that offers additional features such as security scanning, certified plugins, and support12.To upgrade from Docker Engine CE to Docker Engine EE, you need to uninstall Docker Engine CE and install Docker Engine EE following the official documentation3.Reference:
What is the exact difference between Docker EE (Enterprise Edition), Docker CE (Community Edition) and Docker (Custom Support) - Stack Overflow
Difference between Docker Community Edition (CE) vs Docker Enterprise Edition (EE) in 2020
Install Docker Engine | Docker Docs
An application image runs in multiple environments, with each environment using different certificates and ports.
Is this a way to provision configuration to containers at runtime?
Solution: Provision a Docker config object for each environment.
Answer : A
= Provisioning a Docker config object for each environment is a way to provision configuration to containers at runtime. Docker configs allow services to adapt their behaviour without the need to rebuild a Docker image. Services can only access configs when explicitly granted by a configs attribute within the services top-level element.As with volumes, configs are mounted as files into a service's container's filesystem1.Docker configs are supported on both Linux and Windows services2.Reference:Docker Documentation,Configs top-level element
What is the difference between the ADD and COPY Dockerfile instructions? (Select two.)
Answer : A, E
You want to create a container that is reachable from its host's network. Does this action accomplish this?
Solution:Use either EXPOSE or --publish to access the containers on the bridge network
Answer : B
The answer depends on whether you want to access the container from the host's network or from other containers on the same network. EXPOSE and --publish have different effects on the container's port visibility.Reference:Docker run reference,Dockerfile reference,Docker networking overview
You add a new user to the engineering organization in DTR.
Will this action grant them read/write access to the engineering/api repository?
Solution: Add the user directly to the list of users with read/write access under the repository's Permissions tab.
Answer : B
Adding a new user to the engineering organization in DTR will not automatically grant them read/write access to the engineering/api repository. This is because the repository permissions are not inherited from the organization level, but are configured separately for each repository. Therefore, to grant read/write access to the new user, you need to add them directly to the list of users with read/write access under the repository's Permissions tab.Reference:
Docker Trusted Registry - Manage access to repositories
Docker Certified Associate (DCA) Study Guide - Domain 3: Image Creation, Management, and Registry
https://docs.docker.com/ee/dtr/user/manage-repos/#manage-access-to-repositories
https://success.docker.com/certification/study-guides/dca-study-guide#domain-3-image-creation-management-and-registry-20-of-exam
In the context of a swarm mode cluster, does this describe a node?
Solution: a physical machine participating in the swarm
Answer : A
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.Reference:
How nodes work | Docker Docs
Manage nodes in a swarm | Docker Docs
During development of an application meant to be orchestrated by Kubernetes, you want to mount the /data directory on your laptop into a container.
Will this strategy successfully accomplish this?
Solution: Create a PersistentVolume with storageciass: "" and hostPath: /data, and a persistentVolumeClaim requesting this PV. Then use that PVC to populate a volume in a pod
Answer : B
= The strategy of creating a PersistentVolume with hostPath and a PersistentVolumeClaim to mount the /data directory on your laptop into a container will not work, because hostPath volumes are only suitable for single node testing or development. They are not portable across nodes and do not support dynamic provisioning. If you want to mount a local directory from your laptop into a Kubernetes pod, you need to use a different type of volume, such as NFS, hostPath CSI, or minikube. Alternatively, you can copy the files from your laptop to the container using kubectl cp command.Reference:
Volumes | Kubernetes
Configure a Pod to Use a PersistentVolume for Storage | Kubernetes
Mount a local directory to kubernetes pod - Stack Overflow
Kubernetes share a directory from your local system to kubernetes container - Stack Overflow
How to Mount a Host Directory Into a Docker Container