- A
clone
Why wrong: clone is used to create a new process, but execve is the actual execution of a different binary.
- B
open
Why wrong: open is used for file opening, not process execution.
- C
read
Why wrong: read is used for reading file content, not execution.
- D
execve
execve is the syscall used to execute a new program, such as a shell.
Question 639 of 997
Falco Syscall for Shell Detection: execve
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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 is triggered when a shell is spawned inside a container. Which syscall is typically used to detect shell execution?
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
✓
execve
Falco detects shell execution by monitoring the `execve` syscall, which is the standard Linux system call used to execute a new program. When a shell like `/bin/bash` or `/sh` is spawned inside a container, the kernel invokes `execve` to replace the current process image with the shell binary. Falco's rule engine matches this syscall against its default rule set (e.g., `run_shell_untrusted`) to trigger an alert.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
clone
Why it's wrong here
clone is used to create a new process, but execve is the actual execution of a different binary.
- ✗
open
Why it's wrong here
open is used for file opening, not process execution.
- ✗
read
Why it's wrong here
read is used for reading file content, not execution.
- ✓
execve
Why this is correct
execve is the syscall used to execute a new program, such as a shell.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates often mistakenly think that shell execution is detected via process creation syscalls like `clone` or `fork`. However, Falco specifically monitors the `execve` syscall because that is the system call that actually loads the shell binary into memory. In the CKS exam, understanding this distinction is crucial for writing Falco rules.
Detailed technical explanation
How to think about this question
Under the hood, Falco uses kernel eBPF probes or a kernel module to intercept syscalls at the system call table. The `execve` syscall is the only way to load and execute a new binary in Linux (including shells), making it the definitive signal for process execution. In a real-world scenario, an attacker might use a reverse shell payload that calls `execve` to run `/bin/sh`, which Falco catches even if the shell is launched from a compromised application process.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: execve — Falco detects shell execution by monitoring the `execve` syscall, which is the standard Linux system call used to execute a new program. When a shell like `/bin/bash` or `/sh` is spawned inside a container, the kernel invokes `execve` to replace the current process image with the shell binary. Falco's rule engine matches this syscall against its default rule set (e.g., `run_shell_untrusted`) to trigger an alert.
What should I do if I get this CKS question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Same concept, more angles
1 more ways this is tested on CKS
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. You are investigating a security incident where a container ran a shell inside a pod. Which Falco rule condition would trigger on a shell spawned in a container?
medium- A.evt.type=clone and proc.name = 'shell'
- B.evt.type=execve and proc.name contains 'sh'
- ✓ C.proc.name in (sh, bash)
- D.container.id != host and proc.name = shell
Why C: Falco rules use syscalls and process names to detect events. The condition 'proc.name in (sh, bash)' correctly matches processes named 'sh' or 'bash', which are common shells spawned in containers. Option A is incorrect because 'clone' is not the typical syscall for shell execution (execve is used). Option B is incorrect because 'proc.name contains sh' would match any process with 'sh' in its name (e.g., 'sshd'), leading to false positives. Option D is incorrect because 'container.id != host' is unnecessary and 'proc.name = shell' does not match typical shell names like sh or bash.
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.