Bird
0
0

A user reports that their Kubernetes pods are stuck in 'Pending' state after deployment. Which is the most likely cause?

medium📝 Troubleshoot Q7 of 15
Docker - Swarm
A user reports that their Kubernetes pods are stuck in 'Pending' state after deployment. Which is the most likely cause?
AThe pods have completed successfully
BNo available nodes have enough resources to schedule the pods
CThe Kubernetes API server is down
DThe pods are already running on other nodes
Step-by-Step Solution
Solution:

  1. Step 1: Understand 'Pending' pod state

    Pods stay 'Pending' when the scheduler cannot find suitable nodes with enough resources.

  2. Step 2: Evaluate other options

    Pods running or completed would not be 'Pending'; API server down causes different errors.

  3. Final Answer:

    No available nodes have enough resources to schedule the pods -> Option B

  4. Quick Check:

    Pending pods = resource shortage D [OK]
Quick Trick: Pending pods usually mean resource shortage [OK]
Common Mistakes:
  • Confusing 'Pending' with 'Running'
  • Assuming API server down causes Pending state
  • Thinking pods complete instantly

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Why container security matters - Quiz 12easy Docker Security - Capabilities and privilege control - Quiz 6medium Docker Swarm - Overlay networks in Swarm - Quiz 2easy Docker Swarm - Swarm mode initialization - Quiz 10hard Docker Swarm - Deploying services in Swarm - Quiz 3easy Docker Swarm - Overlay networks in Swarm - Quiz 9hard Docker in CI/CD - GitHub Actions with Docker - Quiz 8hard Image Optimization - BuildKit for improved builds - Quiz 8hard Logging and Monitoring - Container metrics collection - Quiz 12easy Production Patterns - Ambassador container pattern - Quiz 4medium