Examkin

Soru

Zorluk: Çok zorManaging Compute Engine Resources

An e-commerce platform relies on a Compute Engine Managed Instance Group (MIG) to serve dynamic web traffic. During high-volume flash sales, incoming load surges rapidly. The application binary deployed on each virtual machine requires approximately 4 minutes to load configuration files and warm up local caches before it can successfully process requests. However, the MIG autoscaler currently evaluates metrics continuously and provisions additional virtual machines every 60 seconds, creating significantly more instances than required and causing regional CPU quota exhaustion errors. Which operational adjustment should you make to stabilize the autoscaling behavior?

  1. Set the autoscaler cool-down period (initialization period) to at least 240 seconds so the MIG waits for newly created instances to complete startup before evaluating scaling metrics again.Cevap
  2. B
    Reconfigure the MIG autoscaling policy to scale based on a custom Cloud Monitoring latency metric while setting the scale-in control period to zero seconds.
  3. C
    Update the Managed Instance Group instance template to utilize Spot virtual machines so that sudden traffic spikes automatically bypass regional CPU quota limits.
  4. D
    Provision an identical Managed Instance Group in a neighboring zone within the same VPC network to automatically double the project's regional CPU quota limits.

Cevap

Configure the cool-down period (initialization period) of the Managed Instance Group autoscaler to at least 240 seconds (4 minutes) to account for application warm-up time.
The correct option is setting the autoscaler cool-down period to at least 240 seconds. When virtual machines require time to initialize and warm up caches, the autoscaler must ignore their metric contributions during that period. Setting the cool-down period to match the 4-minute application startup time prevents the MIG from over-provisioning instances while waiting for existing new instances to become ready.

Adım Adım Çözüm

1
Analyze the operational issue causing instance over-provisioning.
The application takes 4 minutes (240 seconds) to warm up, but the autoscaler evaluates CPU load every 60 seconds. Unready instances cannot accept load, causing high average CPU utilization across existing ready instances and triggering unnecessary scale-out actions.
Autoscaling metrics must account for instance startup and initialization time.
2
Identify the Google Cloud Compute Engine MIG configuration parameter designed to address application warm-up delays.
The cool-down period (also known as the initialization period) specifies how long the autoscaler should wait after a new instance is started before including its metric data in scaling decisions.
Setting cool-down ≥240\ge 240 seconds ensures metrics from booting instances are ignored until they are fully functional.
3
Evaluate alternative choices against Google Cloud operational best practices.
Changing metrics without warm-up delays, switching to Spot VMs, or adding zonal MIGs fails to resolve the metric timing issue and violates quota management procedures.
Only adjusting the initialization cool-down directly fixes the metric misconfiguration cause.

Anahtar Kavram

Compute Engine Managed Instance Group Autoscaler Cool-Down Period
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Managing Compute Engine Resources

Bu konudan daha fazla soru