[Solved] Which of these is a valid reason to use kubectl debug instead of kubectl exec? — Ans: To run a new container with debugging tools when the original container lacks... | Kubernetes

Kubernetes - Troubleshooting

Which of these is a valid reason to use kubectl debug instead of kubectl exec?

ATo restart the pod automatically after failure

BTo permanently change the pod's container image

CTo list all pods in the cluster

DTo run a new container with debugging tools when the original container lacks them

Step-by-Step Solution

Solution:

Step 1: Compare kubectl debug and kubectl exec
kubectl exec runs commands inside existing containers, but if the container lacks debugging tools, it won't help. kubectl debug can add a new container with tools.
Step 2: Understand other options
Changing images, restarting pods, or listing pods are unrelated to debugging with kubectl debug.
Final Answer:
To run a new container with debugging tools when the original container lacks them -> Option D
Quick Check:
Use case for kubectl debug = Add debug container [OK]

Quick Trick: Use kubectl debug to add tools missing in original container [OK]

Common Mistakes:

Master "Troubleshooting" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Which of these is a valid reason to use kubectl debug instead of kubectl exec?