- A
Default level Metadata with a rule that has 'level: Request' and 'namespaces: [kube-system]'
The rule for kube-system overrides the default for that namespace.
- B
Use two rules with 'level: Request' and 'level: Metadata' without default
Why wrong: Without a default, non-matching requests may not be logged at all.
- C
Default level Request with a rule for kube-system at Metadata
Why wrong: This would log all requests at Request, not Metadata.
- D
Default level Metadata with a rule for kube-system at Request
Why wrong: This option sets the correct default level (Metadata) and intends to add a rule for kube-system at Request level, but the description 'a rule for kube-system at Request' is ambiguous. In a valid audit policy rule, you must specify both the 'level' and the 'namespaces' field (e.g., 'namespaces: [kube-system]'). Without explicitly using the 'namespaces' field, the rule would apply to all requests, causing all requests to be logged at Request level, which is not the requirement. Therefore, this option is incorrect.
Kubernetes Audit Policy: Default Level and Namespace Override
This CKS practice question tests your understanding of monitoring, logging and runtime security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
You need to configure Kubernetes audit logging to log all requests at the Metadata level except for requests to the 'kube-system' namespace, which should be logged at Request level. How should you structure the audit policy?
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
Default level Metadata with a rule that has 'level: Request' and 'namespaces: [kube-system]'
Option A is correct because the audit policy in Kubernetes uses a top-down evaluation: the first matching rule applies. By setting a default level of Metadata, all requests are initially logged at Metadata level. Then, a specific rule for the 'kube-system' namespace with 'level: Request' overrides the default for that namespace, ensuring requests to kube-system are logged at Request level while all other requests remain at Metadata level.
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.
- ✓
Default level Metadata with a rule that has 'level: Request' and 'namespaces: [kube-system]'
Why this is correct
The rule for kube-system overrides the default for that namespace.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use two rules with 'level: Request' and 'level: Metadata' without default
Why it's wrong here
Without a default, non-matching requests may not be logged at all.
- ✗
Default level Request with a rule for kube-system at Metadata
Why it's wrong here
This would log all requests at Request, not Metadata.
- ✗
Default level Metadata with a rule for kube-system at Request
Why it's wrong here
This option sets the correct default level (Metadata) and intends to add a rule for kube-system at Request level, but the description 'a rule for kube-system at Request' is ambiguous. In a valid audit policy rule, you must specify both the 'level' and the 'namespaces' field (e.g., 'namespaces: [kube-system]'). Without explicitly using the 'namespaces' field, the rule would apply to all requests, causing all requests to be logged at Request level, which is not the requirement. Therefore, this option is incorrect.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The exam often tests the order of evaluation and the effect of default levels; the trap here is that candidates may think a rule for kube-system at Request level with a default of Metadata is incorrect because they assume the default applies after rules, but in reality the default is the fallback for requests that do not match any rule, so the rule for kube-system takes precedence.
Detailed technical explanation
How to think about this question
Kubernetes audit policy rules are evaluated in order, and the first matching rule determines the logging level. The 'omitStages' and 'omitResources' fields can further refine logging, but for namespace-based filtering, the 'namespaces' field in a rule matches the namespace of the request. Under the hood, the audit policy is a YAML file passed to the kube-apiserver via the '--audit-policy-file' flag, and the policy supports levels: None, Metadata, Request, and RequestResponse. A common real-world scenario is auditing sensitive operations in system namespaces while reducing verbosity for user namespaces to avoid log overload.
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: Default level Metadata with a rule that has 'level: Request' and 'namespaces: [kube-system]' — Option A is correct because the audit policy in Kubernetes uses a top-down evaluation: the first matching rule applies. By setting a default level of Metadata, all requests are initially logged at Metadata level. Then, a specific rule for the 'kube-system' namespace with 'level: Request' overrides the default for that namespace, ensuring requests to kube-system are logged at Request level while all other requests remain at Metadata level.
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.