Kubernetes - Health Checks and ProbesWhat is the main purpose of an exec probe in Kubernetes?ATo schedule pods on specific nodesBTo expose container ports to the outside worldCTo create persistent storage volumesDTo run a command inside a container to check if it is healthyCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand exec probe functionalityAn exec probe runs a command inside the container to check its health status.Step 2: Compare with other optionsOptions A, B, and D relate to scheduling, networking, and storage, not health checks.Final Answer:To run a command inside a container to check if it is healthy -> Option DQuick Check:Exec probe = runs command inside container [OK]Quick Trick: Exec probe runs commands inside container to check health [OK]Common Mistakes:Confusing exec probe with port exposureThinking exec probe schedules podsMixing exec probe with storage management
Master "Health Checks and Probes" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes Ingress - Ingress vs LoadBalancer Service decision - Quiz 1easy Networking - Pod-to-Pod communication - Quiz 15hard Persistent Storage - Reclaim policies (Retain, Delete) - Quiz 1easy Scheduling - Pod priority and preemption - Quiz 6medium Scheduling - Jobs and CronJobs for batch processing - Quiz 1easy Scheduling - Why scheduling controls Pod placement - Quiz 5medium Scheduling - Node selectors for simple scheduling - Quiz 14medium Secrets - Creating Secrets - Quiz 7medium Secrets - Secret types (Opaque, docker-registry, TLS) - Quiz 13medium Secrets - Using Secrets as environment variables - Quiz 15hard