A county engineer claims every Pod shares the node's network namespace by default. What is the correct default networking behavior?
Select an answer to reveal the explanation.
Short Explanation
By default each Pod gets its own IP on the cluster network—like its own apartment address—not a shared seat on the node's network namespace. hostNetwork is an opt-in exception, not the everyday path.
Full Explanation
When a county engineer claims every Pod shares the node's network namespace by default, the correct default networking behavior is that Pods normally receive unique IPs on the CNI network and do not use hostNetwork by default. hostNetwork true is an explicit opt-in that shares the node network namespace; ordinary application Pods get CNI-allocated addresses and isolated network namespaces for multi-tenant county workloads.
All Pods do not use hostNetwork true unless a ServiceAccount disables it. Pods do not inherit the node's IP exclusively without CNI addresses by default. It is false that only kube-system Pods get CNI IPs while application Pods must set hostNetwork.
Exam caveat: some system components may use hostNetwork intentionally; do not generalize that to all workloads. Operational check: kubectl get pods -o wide and confirm distinct Pod IPs; inspect PodSpec for hostNetwork only when intentionally required. This distinction matters on the CKA because distractors often mix adjacent objects that sound related but solve a different control-plane problem. This distinction matters on the CKA because distractors often mix adjacent objects that sound related but solve a different control-plane problem.