KCNA Pod Management & Scheduling 4

Question 1

Which field enables a Pod to run as a specific user ID at the container level?

Accepted Answer

securityContext.runAsUser

Answer

Setting `securityContext.runAsUser` in a container spec makes the container process run as the specified UID.

Question 2

What is the role of the `scheduler.alpha.kubernetes.io/node` annotation on a Pod?

Accepted Answer

It manually assigns the pod to a specific node, bypassing the scheduler

Answer

Setting `nodeName` (or the legacy node annotation) bypasses the scheduler entirely and directly binds the pod to the named node.

Question 3

A readiness probe failing on a pod causes which behavior?

Accepted Answer

The pod's IP is removed from the Service's Endpoints, stopping traffic

Answer

A failing readiness probe removes the pod from Service endpoints so no traffic is routed to it, without killing the container.

Question 4

Which Kubernetes concept allows a pod to request exclusive access to a GPU or custom device on a node?

Accepted Answer

Device Plugins and resource limits with extended resources

Answer

Device Plugins expose custom resources (like `nvidia.com/gpu`) that pods can request via `resources.limits` in their container spec.

Question 5

What happens to pods managed by a ReplicaSet when you manually delete one of them?

Accepted Answer

The ReplicaSet controller creates a replacement pod to maintain the desired replica count

Answer

The ReplicaSet controller continuously reconciles actual vs desired state and immediately creates a new pod to replace the deleted one.

(KCNA) Kubernetes and Cloud Native Associate Practice Test