A platform team is using Fluentd to collect logs from their Kubernetes cluster and forward them to an external SIEM. They notice that some logs are missing, particularly from pods that restart frequently. What is the MOST likely cause?

Fluentd is not configured to read logs from the correct path on the node

The kubelet is not generating logs for restarting pods

The audit policy is not set to log pod restarts

The SIEM is not compatible with Fluentd's output format

Kubernetes and Cloud Native Security Associate (KCSA)

Domain 4Objective 3

Observability KCSA Practice Questions (Page 6)

Part of the Platform Security domain, which accounts for 16% of the KCSA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~6–10 in this domain), expect 1–1 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

6concepts

16%of the exam

Questions 26–28

26foundation · easy
Which type of observability data would best help you trace the path of a request that spans multiple microservices in a Kubernetes cluster?
Select an answer first
27expert · hard
A platform team is using Fluentd to collect logs from their Kubernetes cluster and forward them to an external SIEM. They notice that some logs are missing, particularly from pods that restart frequently. What is the MOST likely cause?
Select an answer first
28foundation · easy
Which Kubernetes component is responsible for collecting and storing logs from containers running on a node?
Select an answer first

Finished these 3 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to KCSA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “KCSA” is a trademark of its owner, used for identification only.

Observability KCSA Practice Questions (Page 6)

Questions 26–28

Which type of observability data would best help you trace the path of a request that spans multiple microservices in a Kubernetes cluster?

A platform team is using Fluentd to collect logs from their Kubernetes cluster and forward them to an external SIEM. They notice that some logs are missing, particularly from pods that restart frequently. What is the MOST likely cause?

Which Kubernetes component is responsible for collecting and storing logs from containers running on a node?

Keep studying — Platform Security