Bird
0
0

You want to ensure a Deployment always has exactly 4 pods running, even if some pods crash. Which Kubernetes feature ensures this?

hard📝 Workflow Q8 of 15
Kubernetes - Fundamentals
You want to ensure a Deployment always has exactly 4 pods running, even if some pods crash. Which Kubernetes feature ensures this?
AThe reconciliation loop continuously recreates pods to match desired replicas
BThe Service automatically restarts crashed pods
CThe ConfigMap updates pod count dynamically
DThe Namespace limits pod crashes
Step-by-Step Solution
Solution:

  1. Step 1: Identify feature that maintains pod count

    The reconciliation loop monitors actual pods and recreates any missing pods to maintain desired count.

  2. Step 2: Exclude unrelated features

    Services expose pods but don't restart them, ConfigMaps store config, Namespaces do not limit crashes.

  3. Final Answer:

    The reconciliation loop continuously recreates pods to match desired replicas -> Option A

  4. Quick Check:

    Reconciliation loop = ensures exact pod count [OK]
Quick Trick: Reconciliation loop keeps pod count stable despite crashes [OK]
Common Mistakes:
  • Thinking Service restarts pods
  • Assuming ConfigMap controls pod count
  • Believing Namespace limits crashes

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Control plane components (API server, scheduler, controller manager, etcd) - Quiz 5medium Labels and Selectors - Using labels for service routing - Quiz 11easy Labels and Selectors - Label selectors (equality, set-based) - Quiz 4medium Namespaces - Default namespaces overview - Quiz 2easy Namespaces - Resource quotas per namespace - Quiz 7medium Pods - Executing commands in Pods - Quiz 8hard Pods - Pod lifecycle states - Quiz 10hard Pods - Executing commands in Pods - Quiz 6medium ReplicaSets and Deployments - Scaling Deployments - Quiz 1easy Services - Headless services concept - Quiz 3easy