Bird
0
0

You want to ensure your application has enough time to start before Kubernetes starts probing it. Which probe and configuration should you use?

hard📝 Workflow Q8 of 15
Kubernetes - Health Checks and Probes
You want to ensure your application has enough time to start before Kubernetes starts probing it. Which probe and configuration should you use?
AUse a readiness probe with a low timeoutSeconds value
BUse a startup probe with a high initialDelaySeconds value
CUse a liveness probe with a short periodSeconds value
DUse no probes and rely on manual pod restarts
Step-by-Step Solution
Solution:

  1. Step 1: Understand startup probe purpose

    Startup probes delay other probes until app is fully started.

  2. Step 2: Configure startup probe timing

    Setting high initialDelaySeconds gives app time to initialize before checks.

  3. Final Answer:

    Use a startup probe with a high initialDelaySeconds value -> Option B

  4. Quick Check:

    Startup probe delays checks = App startup time [OK]
Quick Trick: Startup probe delays health checks until app is ready [OK]
Common Mistakes:
  • Using readiness probe to delay startup
  • Setting liveness probe with short intervals
  • Skipping probes and manual restarts

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Immutable ConfigMaps - Quiz 13medium Health Checks and Probes - Exec probe configuration - Quiz 5medium Health Checks and Probes - Startup probe concept - Quiz 10hard Health Checks and Probes - Startup probe concept - Quiz 11easy Networking - Pod-to-Pod communication - Quiz 11easy Networking - DNS in Kubernetes (CoreDNS) - Quiz 3easy Persistent Storage - Storage classes for dynamic provisioning - Quiz 11easy Persistent Storage - Reclaim policies (Retain, Delete) - Quiz 9hard Secrets - Using Secrets as environment variables - Quiz 6medium Secrets - Why Secrets manage sensitive data - Quiz 4medium