Exam AZ-400 topic 3 question 6 discussion

Should be A Liveness Probe https://docs.microsoft.com/en-us/azure/container-instances/container-instances-liveness-probe

Answer is A

No Probe, No Fun

A is correct

Correct A since it need to restart if it fails

for me is A

Liveness Probe

Liveness probe to restart the container

57. When using Helth check in Kubernets, there are two types of resources: - Readiness probe: this feature is used during the creation of a new pod, where it informs if the pods in question can already receive “requests”. - Liveness probe: here is a process to know if the pods are live or inactive. It is this feature that configures the automatic restart when the power stops responding.

A liveness probe is a diagnostic tool used to check the health of a container and determine if it is running properly. By adding a liveness probe to the YAML configuration of App1, you can periodically check if the application is responsive. If the liveness probe fails, indicating that the application is not responding, Azure DevOps can automatically restart ACI1.

If your main goal is to restart the container when the application within it becomes unresponsive or enters an invalid state, then you should include a liveness probe in the YAML configuration of App1.

Agree on A

(A) Liveness Probe - To restart the instance Both liveness & readiness probes are used to control the health of an application. Failing liveness probe will restart the container, whereas failing readiness probe will stop our application from serving traffic.

Answer should be liveness container. As in case of readiness probe failure , container is never restarted.But only traffic is not send to the container. Only in case of liveness probe , container is restarted.

A. Add a liveness probe to the YAML configuration of App1. A liveness probe is used to detect when an application is no longer responding and take action to restart the application, such as restarting the container. By adding a liveness probe to the YAML configuration of App1, you can configure the probe to check if the application is responding and if not, trigger a restart of the container instance ACI1.

Simply put ReadinessProbe will check the app until its active once it gets confirmation it will loop out Liveness Probe will come into play after the ReadinessProbe & it will keep on checking the application until it stops.

When it stops responding, not check if is ready to take requests. Should be 'Liveliness probe'.