300-910 Question #120: Real Exam Question with Answer & Explanation

Question

Which Kubernetes cluster logging architecture uses a single agent per Kubernetes node to aggregate and stream stdout and stderr logs from containers to a backend log collection service?

Options

• Aship logs
• Bsidecar container with a logging agent
• Cnode-level logging agent
• Dsidecar container

Explanation

Node-level logging in Kubernetes uses a single logging agent deployed as a DaemonSet on each node to collect and forward all container stdout and stderr logs to a centralized backend.

Common mistakes.

• A. Ship logs is not a recognized or defined Kubernetes logging architecture pattern in Kubernetes documentation and does not correspond to a standard deployment approach.
• B. A sidecar container with a logging agent runs a dedicated logging container alongside the application container within the same pod, which is a per-pod pattern rather than a single-agent-per-node aggregation architecture.
• D. A sidecar container alone (without a dedicated logging agent) is a pattern where a second container in the pod re-streams the application's log files, but this does not use a single agent per node and does not aggregate logs across all pods on the node.

Concept tested. Kubernetes node-level logging agent DaemonSet architecture

Reference. https://kubernetes.io/docs/concepts/cluster-administration/logging/#node-level-logging-agent

No community discussion yet for this question.