Liveness probes trigger the kubelet to restart a container when they fail while readiness probes mark whether the Pod is part of a Service's endpoints and therefore accepts traffic is correct.

Liveness probes are used by the kubelet to detect when a container is unhealthy and to restart that container to attempt recovery. Readiness probes are used to signal whether a Pod should be included in a Service's endpoints so that only Pods that are ready receive traffic.

Liveness probes run only once when a Pod initializes while readiness probes run periodically is incorrect because probes run periodically after any configured initial delay and liveness checks are not one time events.

Both liveness and readiness probes are intended to restart a Pod when they detect a problem is incorrect because readiness probes do not trigger restarts and they only control traffic routing, while liveness probes can cause the kubelet to restart containers.

Liveness probes prevent a Pod from receiving traffic while readiness probes cause the kubelet to restart containers is incorrect because the behaviors are reversed. Readiness controls whether a Pod receives traffic and liveness can lead to container restarts.

Full AWS Practitioner Certification Question