ASSOCIATE-CLOUD-ENGINEER Question #34: Real Exam Question with Answer & Explanation

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

Explanation

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.

Common mistakes.

• A. 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.
• B. The question explicitly states that autoscaling is enabled and configured, contradicting the idea that it's inactive.
• D. Option C provides a valid and technically correct reason for the observed autoscaling behavior.

Concept tested. Google Cloud MIG autoscaling metric aggregation

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

No community discussion yet for this question.