Where do you specify per-container CPU and memory requests and limits?

Where do you specify per-container CPU and memory requests and limits?

• A. In the Pod's annotations
• B. In the containers' resources field (requests and limits)
• C. In the Node's capacity
• D. In the Pod security policy

Answer: (D)

The per-container CPU and memory requests and limits are defined in the container's resources field inside the Pod spec. For each container, you specify a resources block with requests (the guaranteed minimum) and limits (the maximum the container may use). The scheduler uses these requests to place the Pod on a node with enough capacity, and the kubelet enforces the limits at runtime. Metadata like annotations and security policies don’t set per-container resources—the node’s total capacity is about the whole node, not individual containers, and security policies govern access and security controls rather than resource sizing. In OpenShift/Kubernetes you can also rely on LimitRange for namespace-wide defaults, but the explicit per-container values live in the containers[].resources section.

The per-container CPU and memory requests and limits are defined in the container's resources field inside the Pod spec. For each container, you specify a resources block with requests (the guaranteed minimum) and limits (the maximum the container may use). The scheduler uses these requests to place the Pod on a node with enough capacity, and the kubelet enforces the limits at runtime. Metadata like annotations and security policies don’t set per-container resources—the node’s total capacity is about the whole node, not individual containers, and security policies govern access and security controls rather than resource sizing. In OpenShift/Kubernetes you can also rely on LimitRange for namespace-wide defaults, but the explicit per-container values live in the containers[].resources section.