- A
Add `DAC_OVERRIDE` capability
Why wrong: DAC_OVERRIDE bypasses file permission checks; not related to DNS or TCP sockets.
- B
Add `NET_RAW` capability
NET_RAW allows raw sockets; TCP DNS uses standard sockets, so this is unnecessary.
- C
Add `NET_ADMIN` capability
Why wrong: NET_ADMIN is for network administration tasks; creating TCP sockets does not require it.
- D
Add `NET_BIND_SERVICE` capability
Why wrong: NET_BIND_SERVICE allows binding to privileged ports; DNS client uses ephemeral ports, not required.
Question 616 of 997
Configuring Capabilities for TCP DNS Lookups — Kubernetes Security Context | Certified Kubernetes Security Specialist Explained
This CKS practice question tests your understanding of minimize microservice vulnerabilities. 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. A key principle to apply: dNS over TCP. 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 microservice container needs to perform DNS lookups using TCP rather than UDP. Which Kubernetes security context setting should be configured to allow this?
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
✓
Add `NET_RAW` capability
TCP DNS lookups use standard TCP sockets, not raw sockets. These are permitted by the default syscall policy, and no additional Linux capability is required. All listed capabilities are unnecessary, as the container already has the ability to create TCP sockets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add `DAC_OVERRIDE` capability
- ✓
Add `NET_RAW` capability
- ✗
Add `NET_ADMIN` capability
Why it's wrong here
NET_ADMIN is for network administration tasks; creating TCP sockets does not require it.
- ✗
Add `NET_BIND_SERVICE` capability
Why it's wrong here
NET_BIND_SERVICE allows binding to privileged ports; DNS client uses ephemeral ports, not required.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap is assuming that DNS over TCP requires a special capability. In reality, TCP socket creation is allowed by default, so no capability is needed. Candidates may incorrectly choose NET_RAW, thinking raw sockets are involved, or NET_ADMIN for network control.
Detailed technical explanation
How to think about this question
DNS over TCP is required when the response exceeds 512 bytes (or 4096 bytes with EDNS0) or for zone transfers (AXFR/IXFR). In Kubernetes, containers run with a default seccomp profile that may restrict raw socket creation; adding `NET_RAW` explicitly grants the `CAP_NET_RAW` capability, enabling the container to use `SOCK_RAW` sockets needed for TCP-based DNS. This is distinct from the `NET_ADMIN` capability, which controls routing and firewall changes via `iptables` or `ip` commands.
KKey Concepts to Remember
- DNS over TCP
- Linux capabilities
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
DNS over TCP
Real-world example
How this comes up in practice
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
Visual reference
What to study next
Got this wrong? Here's your next step.
Review dNS over TCP, then practise related CKS questions on the same topic to reinforce the concept.
- →
Minimize Microservice Vulnerabilities — study guide chapter
Learn the concepts, then practise the questions
- →
Minimize Microservice Vulnerabilities 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?
Minimize Microservice Vulnerabilities — This question tests Minimize Microservice Vulnerabilities — DNS over TCP.
What is the correct answer to this question?
The correct answer is: Add `NET_RAW` capability — TCP DNS lookups use standard TCP sockets, not raw sockets. These are permitted by the default syscall policy, and no additional Linux capability is required. All listed capabilities are unnecessary, as the container already has the ability to create TCP sockets.
What should I do if I get this CKS question wrong?
Review dNS over TCP, then practise related CKS questions on the same topic to reinforce the concept.
What is the key concept behind this question?
DNS over TCP
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: Jun 11, 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.