Which OpenShift object enforces namespace-level resource usage limits?

Which OpenShift object enforces namespace-level resource usage limits?

• A. LimitRange
• B. PodSecurityPolicy
• C. ResourceQuota
• D. NetworkPolicy

Answer: (C)

Controlling resource usage within a namespace is done with a ResourceQuota. It’s defined at the namespace level and enforces limits on total resources like CPU, memory, storage, and the number of objects (pods, services, secrets, etc.) that can exist in that namespace. This prevents a single project from exhausting cluster resources and ensures fair sharing. In contrast, LimitRange sets per-pod defaults and constraints (like default CPU/memory requests or maximums) but doesn’t cap total namespace usage. PodSecurityPolicy governs pod security settings, not resource accounting, and NetworkPolicy controls network traffic, not resource quotas. So the object that enforces namespace-level resource usage limits is ResourceQuota.

Controlling resource usage within a namespace is done with a ResourceQuota. It’s defined at the namespace level and enforces limits on total resources like CPU, memory, storage, and the number of objects (pods, services, secrets, etc.) that can exist in that namespace. This prevents a single project from exhausting cluster resources and ensures fair sharing. In contrast, LimitRange sets per-pod defaults and constraints (like default CPU/memory requests or maximums) but doesn’t cap total namespace usage. PodSecurityPolicy governs pod security settings, not resource accounting, and NetworkPolicy controls network traffic, not resource quotas. So the object that enforces namespace-level resource usage limits is ResourceQuota.