The answer is container runtime events, Kubernetes audit logs, and network flow from the pod, as these three telemetry sources together provide the complete chain of events needed for root cause analysis of a container compromise. Container runtime events capture the unexpected shell execution and host filesystem mount, while Kubernetes audit logs reveal the API calls that initiated the pod, identifying the attacker’s initial access vector. Network flow logs from the pod then link the outbound connections to the unknown IP, showing lateral movement. On the CompTIA CySA+ CS0-003 exam, this tests your ability to correlate telemetry across layers—runtime, orchestration, and network—rather than relying on a single log source. A common trap is focusing only on network logs or container images, missing the audit trail of how the pod was created. Remember the mnemonic “RAN”: Runtime events, Audit logs, Network flows—three pillars for container compromise telemetry.
CS0-003 Security Operations Practice Question
This CS0-003 practice question tests your understanding of security operations. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. A key principle to apply: container runtime events detail process execution and system calls within a container.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A container workload unexpectedly starts a shell, mounts the host filesystem, and attempts outbound connections to an unknown IP. Which telemetry is MOST useful? In the root-cause analysis phase, Which finding would most directly explain the activity?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Container runtime events, Kubernetes audit logs, and network flow from the pod
Container runtime events (e.g., `docker events` or CRI-O logs) capture the unexpected shell execution and host filesystem mount. Kubernetes audit logs record the API calls that initiated the pod, revealing the attacker's initial access vector. Network flow logs from the pod (e.g., via Calico or Cilium) show the outbound connections to the unknown IP, linking the lateral movement to the compromised container. Together, these three telemetry sources provide the complete chain of events needed for root-cause analysis.
Key principle: Container runtime events detail process execution and system calls within a container.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Only user password age reports
Why it's wrong here
Password age does not explain container escape indicators.
✗
Only physical datacenter access logs
Why it's wrong here
Physical access logs are unrelated to pod-level activity.
✓
Container runtime events, Kubernetes audit logs, and network flow from the pod
Why this is correct
Runtime, orchestration, and network telemetry together show process execution, privilege context, and external communication.
Related concept
Container runtime events detail process execution and system calls within a container.
✗
Only monthly vulnerability scan summaries
Why it's wrong here
Scan summaries do not capture live runtime behaviour.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that a single log source (e.g., only network flows) is sufficient for root-cause analysis, when in reality a combination of container runtime, Kubernetes audit, and network telemetry is required to reconstruct the full attack chain.
Detailed technical explanation
How to think about this question
Under the hood, container runtime events are emitted via the CRI (Container Runtime Interface) and can be captured by tools like Falco or Sysdig, which use eBPF to monitor syscalls such as `clone()` (shell spawn) and `mount()`. Kubernetes audit logs are generated by the API server for every request, including `exec` commands that start a shell inside a pod. Network flow logs (e.g., NetFlow v9 or IPFIX) from the pod's CNI plugin record source/destination IPs and ports, enabling correlation with threat intelligence feeds for the unknown IP.
KKey Concepts to Remember
Container runtime events detail process execution and system calls within a container.
Kubernetes audit logs track API requests made to the Kubernetes control plane.
Network flow data from a pod records all ingress and egress network connections.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Container runtime events detail process execution and system calls within a container.
Real-world example
How this comes up in practice
A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CS0-003 question in full detail.
Review container runtime events detail process execution and system calls within a container., then practise related CS0-003 questions on the same topic to reinforce the concept.
Security Operations — This question tests Security Operations — Container runtime events detail process execution and system calls within a container..
What is the correct answer to this question?
The correct answer is: Container runtime events, Kubernetes audit logs, and network flow from the pod — Container runtime events (e.g., `docker events` or CRI-O logs) capture the unexpected shell execution and host filesystem mount. Kubernetes audit logs record the API calls that initiated the pod, revealing the attacker's initial access vector. Network flow logs from the pod (e.g., via Calico or Cilium) show the outbound connections to the unknown IP, linking the lateral movement to the compromised container. Together, these three telemetry sources provide the complete chain of events needed for root-cause analysis.
What should I do if I get this CS0-003 question wrong?
Review container runtime events detail process execution and system calls within a container., then practise related CS0-003 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Container runtime events detail process execution and system calls within a container.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A container workload unexpectedly starts a shell, mounts the host filesystem, and attempts outbound connections to an unknown IP. Which telemetry is MOST useful? In the containment trade-off phase, Which response balances containment with evidence preservation?
hard
A.Only physical datacenter access logs
✓ B.Container runtime events, Kubernetes audit logs, and network flow from the pod
C.Only monthly vulnerability scan summaries
D.Only user password age reports
Why B: Option B is correct because container runtime events (e.g., Docker/containerd exec logs) capture the unexpected shell launch, Kubernetes audit logs record the pod creation and mount operations, and network flow logs (e.g., NetFlow, eBPF-based tools) reveal the outbound connection to the unknown IP. Together, these provide the granular, real-time telemetry needed to detect and investigate the compromise, unlike static or coarse-grained logs.
Variation 2. A container workload unexpectedly starts a shell, mounts the host filesystem, and attempts outbound connections to an unknown IP. Which telemetry is MOST useful? In the detection engineering phase, Which detection or tuning approach would reduce noise without losing the signal?
hard
A.Only physical datacenter access logs
B.Only user password age reports
✓ C.Container runtime events, Kubernetes audit logs, and network flow from the pod
D.Only monthly vulnerability scan summaries
Why C: Container runtime events (e.g., from containerd or CRI-O) capture process spawns like a shell inside the container, Kubernetes audit logs record API calls that mount host paths (e.g., `hostPath` volumes), and network flow logs (e.g., from CNI plugins or eBPF) show outbound connections to unknown IPs. Together, these three telemetry sources provide the full kill chain—execution, privilege escalation, and exfiltration—making option C the most useful for detection engineering.
Variation 3. A container workload unexpectedly starts a shell, mounts the host filesystem, and attempts outbound connections to an unknown IP. Which telemetry is MOST useful? In the evidence source phase, Which evidence source best supports or refutes the detection?
hard
A.Only monthly vulnerability scan summaries
B.Only user password age reports
C.Only physical datacenter access logs
✓ D.Container runtime events, Kubernetes audit logs, and network flow from the pod
Why D: Container runtime events (e.g., from containerd or CRI-O) capture process spawns like an unexpected shell, Kubernetes audit logs record API calls that could indicate a compromised pod mounting the host filesystem, and network flow logs from the pod (e.g., via eBPF or Calico) reveal outbound connections to an unknown IP. Together, these three telemetry sources provide direct, real-time evidence of the three suspicious behaviors described, making them the most useful for detection and investigation.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CS0-003 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CS0-003 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.