Bird
0
0

You notice your ReplicaSet is not maintaining the desired number of pods. Which of these could be the cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - ReplicaSets and Deployments
You notice your ReplicaSet is not maintaining the desired number of pods. Which of these could be the cause?
AThe ReplicaSet is using the correct image version
BThe ReplicaSet has too many replicas defined
CThe pods are running on nodes with enough resources
DThe ReplicaSet's label selector does not match pod labels
Step-by-Step Solution
Solution:

  1. Step 1: Identify how ReplicaSet tracks pods

    ReplicaSets use label selectors to find and manage pods.

  2. Step 2: Understand impact of label mismatch

    If selectors don't match pod labels, ReplicaSet cannot manage pods, causing availability issues.

  3. Final Answer:

    The ReplicaSet's label selector does not match pod labels -> Option D

  4. Quick Check:

    Label selector mismatch breaks ReplicaSet control [OK]
Quick Trick: Check label selectors match pod labels exactly [OK]
Common Mistakes:
  • Assuming too many replicas cause pod loss
  • Ignoring label selector importance
  • Thinking correct image fixes pod count issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Kubernetes architecture (control plane and nodes) - Quiz 1easy Kubernetes Fundamentals - Kubernetes architecture (control plane and nodes) - Quiz 14medium Labels and Selectors - Adding labels to resources - Quiz 7medium Labels and Selectors - Label selectors (equality, set-based) - Quiz 12easy Namespaces - Default namespaces overview - Quiz 13medium Namespaces - Resource quotas per namespace - Quiz 3easy Pods - Pod lifecycle states - Quiz 8hard ReplicaSets and Deployments - Recreate update strategy - Quiz 6medium Services - Service selectors and labels - Quiz 10hard kubectl Essential Commands - kubectl port-forward for local access - Quiz 4medium