Logging Quiz

Note that this quiz is broader than logging alone — it covers cluster observability and the troubleshooting commands that go with it, which is how the topic tends to come up in practice and in the exam.

What this quiz covers

• kubectl logs — targeting a specific container inside a multi-container pod
• kubectl describe — reading events when a pod won’t start, which is usually where the answer is
• Fluentd as a DaemonSet — why node-level log collection uses that pattern
• Logging drivers — container runtime configuration for downstream collectors
• Prometheus and Grafana — metrics collection and visualisation
• kube-proxy — network rules on each node
• Cross-node pod connectivity — where to start when traffic doesn’t flow
• API server — its role and how it’s made highly available

Common mistakes

• Going to kubectl logs for a pod stuck in Pending — there are no logs yet; describe has the events
• Assuming a DaemonSet lands on every node regardless of taints
• Reading container logs when the failure is at the runtime or scheduling layer

Twenty questions below, each with an explanation.

Time's up