Bird
0
0

Why does Kubernetes enforce ResourceQuota limits based on resource requests rather than actual usage?

hard📝 Conceptual Q10 of 15
Kubernetes - Namespaces
Why does Kubernetes enforce ResourceQuota limits based on resource requests rather than actual usage?
AActual usage is not measurable by Kubernetes
BRequests are guaranteed resources, so quotas prevent overcommitment
CRequests are easier to configure than limits
DResourceQuota only applies to limits, not requests
Step-by-Step Solution
Solution:

  1. Step 1: Understand resource requests vs actual usage

    Requests reserve resources for pods, ensuring guaranteed minimums.

  2. Step 2: Reason why quotas use requests

    Using requests prevents cluster overcommitment by limiting guaranteed resource reservations.

  3. Final Answer:

    Requests are guaranteed resources, so quotas prevent overcommitment -> Option B

  4. Quick Check:

    Quotas limit requests to avoid overcommitment = B [OK]
Quick Trick: Quotas limit requests to guarantee resource availability [OK]
Common Mistakes:
  • Thinking actual usage is unmeasurable
  • Confusing requests with limits
  • Believing quotas apply only to limits

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - kubectl CLI installation and configuration - Quiz 4medium Pods - Why Pods are the smallest deployable unit - Quiz 13medium Pods - Sidecar container pattern - Quiz 14medium Pods - Multi-container Pods concept - Quiz 15hard Pods - Pod lifecycle states - Quiz 14medium ReplicaSets and Deployments - Deployment as higher-level abstraction - Quiz 7medium kubectl Essential Commands - kubectl explain for API reference - Quiz 1easy kubectl Essential Commands - kubectl exec for container access - Quiz 12easy kubectl Essential Commands - kubectl explain for API reference - Quiz 8hard kubectl Essential Commands - kubectl apply vs create - Quiz 12easy