You want to provide a configuration file to a container at runtime. Does this set of Kubernetes tools and steps accomplish this?
Solution: Turn the configuration file into a configMap object, use it to populate a volume associated with the pod, and mount that file from the volume to the appropriate container and path.

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

Which of the following commands starts a Redis container and configures it to always restart unless it is
explicitly stopped or Docker is restarted?

• A.'docker run -d --restart unless-stopped redis'
• B.'docker run -d --restart omit-stopped redis'
• C.'docker run -d --failure omit-stopped redis'
• D.'docker run -d --restart-policy unless-stopped redis'

Comment: *

Name: *

Email: *

Verification: *

Is this a Linux kernel namespace that is disabled by default and must be enabled at Docker engine runtime to be used?
Solution: net

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

A container named "analytics" that stores results in a volume called "data" was created.
docker run -d --name=analytics -v data:/data app1
How are the results accessed in "data" with another container called "app2"?

• A.docker run -d --name=reports --mount=app1 app2
• B.docker run -d --name=reports --volume=app1 app2
• C.docker run -d --name=reports --volume=data app2
• D.docker run -d --name=reports --volumes-from=analytics app2

Comment: *

Name: *

Email: *

Verification: *

Does this command display all the pods in the cluster that are labeled as 'env: development'?
Solution: 'kubectl get pods --all-namespaces -I env=development'

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *