Question 6
Domain 4: Services, Networking, and Service DiscoveryWhich Pod manifest best creates a temporary debug Pod in namespace q32 to test reachability of backend-svc using busybox?
Correct answer: A
Explanation
A temporary debug Pod should use a lightweight image like "busybox:latest" and run a one-shot command such as "wget -qO- http://backend-svc.q32.svc.cluster.local" to test service reachability. Setting "restartPolicy: Never" makes it a non-restarting diagnostic Pod, and placing it in namespace "q32" ensures it resolves the service name in the same namespace.
Why each option is right or wrong
A. A Pod named debug-pod in namespace q32, using image busybox:latest, running wget -qO- http://backend-svc.q32.svc.cluster.local, with restartPolicy: Never
Under the Pod API, `restartPolicy` for a standalone Pod must be either `Always`, `OnFailure`, or `Never` (Kubernetes Pod spec), and `Never` is the correct choice for a one-shot diagnostic container so it exits after the probe instead of looping. Using the fully qualified service DNS name `backend-svc.q32.svc.cluster.local` targets the Service in namespace `q32` via the standard cluster DNS format `<service>.<namespace>.svc.cluster.local`, and `busybox:latest` is a minimal image that includes `wget` for a simple reachability test.
B. A Pod named debug-pod in namespace q32, using image busybox:latest, running curl http://backend-svc, with restartPolicy: Always
C. A Pod named backend-pod in namespace default, using image busybox:latest, running wget -qO- http://backend-svc.q32.svc.cluster.local, with restartPolicy: Never
D. A Deployment named debug-pod in namespace q32, using image busybox:latest, running wget -qO- http://backend-svc.q32.svc.cluster.local