Where in a Deployment manifest should a developer place container CPU and memory requests so every replica inherits them?
Select an answer to reveal the explanation.
![To Create an exciting colorful infographic that explains the concepts in the question: Question: Where in a Deployment manifest should a developer place container CPU and memory requests so every replica inherits them? Correct Answer: Under each container in spec.template.spec.containers[].resources within the Pod template. Put EVERY visible label in double quotes. No people. No A/B/C/D letters. In one of the four corners put a little "Navy Duck".](/media/cncf/ckad/CKAD-e1-q210-infographic.webp)
Short Explanation
Replicas clone the Pod template like cookie-cutter dough—resources belong in that mold. Put requests under each container inside spec.template.spec. Strategy blocks and labels don't feed the scheduler's reservation math.
Full Explanation
Deployment-managed Pods take their container specs from spec.template. Resource requests and limits must be set on each container under that Pod template so every replica receives them. RollingUpdate strategy fields, Deployment labels, and LimitRanges (namespace defaults/constraints) are not substitutes for explicitly defining resources in the template when you need specific values.