Pods can both send and receive network traffic is correct.

Kubernetes provides a flat pod network where each pod gets its own IP and pods can reach other pods by default when no Network firewall or VPC controls block pod traffic until explicit rules are added or NetworkPolicy resources are present to restrict traffic.

NetworkPolicies are used to restrict traffic and they are not enforced unless a policy exists and the cluster network plugin supports the policies. In other words traffic is allowed by default and rules must be added to deny or limit connectivity.

Network firewall or VPC controls block pod traffic until explicit rules are added is incorrect because Kubernetes itself does not block inter‑pod traffic by default. Cloud provider firewalls or node security groups can affect traffic at the node level but that is separate from the Kubernetes default pod networking model.

Outbound connections are allowed but inbound connections are blocked is incorrect because there is no built in asymmetric block like that for pods. By default pods can both initiate and receive connections from other pods unless a NetworkPolicy restricts them.

All inbound and outbound traffic is prevented for every pod is incorrect because the default policy is permissive and not deny all. Traffic is only restricted when you create network policies or when external network controls block it.

Full AWS Practitioner Certification Question