QuestionQ8

Designing scalable, available, and reliable cloud-native applications

You configured your Compute Engine instance group to autoscale based on overall CPU utilization. However, your application's response latency rises sharply before the cluster has completed adding instances. You want to deliver a more consistent latency experience to end users by modifying the instance group autoscaler configuration.

Which two configuration changes should you make?

Choose two
  • A Add the label ג€AUTOSCALEג€ to the instance group template.
  • B Decrease the cool-down period for instances added to the group.
  • C Increase the target CPU usage for the instance group autoscaler.
  • D Decrease the target CPU usage for the instance group autoscaler.
  • E Remove the health-check for individual VMs in the instance group.
Explanation

A lower CPU utilization target makes a Compute Engine managed instance group scale out before the existing instances are as heavily loaded, preserving capacity headroom and helping prevent latency spikes. The initialization (formerly cool-down) period controls how long the autoscaler ignores utilization data from newly created VMs during scale-out; reducing an unnecessarily long period allows those instances to contribute to autoscaling decisions sooner.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!