- A
NetworkPolicy: A Kubernetes resource that defines rules for ingress and egress traffic to and from pods.
This is the standard definition of a Kubernetes NetworkPolicy.
- B
Calico network policy: A policy implemented by Calico that supports advanced features like IP blocks and service account selectors.
Calico network policies extend Kubernetes NetworkPolicy with additional capabilities.
- C
Ingress rule: In a NetworkPolicy, specifies which incoming traffic is allowed to reach pods.
Ingress rules control inbound traffic to pods.
- D
Egress rule: In a NetworkPolicy, specifies which incoming traffic is allowed to reach pods.
Why wrong: This is incorrect because egress rules control outgoing traffic, not incoming.
- E
Default deny: A policy that blocks all traffic unless explicitly permitted by another policy.
A default deny policy ensures no traffic is allowed without explicit rules.
- F
Calico network policy: A Kubernetes native resource for network segmentation.
Why wrong: Incorrect because Calico network policy is not native; it is added by the Calico CNI plugin.
Kubernetes Network Security Concepts Explained
This CKS practice question tests your understanding of minimize microservice vulnerabilities. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
Match each Kubernetes network security concept to its definition.
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
NetworkPolicy: A Kubernetes resource that defines rules for ingress and egress traffic to and from pods.
Correct matches: NetworkPolicy defines ingress/egress rules; Calico network policy extends with advanced features; Ingress rule controls inbound traffic; Egress rule controls outbound traffic; Default deny blocks all unless allowed. Common confusions include swapping ingress and egress definitions and mistaking non-native policies as native.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
NetworkPolicy: A Kubernetes resource that defines rules for ingress and egress traffic to and from pods.
Why this is correct
This is the standard definition of a Kubernetes NetworkPolicy.
Related concept
Standard ACLs match source addresses.
- ✓
Calico network policy: A policy implemented by Calico that supports advanced features like IP blocks and service account selectors.
Why this is correct
Calico network policies extend Kubernetes NetworkPolicy with additional capabilities.
Related concept
Standard ACLs match source addresses.
- ✓
Ingress rule: In a NetworkPolicy, specifies which incoming traffic is allowed to reach pods.
Why this is correct
Ingress rules control inbound traffic to pods.
Related concept
Standard ACLs match source addresses.
- ✗
Egress rule: In a NetworkPolicy, specifies which incoming traffic is allowed to reach pods.
Why it's wrong here
This is incorrect because egress rules control outgoing traffic, not incoming.
- ✓
Default deny: A policy that blocks all traffic unless explicitly permitted by another policy.
Why this is correct
A default deny policy ensures no traffic is allowed without explicit rules.
Related concept
Standard ACLs match source addresses.
- ✗
Calico network policy: A Kubernetes native resource for network segmentation.
Why it's wrong here
Incorrect because Calico network policy is not native; it is added by the Calico CNI plugin.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
- Standard ACLs match source addresses.
- Extended ACLs can match source, destination, protocol and ports.
- The first matching ACL entry is used.
- There is usually an implicit deny at the end.
TExam Day Tips
- Check inbound versus outbound direction.
- Read the ACL from top to bottom.
- Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
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.
What to study next
Got this wrong? Here's your next step.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related CKS ACL questions on filtering logic and placement.
- →
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 — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: NetworkPolicy: A Kubernetes resource that defines rules for ingress and egress traffic to and from pods. — Correct matches: NetworkPolicy defines ingress/egress rules; Calico network policy extends with advanced features; Ingress rule controls inbound traffic; Egress rule controls outbound traffic; Default deny blocks all unless allowed. Common confusions include swapping ingress and egress definitions and mistaking non-native policies as native.
What should I do if I get this CKS question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related CKS ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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.