Which of the following YAML snippets correctly defines a readiness probe using a TCP socket in a Kubernetes pod spec?

easy📝 Configuration Q3 of 15

Kubernetes - Health Checks and Probes

AreadinessProbe: tcpSocket: port: 3306 initialDelaySeconds: 5 periodSeconds: 10

BreadinessProbe: httpGet: path: /health port: 3306 initialDelaySeconds: 5

CreadinessProbe: exec: command: ["curl", "-f", "http://localhost:3306"] periodSeconds: 10

DreadinessProbe: tcpSocket: path: /ready port: 3306 periodSeconds: 10

Step-by-Step Solution

Solution:

Step 1: Identify valid readiness probe types
Readiness probes can be httpGet, tcpSocket, or exec.
Step 2: Check tcpSocket syntax
tcpSocket requires only a port number, no path.
Step 3: Validate options
readinessProbe: tcpSocket: port: 3306 initialDelaySeconds: 5 periodSeconds: 10 correctly uses tcpSocket with port and timing fields.
Final Answer:
Option A -> Option A
Quick Check:
tcpSocket needs port only, no path [OK]

Quick Trick: tcpSocket readiness probe requires only port, no path [OK]

Common Mistakes:

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes