Bird
0
0

Identify the reason why this pod is classified as Burstable instead of Guaranteed:

medium📝 Debug Q7 of 15
Kubernetes - Resource Management
Identify the reason why this pod is classified as Burstable instead of Guaranteed:
resources:
  requests:
    cpu: '300m'
    memory: '256Mi'
  limits:
    cpu: '300m'
    memory: '256Mi'
  extra: 'value'
ACPU limits are less than requests
BRequests and limits are equal, so it should be Guaranteed
CMemory requests are missing
DThe presence of an unsupported 'extra' field in resources
Step-by-Step Solution
Solution:
  1. Step 1: Check resource requests and limits

    CPU and memory requests and limits are equal, which normally qualifies for Guaranteed.
  2. Step 2: Identify invalid fields

    The 'extra' field is not valid under resources and causes the pod spec to be invalid or ignored for QoS classification.
  3. Step 3: Effect on QoS classification

    Due to the invalid field, Kubernetes falls back to Burstable QoS.
  4. Final Answer:

    The presence of an unsupported 'extra' field in resources -> Option D
  5. Quick Check:

    Invalid resource fields cause fallback to Burstable [OK]
Quick Trick: Invalid resource fields cause Burstable, not Guaranteed [OK]
Common Mistakes:
  • Ignoring invalid fields in resource spec
  • Assuming equal requests and limits always guarantee Guaranteed class
  • Confusing missing requests with invalid fields

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes