How does Kubernetes integrate with CNI plugins?

The container runtime configures the network without any external plugin

The API server directly configures network interfaces on nodes

The kubelet calls the CNI plugin when a pod is created or deleted

The scheduler assigns IP addresses to pods

What is the primary purpose of a NetworkPolicy in Kubernetes?

To provide DNS resolution for Services

To load-balance traffic between pods

To control traffic flow between pods and from external sources

How does a Service distribute traffic among the pods it selects?

By requiring the client to specify which pod to use

By sending traffic to the pod with the highest available memory

By sending all traffic to the pod with the lowest CPU usage

By using round-robin or random selection among the available pods

A developer is writing a multi-container pod that includes a main application container and a sidecar container that needs to communicate with the main container over localhost. What is the most reliable way for the sidecar container to reach the main container?

Use the main container's pod IP address.

Use the Service name that selects the main container.

Use 'localhost' with the port that the main container is listening on.

Use the node's IP address and the container's host port.

A developer is troubleshooting a newly deployed application on a single-node Kubernetes cluster. The application pod runs a web server that listens on port 8080. From the node, the developer can successfully curl the pod's IP address, but from inside the pod itself, the developer cannot reach the node's hostname. What is the most likely reason for this behavior?

The pod's /etc/hosts file is read-only and cannot be updated with the node's hostname.

Pods and the node share the same network namespace, so the node's hostname is not resolvable from within the pod.

The CNI plugin is misconfigured, preventing the pod from sending DNS queries to the cluster's CoreDNS service.

The pod's network namespace is isolated from the host's network namespace, so the node's hostname is not automatically resolvable from inside the pod.

Kubernetes and Cloud Native Associate (KCNA)

Domain 1Objective 3

Networking KCNA Practice Questions (Page 1)

Part of the Kubernetes Fundamentals domain, which accounts for 44% of the KCNA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~15–26 in this domain), expect 3–4 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

7concepts

44%of the exam

Questions 1–5

1foundation · easy
How does Kubernetes integrate with CNI plugins?
Select an answer first
2foundation · easy
What is the primary purpose of a NetworkPolicy in Kubernetes?
Select an answer first
3foundation · easy
How does a Service distribute traffic among the pods it selects?
Select an answer first
4application · medium
A developer is writing a multi-container pod that includes a main application container and a sidecar container that needs to communicate with the main container over localhost. What is the most reliable way for the sidecar container to reach the main container?
Select an answer first
5application · medium
A developer is troubleshooting a newly deployed application on a single-node Kubernetes cluster. The application pod runs a web server that listens on port 8080. From the node, the developer can successfully curl the pod's IP address, but from inside the pod itself, the developer cannot reach the node's hostname. What is the most likely reason for this behavior?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to KCNA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “KCNA” is a trademark of its owner, used for identification only.