What does a resource quota limit in Kubernetes?

Correct answer: The total resources a namespace can consume

Option C is correct because a ResourceQuota object in Kubernetes is applied at the namespace level and enforces aggregate limits on total CPU, memory, storage, and object counts that all pods and objects within that namespace can collectively consume, preventing any single team or workload from exhausting cluster resources. Option A is wrong because container image counts in a registry are managed by the registry itself, such as Docker Hub or a private registry, and are entirely outside the scope of Kubernetes ResourceQuota. Option B is wrong because a node's physical or allocated storage capacity is a property of the node and the underlying infrastructure, not something controlled by a namespace-scoped ResourceQuota. Option D is wrong because per-pod CPU and memory limits are set by LimitRange objects or by individual container resource requests and limits fields, not by ResourceQuota, which operates at the aggregate namespace level rather than at the individual pod level.