Kubernetes and Cloud Native Security Associate (KCSA) Practice Questions

Kubernetes and Cloud Native Security Associate (KCSA) exam preparationAligned with the official KCSA Exam Curriculum (CNCF, published 2024-06-24; retrieved 2026-11-08)

Kubernetes and Cloud Native Security Associate (KCSA) practice questions in English: 180 questions with explanations. The mock exam has 60 questions and 90 minutes.

Kubernetes and Cloud Native Security Associate (KCSA) free question 5 / 10 · Domain 3: Kubernetes Security Fundamentals

Pod "api" is selected for ingress by two NetworkPolicies. Policy 1 allows traffic from Pods labelled role=web. Policy 2 allows traffic from Pods labelled role=batch. Which Pods in its namespace can connect to "api"?

  1. No Pods, because the two policies conflict and conflicting policies deny traffic.
  2. Just Pods labelled role=web, because Policy 1 was created before the role=batch one.
  3. Pods labelled role=web and Pods labelled role=batch, as the policies add up.
  4. Just the Pods that carry both labels, because each policy narrows the other one.
Show the answer and explanation

Answer: C

Why this is correct
A Pod is isolated for ingress once any NetworkPolicy that selects it has Ingress in its policyTypes. From then on, other Pods can connect to it only as far as the ingress list of some policy that applies to it allows. The page then says: "Network policies do not conflict; they are additive. If any policy or policies apply to a given pod for a given direction, the connections allowed in that direction from that pod is the union of what the applicable policies allow. Thus, order of evaluation does not affect the policy result." So both role=web and role=batch Pods may connect to "api"; neither policy takes anything away from the other.

Why the other options are wrong
"Just Pods labelled role=web, because Policy 1 was created before the role=batch one." … The page says the result is a union, "Thus, order of evaluation does not affect the policy result." Which policy came first does not matter.
"No Pods, because the two policies conflict and conflicting policies deny traffic." … "Network policies do not conflict; they are additive." Two policies selecting the same Pod each add allowed connections.
"Just the Pods that carry both labels, because each policy narrows the other one." … The page describes the opposite of narrowing: "The effects of those ingress lists combine additively." A Pod needs to match one policy's rule, not all of them.

NetworkPolicies only add
There is no precedence and no conflict between NetworkPolicies. What a Pod may receive is the union of all policies that select it.

Go to the Kubernetes and Cloud Native Security Associate (KCSA) practice app (10 free questions; purchase unlocks all questions)

See the full practice set