Home › Software Testing › Software Testing › microservices_cloud_observability › A Kubernetes 'liveness probe' detects
A Kubernetes 'liveness probe' detects
AA container deployed to wrong region
BA container that is stuck and needs restart
CA container that has not yet started up
DA container with too many open ports
Answer & Solution
Correct answer: B. A container that is stuck and needs restart
Liveness probes restart unhealthy containers (deadlocked, hung). Readiness probes signal whether the pod can receive traffic (boot complete, dependencies ready). Startup probes give slow-starting apps time before liveness kicks in.
Related questions
A 'red team' in security testing is a group that'Test impact analysis' speeds CI byIn Test Maturity Model integrated (TMMi), Level 2 is'Test pyramid' for microservices typically pushes effort toQuality gates in a deployment pipeline areA test environment management strategy primarily addressesGame days in production resilience testing involveFeature flags enable testing by