Bird
0
0

You run kubectl rollout status deployment/webapp but it hangs indefinitely. What is a likely cause?

medium📝 Troubleshoot Q6 of 15
Kubernetes - ReplicaSets and Deployments
You run kubectl rollout status deployment/webapp but it hangs indefinitely. What is a likely cause?
AThe deployment does not exist
BThe command syntax is incorrect
CThe deployment is stuck because pods are not becoming ready
DThe cluster is offline
Step-by-Step Solution
Solution:

  1. Step 1: Analyze hanging rollout status

    If the command hangs, it usually means the rollout is waiting for pods to become ready.

  2. Step 2: Exclude other causes

    If deployment did not exist, an error would show immediately. Syntax errors cause instant failure. Cluster offline would affect all commands.

  3. Final Answer:

    The deployment is stuck because pods are not becoming ready -> Option C

  4. Quick Check:

    Hanging rollout = pods not ready [OK]
Quick Trick: Hanging rollout usually means pods are not ready [OK]
Common Mistakes:
  • Assuming deployment does not exist without error
  • Blaming command syntax without checking
  • Ignoring pod readiness status

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Labels and Selectors - Annotations vs labels - Quiz 11easy Labels and Selectors - Why labels organize resources - Quiz 6medium Namespaces - Why namespaces provide isolation - Quiz 15hard Namespaces - Limit ranges for defaults - Quiz 2easy Pods - Sidecar container pattern - Quiz 14medium Pods - Viewing Pod details and logs - Quiz 13medium Services - Endpoints and endpoint slices - Quiz 12easy Services - Service discovery via DNS - Quiz 8hard kubectl Essential Commands - kubectl port-forward for local access - Quiz 2easy kubectl Essential Commands - kubectl logs for debugging - Quiz 13medium