Bird
0
0

If a liveness probe fails continuously, what is the expected behavior of the Kubernetes system?

medium📝 Analysis Q5 of 15
Microservices - Orchestration with Kubernetes
If a liveness probe fails continuously, what is the expected behavior of the Kubernetes system?
AKubernetes scales the pod replicas up
BKubernetes removes the pod from the service endpoints
CKubernetes ignores the failure and keeps the pod running
DKubernetes restarts the container repeatedly
Step-by-Step Solution
Solution:

  1. Step 1: Identify liveness probe failure consequence

    Continuous failure of liveness probe causes Kubernetes to restart the container to recover it.

  2. Step 2: Exclude other behaviors

    Removing from endpoints is readiness failure effect; scaling or ignoring failure is incorrect.

  3. Final Answer:

    Kubernetes restarts the container repeatedly on liveness failure -> Option D

  4. Quick Check:

    Liveness failure = Restart container [OK]
Quick Trick: Liveness failure triggers restart, readiness failure stops traffic [OK]
Common Mistakes:
MISTAKES
  • Confusing readiness and liveness failure effects
  • Thinking pod is deleted on liveness failure
  • Assuming scaling happens automatically

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Event-Driven Architecture - Event types (domain, integration, notification) - Quiz 8hard Event-Driven Architecture - Eventual consistency handling - Quiz 10hard Monitoring and Observability - Correlation IDs - Quiz 14medium Orchestration with Kubernetes - Horizontal Pod Autoscaler - Quiz 13medium Resilience Patterns - Circuit breaker pattern - Quiz 13medium Resilience Patterns - Fallback pattern - Quiz 8hard Resilience Patterns - Circuit breaker pattern - Quiz 1easy Service Mesh - Linkerd overview - Quiz 3easy Service Mesh - Service mesh concept - Quiz 15hard Service Mesh - Why service mesh manages inter-service traffic - Quiz 1easy