CKAD Multi-Container Pods and Init Containers

Question 1

Which multi-container pattern uses a secondary container to handle network communication on behalf of the primary container?

Accepted Answer

Ambassador

Answer

Sidecar

Answer

Adapter

Answer

Proxy

Question 2

What is the primary purpose of an Init Container in a Pod?

Accepted Answer

To perform setup tasks that must complete before the main containers start

Answer

To run alongside the main container and share CPU

Answer

To restart the main container when it crashes

Answer

To expose metrics from the main container

Question 3

In a multi-container pod, how do containers share network communication?

Accepted Answer

Via shared loopback interface — they share the same network namespace

Answer

Via Kubernetes Services only

Answer

Via mounted shared volumes

Answer

Via ClusterIP addresses assigned to each container

Question 4

Which multi-container pattern uses a helper container to normalize or transform the main container's output?

Accepted Answer

Adapter

Answer

Ambassador

Answer

Sidecar

Answer

Controller

Question 5

What happens if an Init Container fails in a Pod?

Accepted Answer

Kubernetes retries the init container until it succeeds or the pod restartPolicy prevents it

Answer

The pod continues and skips the init container

Answer

The main containers start with a warning

Answer

The pod is deleted and not recreated

Question 6

How do containers in the same pod share data using a volume?

Accepted Answer

Both containers reference the same volume name in their volumeMounts

Answer

They use a shared PersistentVolumeClaim only

Answer

They communicate via the pod's IP address

Answer

They use Kubernetes Secrets to pass data