- A
%pod.name
Why wrong: %pod.name is not a valid Falco output field. The correct field for Kubernetes pod name is %k8s.pod.name.
- B
%fd.name
Why wrong: %fd.name is not a valid Falco output field; it is used in rule conditions for file descriptors but not in the output format string.
- C
%k8s.ns
Why wrong: %k8s.ns is not a valid Falco output field; the correct field is %k8s.ns.name for namespace.
- D
%evt.type
%evt.type is a valid Falco output field that refers to the event type (e.g., 'open', 'execve', 'connect').
- E
%proc.name
%proc.name is a valid Falco output field that refers to the process name.
Question 465 of 997
Valid Falco Output Fields — %evt.type and %proc.name
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.
Which TWO of the following are valid Falco output fields?
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
✓
%evt.type
Option D is correct because `%evt.type` is a valid Falco output field that refers to the event type (e.g., 'open', 'execve', 'connect'). Falco uses this field in its rule conditions and output format strings to identify the specific system call or event that triggered the alert. It is a core field defined in the Falco event schema.
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.
- ✗
%pod.name
Why it's wrong here
%pod.name is not a valid Falco output field. The correct field for Kubernetes pod name is %k8s.pod.name.
- ✗
%fd.name
Why it's wrong here
%fd.name is not a valid Falco output field; it is used in rule conditions for file descriptors but not in the output format string.
- ✗
%k8s.ns
Why it's wrong here
%k8s.ns is not a valid Falco output field; the correct field is %k8s.ns.name for namespace.
- ✓
%evt.type
Why this is correct
%evt.type is a valid Falco output field that refers to the event type (e.g., 'open', 'execve', 'connect').
Related concept
Read the scenario before looking for a memorised answer.
- ✓
%proc.name
Why this is correct
%proc.name is a valid Falco output field that refers to the process name.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
In the CKS exam, candidates often confuse Kubernetes-related fields (like `%k8s.ns` or `%pod.name`) with the correct field names (e.g., `%k8s.ns.name` and `%k8s.pod.name`), or they assume `%fd.name` is a standard output field when it is actually used in rule conditions but not typically in the output format string.
Trap categories for this question
Command / output trap
%pod.name is not a valid Falco output field. The correct field for Kubernetes pod name is %k8s.pod.name.
Detailed technical explanation
How to think about this question
Falco output fields are defined in the Falco rule language and are used in the `output` property of rules to format alert messages. The `%evt.type` field returns the event type string (e.g., 'open', 'execve', 'connect') and is essential for filtering specific system calls. `%proc.name` returns the process name that triggered the event. Under the hood, Falco uses a gRPC API and a shared library (libsinsp) to extract these fields from kernel events via eBPF or kernel modules. In a real-world scenario, a rule like `output: "File opened (user=%user.name command=%proc.cmdline file=%fd.name evt_type=%evt.type)"` helps security teams quickly identify suspicious file access patterns.
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: %evt.type — Option D is correct because `%evt.type` is a valid Falco output field that refers to the event type (e.g., 'open', 'execve', 'connect'). Falco uses this field in its rule conditions and output format strings to identify the specific system call or event that triggered the alert. It is a core field defined in the Falco event schema.
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 →
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.