[Solved] Why does a Kubernetes NetworkPolicy with no ingress or egress rules deny all traffic by default? — Ans: Because NetworkPolicy defaults to deny all traffic unless explicitly allowed | Kubernetes

Kubernetes - RBAC and Security

Why does a Kubernetes NetworkPolicy with no ingress or egress rules deny all traffic by default?

ABecause Kubernetes disables networking until policies are applied

BBecause pods have no IP addresses assigned

CBecause NetworkPolicy only controls DNS traffic by default

DBecause NetworkPolicy defaults to deny all traffic unless explicitly allowed

Step-by-Step Solution

Solution:

Step 1: Understand default NetworkPolicy behavior
NetworkPolicy enforces a default deny for traffic directions it controls if no rules allow traffic.
Step 2: Confirm why traffic is denied
Without explicit allow rules, all ingress or egress traffic is blocked.
Final Answer:
Because NetworkPolicy defaults to deny all traffic unless explicitly allowed -> Option D
Quick Check:
Default deny unless allowed = A [OK]

Quick Trick: NetworkPolicy denies all traffic by default without allow rules [OK]

Common Mistakes:

Master "RBAC and Security" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Why does a Kubernetes NetworkPolicy with no ingress or egress rules deny all traffic by default?