A media streaming provider is preparing for a live sports event expected to cause a 10x traffic surge on its I/O-bound metadata API service, which is deployed on Compute Engine Managed Instance Groups (MIGs). During previous high-traffic events, the service experienced request timeouts because CPU-based autoscaling reacted too slowly to memory and network connection bottlenecks, and automated scaling requests were blocked by regional compute resource limits. Which TWO actions should you take to optimize capacity planning and ensure seamless workload scaling during the upcoming event?
- Configure the Managed Instance Group (MIG) autoscaling policy to scale based on Cloud Monitoring custom metrics such as active HTTP connections or queue depth, and proactively request regional Compute Engine quota increases ahead of the event.Cevap
- Implement scheduled scaling policies on the Managed Instance Groups to pre-provision baseline instance capacity prior to the expected event start time.Cevap
- CMigrate the stateless API microservice to a multi-region Google Kubernetes Engine (GKE) enterprise cluster to automatically bypass regional compute quota constraints.
- DMaintain MIG autoscaling based strictly on average CPU utilization while relying on automated system quota scaling during peak traffic hours.
Cevap
To optimize capacity planning and scaling, you should configure MIG autoscaling based on custom I/O metrics while submitting proactive regional quota increase requests, and set up scheduled scaling policies to pre-provision capacity before the event starts.
The combination of using relevant custom metrics (active HTTP connections/queue depth) for I/O-bound workloads, proactively requesting regional compute quota increases, and using scheduled scaling policies to pre-warm instance groups effectively addresses both latency response delays and quota capacity exhaustion during planned peak events.
Adım Adım Çözüm
Anahtar Kavram
Capacity Planning and Workload Autoscaling Optimization