Kubernetes - Health Checks and Probes
Which of the following is a correct way to define a liveness probe using an HTTP GET request in a pod spec?
Which of the following is a correct way to define a liveness probe using an HTTP GET request in a pod spec?
easy📝 Configuration Q12 of 15
Step-by-Step Solution
Solution:
Step 1: Check HTTP GET syntax for livenessProbe
The correct syntax useshttpGetwithpathand numericport. "livenessProbe:\n httpGet:\n path: /healthz\n port: 8080\n initialDelaySeconds: 5" matches this.Step 2: Identify errors in other options
"livenessProbe:\n exec:\n command: [\"curl\", \"/healthz\"]\n initialDelaySeconds: 5" uses exec with curl incorrectly. "livenessProbe:\n tcpSocket:\n path: /healthz\n port: 8080\n initialDelaySeconds: 5" wrongly uses tcpSocket with a path. "livenessProbe:\n httpGet:\n path: healthz\n port: 'eighty'\n initialDelaySeconds: 5" uses a string for port instead of a number.Final Answer:
"livenessProbe:\n httpGet:\n path: /healthz\n port: 8080\n initialDelaySeconds: 5" -> Option AQuick Check:
HTTP GET probe syntax = "livenessProbe:\n httpGet:\n path: /healthz\n port: 8080\n initialDelaySeconds: 5" [OK]
Quick Trick: HTTP GET needs numeric port and valid path [OK]
Common Mistakes:
- Using string instead of number for port
- Adding path to tcpSocket probe
- Using exec command incorrectly
Master "Health Checks and Probes" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes