New Release DCA Docker Certified Associate Questions

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. References:

• Docker Trusted Registry - Manage access to repositories
• Docker Certified Associate (DCA) Study Guide - Domain 3: Image Creation, Management, and Registry

 = The command kubectl get pods --all-namespaces -label env=development is not valid because it has a syntax error. The correct syntax for listing pods with a specific label is kubectl get pods --all-namespaces --selector label=value or kubectl get pods --all-namespaces -l label=value. The error in the command is:

• The option flag for specifying the label selector is --selector or -l, not -label. For example, -label env=development should be --selector env=development or -l env=development.

The correct command for listing all the pods in the cluster that are labeled as env: development is:

kubectl get pods --all-namespaces --selector env=development

This command will display the name, status, restarts, and age of the pods that have the label env: development in all namespaces.

References: : Labels | Kube by Example : kubectl Cheat Sheet | Kubernetes

= Authentication is not a type of Linux kernel namespace that provides container isolation. Namespaces are a feature of the Linux kernel that partitions kernel resources such that one set of processes sees one set of resources and another set of processes sees a different set of resources. Docker uses six different namespaces to isolate containers from the host and from each other: PID, USER, UTS, IPC, MNT, and NET12. Authentication is not one of them. Authentication is a process of verifying the identity of a user or a system, which is usually done by using credentials such as passwords, tokens, or certificates. Authentication does not directly affect the isolation of containers, although it can be used to control access to them. References:

• Docker security | Docker Docs
• Securing Docker Containers with Linux Kernel Features | Infosec

= Setting and exporting the IGNORE_TLS environment variable on the command line is not a way to configure the Docker engine to use a registry without a trusted TLS certificate. This environment variable is not recognized by Docker and has no effect on the TLS verification process1. To use a registry without a trusted TLS certificate, you need to either add the certificate to the system or Docker-specific trust store, or configure the Docker daemon to allow insecure registries23. References:

• Environment variables | Docker Docs
• Verify repository client with certificates | Docker Docs
• Test an insecure registry | Docker Docs