nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #34

You're working for a company as a Cloud engineer. You have a managed instance group for which the autoscaling is enabled if CPU utilization is 70%. Right now there are 4 instances available in this in

The correct answer is C. Average CPU usage of the instance group is less than 70%. The question asks for the reason why an autoscaling managed instance group (MIG) isn't scaling out, even though one instance exceeds the CPU threshold.

Submitted by carter_n· Mar 30, 2026Ensuring successful operation of a cloud solution

Question

You're working for a company as a Cloud engineer. You have a managed instance group for which the autoscaling is enabled if CPU utilization is 70%. Right now there are 4 instances available in this instance group. When you connect to one of the instance, you see that the CPU utilization is 75% and there is no new instance is started in the group. What could be the possible reason for not starting another instance here?

Options

  • AIt will take 60 seconds to launch a new instance
  • BAutoscaling is not active
  • CAverage CPU usage of the instance group is less than 70%
  • DNone of the above

How the community answered

(40 responses)
  • A
    5% (2)
  • B
    8% (3)
  • C
    73% (29)
  • D
    15% (6)

Why each option

The question asks for the reason why an autoscaling managed instance group (MIG) isn't scaling out, even though one instance exceeds the CPU threshold.

AIt will take 60 seconds to launch a new instance

While instance launch takes time, the problem implies the autoscaler hasn't been triggered to *start* a new instance yet, not that one is in the process of launching.

BAutoscaling is not active

The question explicitly states that autoscaling is enabled and configured, contradicting the idea that it's inactive.

CAverage CPU usage of the instance group is less than 70%Correct

Google Cloud autoscaling for Managed Instance Groups based on CPU utilization typically aggregates the metric across all instances in the group; therefore, if the average CPU usage of the entire group remains below the 70% threshold, new instances will not be launched, even if a single instance is overloaded.

DNone of the above

Option C provides a valid and technically correct reason for the observed autoscaling behavior.

Concept tested: Google Cloud MIG autoscaling metric aggregation

Source: https://cloud.google.com/compute/docs/instance-groups/creating-groups-of-vms#autoscaling_instance_groups

Topics

#managed instance group#autoscaling#average CPU utilization#scaling policy

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full ASSOCIATE-CLOUD-ENGINEER Practice