Exam AZ-400 topic 2 question 4 discussion

The readinessProbe is wrong. It clearly says "Initiate a shutdown if the pod is unresponsive." How can you iniate a shutdown (restart) with readinessProbe. It must have been livelinessProbe.

The correct answer is liveness because you want that your POD restart in case of failure. Readiness remove the POD from Load Balancer, but doesn't restart it. The kubelet uses liveness probes to know when to restart a container. For example, liveness probes could catch a deadlock, where an application is running, but unable to make progress. Restarting a container in such a state can help to make the application more available despite bugs. The kubelet uses readiness probes to know when a container is ready to start accepting traffic. A Pod is considered ready when all of its containers are ready. One use of this signal is to control which Pods are used as backends for Services. When a Pod is not ready, it is removed from Service load balancers.

The readiness probe ensures that the container is ready to handle incoming requests, and the periodSeconds property indicates the frequency of the readiness check.

1. livenessProbe: Ensures the container is running. If the liveness probe fails, Kubernetes will kill the container and restart it 2. initialDelaySeconds: 15

The correct answer is livenessProbe, and periodSeconds: 15 : apiVersion: v1 kind: Pod metadata: name: my-aks-pod spec: containers: - name: my-app-container image: my-app-image ports: - containerPort: 80 livenessProbe: httpGet: path: /healthz port: 80 initialDelaySeconds: 15 periodSeconds: 15 failureThreshold: 3

Liveness Probes Period Seconds: 15

Liveness Probes Period Seconds; 15 Liveness Probes are used to check if the pod is responding or not. If not reboot. Readiness probe is used to check if the pod is ready to accept request.

livelinessProbe is correct. readinessProbe is for checking container dependencies and seeing if services are ready for serve request.

Readiness probe & period seconds:15

I quote in microsoft official site; Readines Probes; For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. liveness probes; Azure Container Instances supports liveness probes so that you can configure your containers within your container group to restart if critical functionality is not working. Answers; Liveness Probes Period Seconds; 15

yaml code (GPT): livenessProbe: httpGet: path: /Server port: <port number> initialDelaySeconds: 15 periodSeconds: 15 timeoutSeconds: 15 failureThreshold: 4

The provided answers are correct - check the definition regarding containers probe types - https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes

https://docs.microsoft.com/en-us/azure/container-instances/container-instances-readiness-probe https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/ "readinessProbe Indicates whether the container is ready to respond to requests" "Confirm that the pod is responding to service requests" (From question) I would agree with the given answer

liveness to reboot when the system is unresponsive. Readness is when the system ready to accepts the requests.

Liveness Period seconds 15

I agree with liveness probe, it is described here https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes But it is Microsoft tests and all will be possible. One can observe metadata where you can find the name of pod =) It is related to readyness.

liveness is most appropriate (Kill the process)