MENU
Which Cilium command should you execute to gather network-related troubleshooting information from your Kubernetes cluster?
The intended answer is D, but the option contains a source-bank typographical error. The valid command is cilium sysdump, not cilium sysduwp. Read literally, none of the four displayed commands exactly answers the question.
The Cilium CLI's sysdump operation gathers cluster-wide troubleshooting material, including Cilium configuration and endpoint state, agent and operator logs, Kubernetes workload information, routing and interface details, kernel messages, service state, policies, and selected eBPF-map output. This consolidated archive is the preferred diagnostic package when investigating Kubernetes networking or preparing a support report.
cilium status --verbose provides expanded health and deployment status, but it does not collect the comprehensive diagnostic archive requested. debuginfo is associated with the in-agent debug client---currently documented as cilium-dbg debuginfo---and produces useful local-agent API information; in Kubernetes environments it is already included as part of the system dump. cilium bugtool is not the current cluster-wide Cilium CLI command requested here.
For an exam-ready correction, option D should read cilium sysdump.
Official references
Cilium Troubleshooting and Sysdump
Study Guide topic: Cilium CLI troubleshooting, system dumps, and diagnostic collection.