The resources field inside the containers definition is the correct answer.

You declare CPU and memory requests and limits per container inside the pod manifest under the container's resources field. Values go under resources.requests and resources.limits for each entry in spec.containers so the scheduler and kubelet know how to allocate and enforce resources.

A LimitRange object declared in the namespace is not where you put the resource lines in a pod manifest. LimitRange can provide defaults or enforce minimum and maximum values in a namespace but it does not replace the per container resources section in the pod spec.

The resources attribute under the metadata section is incorrect because metadata stores name, labels, and annotations. The resources field belongs to the container specification and not to metadata.

A limits field directly under the spec section is wrong because limits must be nested inside each container's resources field under spec.containers. A top level limits entry under spec is not the correct place for per container requests and limits.

Full AWS Practitioner Certification Question