The correct options are NetworkPolicy to restrict traffic to the updated pods and Rolling update deployment strategy.

A Rolling update deployment strategy updates pods gradually so that old and new releases can coexist during the rollout. This strategy lets you control how many pods are updated at once so you can maintain availability while new replicas start.

A NetworkPolicy to restrict traffic to the updated pods allows you to limit which sources can reach the new pods during the rollout. You can use pod selectors and ingress rules to stage traffic to the updated instances while keeping broader access to the previous release.

Readiness probes on application containers indicate when a pod is ready to receive traffic but they do not orchestrate a staged replacement of versions or enforce network restrictions. Readiness probes alone will not manage rollout concurrency or network access policies.

Resource quota limits in the namespace control consumption of CPU, memory and other resources across a namespace. They do not provide a mechanism to perform rolling updates or to restrict traffic to a subset of pods during deployment.

Recreate deployment strategy replaces all old pods by first terminating them and then creating new ones so it cannot keep both releases available at the same time. That strategy will cause downtime for workloads that require simultaneous old and new instances.

Full AWS Practitioner Certification Question