Bird
0
0

Why might an HPA fail to scale pods even if CPU usage is above the target and metrics are available?

hard📝 Conceptual Q10 of 15
Microservices - Orchestration with Kubernetes
Why might an HPA fail to scale pods even if CPU usage is above the target and metrics are available?
AThe maximum replicas limit has been reached
BThe pods are running on nodes with high memory
CThe HPA minReplicas is set too low
DThe Deployment uses a Recreate update strategy
Step-by-Step Solution
Solution:

  1. Step 1: Check scaling limits

    HPA cannot scale beyond maxReplicas even if load is high.

  2. Step 2: Understand impact of maxReplicas

    If maxReplicas is reached, no further scaling occurs despite CPU usage.

  3. Final Answer:

    The maximum replicas limit has been reached -> Option A

  4. Quick Check:

    Scaling stops at maxReplicas limit [OK]
Quick Trick: HPA respects maxReplicas limit even on high load [OK]
Common Mistakes:
MISTAKES
  • Confusing memory with CPU scaling
  • Thinking minReplicas affects scale-up limit
  • Assuming update strategy blocks scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Authentication and Authorization - OAuth 2.0 for microservices - Quiz 15hard Authentication and Authorization - Why security spans all services - Quiz 14medium Event-Driven Architecture - Idempotent event consumers - Quiz 2easy Monitoring and Observability - Centralized logging (ELK stack) - Quiz 3easy Monitoring and Observability - Alerting strategies - Quiz 2easy Orchestration with Kubernetes - Liveness and readiness probes - Quiz 1easy Resilience Patterns - Timeout pattern - Quiz 12easy Resilience Patterns - Health check pattern - Quiz 8hard Service Mesh - Traffic management (routing, splitting) - Quiz 2easy Service Mesh - Linkerd overview - Quiz 4medium