CKAD Multi-Container Pods and Init Containers 3

Question 1

What is the behavior when multiple Init Containers are defined in a pod?

Accepted Answer

They run sequentially in the order defined

Answer

Multiple init containers run in the exact order they are listed in 'spec.initContainers', each waiting for the previous to succeed.

Question 2

Which command checks if a multi-container pod has all containers running?

Accepted Answer

Both A and B show container readiness

Answer

'kubectl get pod' shows a READY column (e.g., 2/2) and 'kubectl describe pod' shows each container's state — both are useful.

Question 3

A sidecar container in a pod runs a log forwarder. Which volume type allows it to read logs written by the main container?

Accepted Answer

emptyDir

Answer

An emptyDir volume is mounted by both containers, enabling the main container to write logs and the sidecar to read and forward them.

Question 4

What happens to init container logs after the init container completes successfully?

Accepted Answer

They remain accessible via 'kubectl logs' with the container name until the pod is deleted

Answer

Kubernetes retains init container logs even after they complete, accessible via 'kubectl logs -c '.

Question 5

Which resource field in a pod spec must match between containers to use the same volume?

Accepted Answer

volumes.name in spec.volumes and volumeMounts.name in each container

Answer

The volume is declared once in 'spec.volumes' with a name, and each container references that name in its 'volumeMounts.name' field.

CKAD - Certified Kubernetes Application Developer Practice Test