- A
Any process spawning bash
Why wrong: This option is incorrect because the rule detects processes that are NOT bash, not processes spawning bash.
- B
All execve events except bash regardless of namespace
Correct. The rule catches all execve events where the process name is not bash, applying to all processes on the node irrespective of namespace (host or container).
- C
All execve events inside containers except bash
Why wrong: This option is incorrect because the rule does not limit detection to containers only; it applies to all processes on the host, including containers.
- D
All execve events on the host except bash
Why wrong: This option is misleading because it suggests the rule only applies to host-level processes, but Falco monitors all processes on the node, including those inside containers. Option B is more accurate.
Falco Rule for Monitoring execve System Calls Except Bash
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: falco event filtering. 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 Falco rule has priority: CRITICAL and condition: evt.type=execve and proc.name!=bash. What does this rule detect?
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
All execve events except bash regardless of namespace
The Falco rule `evt.type=execve and proc.name!=bash` with priority CRITICAL detects all `execve` system call events where the process name is NOT `bash`. Falco operates at the host level and monitors all system calls across the entire node, including those from containers. Since the rule does not include a container-specific filter (e.g., `container.id != host`), it applies to all processes regardless of namespace. Therefore, the rule detects all execve events except bash on the entire node—both host and container processes. Option B correctly captures this scope ('regardless of namespace').
Key principle: Falco event filtering
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Any process spawning bash
Why it's wrong here
This option is incorrect because the rule detects processes that are NOT bash, not processes spawning bash.
- ✓
All execve events except bash regardless of namespace
Why this is correct
Correct. The rule catches all execve events where the process name is not bash, applying to all processes on the node irrespective of namespace (host or container).
Related concept
Falco event filtering
- ✗
All execve events inside containers except bash
Why it's wrong here
This option is incorrect because the rule does not limit detection to containers only; it applies to all processes on the host, including containers.
- ✗
All execve events on the host except bash
Why it's wrong here
This option is misleading because it suggests the rule only applies to host-level processes, but Falco monitors all processes on the node, including those inside containers. Option B is more accurate.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Falco rules are container-scoped by default, but Falco operates at the host level and monitors all system calls unless explicitly filtered by container ID or namespace, so a rule without a container filter applies to the entire host.
Detailed technical explanation
How to think about this question
Falco uses kernel modules or eBPF to intercept system calls at the kernel level, and `evt.type=execve` matches the `execve` syscall (which is used to execute programs). The `proc.name` field refers to the process name as seen by the kernel, not the full path. In a real-world scenario, this rule would alert on any process execution that is not `bash`, such as `sh`, `python`, or `curl`, which is useful for detecting suspicious activity like reverse shells or unauthorized binaries, but it would miss attacks that use `bash` itself.
KKey Concepts to Remember
- Falco event filtering
- Host-level monitoring
- System calls (syscalls)
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
Falco event filtering
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. Falco event filtering 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 falco event filtering, 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 — Falco event filtering.
What is the correct answer to this question?
The correct answer is: All execve events except bash regardless of namespace — The Falco rule `evt.type=execve and proc.name!=bash` with priority CRITICAL detects all `execve` system call events where the process name is NOT `bash`. Falco operates at the host level and monitors all system calls across the entire node, including those from containers. Since the rule does not include a container-specific filter (e.g., `container.id != host`), it applies to all processes regardless of namespace. Therefore, the rule detects all execve events except bash on the entire node—both host and container processes. Option B correctly captures this scope ('regardless of namespace').
What should I do if I get this CKS question wrong?
Review falco event filtering, then practise related CKS questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Falco event filtering
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.