TCP probe configuration in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a TCP liveness probe port.

Kubernetes

livenessProbe:
  tcpSocket:
    port: [1]

Drag options to blanks, or click blank then click option'

A80

B8080

C443

D22

Attempts:

3 left

💡 Hint

Common Mistakes

Using a port number that the container does not listen on.

Using a string instead of a number for the port.

The TCP probe port is set to 80, which is a common HTTP port used for checking container health.

2fill in blank

medium

Complete the code to set the initial delay seconds for the TCP readiness probe.

Kubernetes

readinessProbe:
  tcpSocket:
    port: 3306
  initialDelaySeconds: [1]

Drag options to blanks, or click blank then click option'

A5

B10

C0

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Setting initialDelaySeconds too low causing false failures.

Using zero which may cause immediate probe failures.

Setting initialDelaySeconds to 10 gives the container time to start before Kubernetes checks readiness.

3fill in blank

hard

Fix the error in the TCP liveness probe configuration by completing the missing field.

Kubernetes

livenessProbe:
  tcpSocket:
    port: [1]
  periodSeconds: 15

Drag options to blanks, or click blank then click option'

Areadiness

Bhttp

Ctcp

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using protocol names like 'http' or 'tcp' instead of port numbers.

Confusing readiness probe settings with liveness probe.

The port must be a number, such as 8080, not a protocol name or unrelated string.

4fill in blank

hard

Fill both blanks to configure a TCP readiness probe with a timeout and success threshold.

Kubernetes

readinessProbe:
  tcpSocket:
    port: [1]
  timeoutSeconds: [2]

Drag options to blanks, or click blank then click option'

A5432

B5

C10

D3306

Attempts:

3 left

💡 Hint

Common Mistakes

Using a port number that does not match the service.

Setting timeoutSeconds too high causing slow failure detection.

The port 3306 is for MySQL TCP readiness probe, and timeoutSeconds 5 means the probe waits 5 seconds before timing out.

5fill in blank

hard

Fill all three blanks to complete a TCP liveness probe with port, failure threshold, and period seconds.

Kubernetes

livenessProbe:
  tcpSocket:
    port: [1]
  failureThreshold: [2]
  periodSeconds: [3]

Drag options to blanks, or click blank then click option'

A8080

B3

C10

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong port numbers.

Setting failureThreshold too low causing restarts.

Setting periodSeconds too high delaying failure detection.

Port 8080 is common for web apps, failureThreshold 3 means 3 failed probes before restart, and periodSeconds 10 means probe runs every 10 seconds.