A gaming company's leaderboard API on GKE handles 10k RPS normally but fails during tournament events with 100k RPS. The team already uses horizontal pod autoscaling. What additional change addresses the traffic spike?
-
A
Pre-scale the deployment before the event and configure cluster autoscaler with surge nodes
-
B
Switch from GKE Standard to GKE Autopilot
-
C
Increase pod CPU limits to reduce throttling
-
D
Add a Redis cache in front of the leaderboard database