QUESTION: 81

Your organization has a centralized logging solution, such as Splunk.

Will this configure a Docker container to export container logs to the logging solution?

Solution: docker logs <container-id>

Yes
No

Answer(s): B

Explanation:

: = The command docker logs <container-id> will not configure a Docker container to export container logs to the logging solution, such as Splunk. This command only displays the logs of a specific container in the standard output or a file, but does not send them to any external system. To export container logs to Splunk, you need to use the Docker Logger Drivers, which are plugins that provide logging capabilities for Docker containers. The Splunk logging driver sends container logs to HTTP Event Collector in Splunk Enterprise and Splunk Cloud. To use the Splunk logging driver for a specific container, you need to use the command-line flags --log-driver and --log-opt with docker run, and provide the Splunk token and URL as options. For example:

$ docker run --log-driver=splunk --log-opt splunk-token=VALUE --log-opt splunk-url=VALUE ...

Reference:

docker logs | Docker Documentation

Logging drivers | Docker Documentation

Splunk logging driver | Docker Documentation

Reveal Solution Next Question

QUESTION: 82

Your organization has a centralized logging solution, such as Splunk.

Will this configure a Docker container to export container logs to the logging solution?

Solution: Set the log-driver and log-oPt keys to values for the logging solution (Splunk) In the daemon.json file.

Yes
No

Answer(s): A

Explanation:

Setting the log-driver and log-opt keys to values for the logging solution (Splunk) in the daemon.json file will configure a Docker container to export container logs to the logging solution. This is because the Splunk logging driver sends container logs to the HTTP Event Collector in Splunk Enterprise and Splunk Cloud. To use the Splunk driver as the default logging driver, set the keys log-driver and log- opts to appropriate values in the daemon.json configuration file and restart Docker. To use the Splunk driver for a specific container, use the commandline flags --log-driver and log-opt with docker run. The Splunk logging driver supports various options, such as splunk-token, splunk-url, splunk- source, splunk-sourcetype, splunk-index, etc.

Reference:

Splunk logging driver | Docker Docs1

Reveal Solution Next Question

QUESTION: 83

A persistentVolumeClaim (PVC) is created with the specification storageClass: "", and size requirements that cannot be satisfied by any existing persistentVolume.

Is this an action Kubernetes takes in this situation?

Solution: The PVC remains unbound until a persistentVolume that matches all requirements of the PVC becomes available.

Yes
No

Answer(s): A

Explanation:

= A persistentVolumeClaim (PVC) is a request for storage by a user. It is similar to a Pod. Pods consume node resources and PVCs consume PV resources. A PVC can specify a storage class, which is a way of requesting a certain quality of service for the volume. If the storage class is empty, it means the PVC does not have any specific storage class requirements and can be bound to any PV that satisfies its size and access mode. However, if there is no existing PV that matches the PVC's requirements, the PVC remains unbound until a suitable PV becomes available. This can happen either by manual provisioning by an administrator or by dynamic provisioning using StorageClasses.

Reference:

Persistent Volumes | Kubernetes

Storage Classes | Kubernetes

Configure a Pod to Use a PersistentVolume for Storage | Kubernetes

Reveal Solution Next Question

QUESTION: 84

You created a new service named 'http' and discover it is not registering as healthy. Will this command enable you to view the list of historical tasks for this service?

Solution: 'docker service inspect http'

Yes
No

Answer(s): B

Explanation:

= The command `docker service inspect http' will display detailed information on the `http' service, such as its ID, name, mode, replicas, container spec, networks, ports, etc. However, it will not show the list of historical tasks for the service. To view the list of tasks, you need to use the command `docker service ps http', which will show the ID, name, image, node, desired state, current state, and error of each task.

Reference:

1: docker service inspect | Docker Docs

2: docker service ps | Docker Docs

Reveal Solution Next Question

Free DCA Exam Braindumps (page: 22)

QUESTION: 81

Explanation:

Reference:

QUESTION: 82

Explanation:

Reference:

QUESTION: 83

Explanation:

Reference:

QUESTION: 84

Explanation:

Reference:

DCA Exam Discussions & Posts