Bird
0
0

A developer configures a readiness probe but forgets to set 'initialDelaySeconds'. What issue might occur?

medium📝 Analysis Q6 of 15
Microservices - Orchestration with Kubernetes
A developer configures a readiness probe but forgets to set 'initialDelaySeconds'. What issue might occur?
AThe liveness probe will override readiness probe
BThe pod will never start
CThe probe may fail immediately causing the pod to be marked unready
DThe pod will restart continuously
Step-by-Step Solution
Solution:

  1. Step 1: Understand initialDelaySeconds role

    This setting delays the first probe to allow container startup; missing it causes immediate probing.

  2. Step 2: Consequence of missing initial delay

    Immediate probe may fail if container is not ready, marking pod unready prematurely.

  3. Final Answer:

    Probe fails immediately causing pod to be marked unready -> Option C

  4. Quick Check:

    Missing initialDelaySeconds = Immediate probe failure [OK]
Quick Trick: Set initialDelaySeconds to avoid premature probe failures [OK]
Common Mistakes:
MISTAKES
  • Assuming pod won't start without initialDelaySeconds
  • Confusing readiness and liveness probe effects
  • Thinking pod restarts due to readiness probe failure

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