- A
Use the rule 'Launch Sensitive Mount'
Why wrong: Option A is incorrect. 'Launch Sensitive Mount' is a Falco rule for detecting sensitive volume mounts, not shell spawning.
- B
Check if proc.name is 'bash' and container is true
Option B is correct because checking proc.name='bash' with container=true directly identifies a shell process starting inside a container.
- C
Use the macro 'spawned_process' combined with a container filter
Option C is correct because the 'spawned_process' macro catches new process events, and combining it with a container filter detects shell spawns within containers.
- D
Check if the process's parent is 'sshd'
Why wrong: Option D is incorrect. Checking if the parent is 'sshd' detects SSH connections, not generic shell spawns. A shell can be spawned by many processes, not just sshd.
- E
Check if evt.type is 'execve' and fd.name contains 'bash'
Why wrong: Option E is incorrect. evt.type='execve' is correct, but fd.name refers to file descriptors (e.g., opened files), not process names. proc.name should be used instead.
Falco Rules to Detect Shell Spawning Inside Containers
This CKS practice question tests your understanding of monitoring, logging and runtime security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: proc.name. 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.
Which TWO of the following are valid methods to detect a container spawning a shell (e.g., /bin/bash) using Falco? (Select two.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Check if proc.name is 'bash' and container is true
Option B is correct because Falco can detect a shell spawning by checking if the process name (proc.name) is 'bash' and the container context is true. This directly identifies when a shell process is started inside a container, which is a common indicator of unauthorized access or malicious activity. Option C is correct because Falco's 'spawned_process' macro filters for new process creation events, and combining it with a container filter (e.g., 'container.id != host') allows detection of any shell spawned within a container.
Key principle: proc.name
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the rule 'Launch Sensitive Mount'
Why it's wrong here
Option A is incorrect. 'Launch Sensitive Mount' is a Falco rule for detecting sensitive volume mounts, not shell spawning.
- ✓
Check if proc.name is 'bash' and container is true
Why this is correct
Option B is correct because checking proc.name='bash' with container=true directly identifies a shell process starting inside a container.
Related concept
proc.name
- ✓
Use the macro 'spawned_process' combined with a container filter
Why this is correct
Option C is correct because the 'spawned_process' macro catches new process events, and combining it with a container filter detects shell spawns within containers.
Related concept
proc.name
- ✗
Check if the process's parent is 'sshd'
Why it's wrong here
Option D is incorrect. Checking if the parent is 'sshd' detects SSH connections, not generic shell spawns. A shell can be spawned by many processes, not just sshd.
- ✗
Check if evt.type is 'execve' and fd.name contains 'bash'
Why it's wrong here
Option E is incorrect. evt.type='execve' is correct, but fd.name refers to file descriptors (e.g., opened files), not process names. proc.name should be used instead.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Falco often tests the distinction between process name fields (proc.name) and file descriptor fields (fd.name), leading candidates to incorrectly select option E, which uses fd.name instead of proc.name for process detection.
Detailed technical explanation
How to think about this question
Falco operates by hooking into system calls via kernel modules or eBPF; for process detection, it uses the 'execve' event and inspects the 'proc.name' field, which contains the executable name (e.g., 'bash', 'sh'). The 'spawned_process' macro is defined as 'evt.type = execve and evt.dir = <' to capture new process creations, and combining it with a container filter ensures only containerized processes are flagged. In real-world scenarios, attackers often spawn a shell inside a container after exploiting a vulnerability, and Falco's default rules like 'Terminal shell in container' use this exact logic to alert.
KKey Concepts to Remember
- proc.name
- spawned_process
- container filter
TExam Day Tips
- 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
proc.name
Real-world example
How this comes up in practice
A practitioner preparing for the CKS exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. proc.name Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Review proc.name, then practise related CKS questions on the same topic to reinforce the concept.
- →
Monitoring, Logging and Runtime Security — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring, Logging and Runtime Security practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CKS question test?
Monitoring, Logging and Runtime Security — This question tests Monitoring, Logging and Runtime Security — proc.name.
What is the correct answer to this question?
The correct answer is: Check if proc.name is 'bash' and container is true — Option B is correct because Falco can detect a shell spawning by checking if the process name (proc.name) is 'bash' and the container context is true. This directly identifies when a shell process is started inside a container, which is a common indicator of unauthorized access or malicious activity. Option C is correct because Falco's 'spawned_process' macro filters for new process creation events, and combining it with a container filter (e.g., 'container.id != host') allows detection of any shell spawned within a container.
What should I do if I get this CKS question wrong?
Review proc.name, then practise related CKS questions on the same topic to reinforce the concept.
What is the key concept behind this question?
proc.name
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 →
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jul 4, 2026
This CKS practice question is part of Courseiva's free CNCF 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 CKS 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.