Associate Cloud Engineer ยท Compute Engine: choosing, launching and scaling
Instance templates and managed instance groups
Instance templates (immutable), zonal vs regional MIGs, autoscaling policies (CPU, load balancing, schedule), autohealing health checks, rolling updates.
Key points
- Instance template: immutable blueprint for VMs; to change settings, create a new template.
- Managed instance group (MIG): identical VMs from a template, zonal (one zone) or regional (across zones, better for resilience).
- Autoscaling: adds or removes VMs based on CPU, load balancer capacity or a schedule.
- Autohealing: recreates VMs that fail a health check.
- Rolling updates: move the group to a new template gradually.
Practice questions
Which statement describes an instance template?
- An immutable definition used to create VMs
- A running group of VMs that can be edited live
- A snapshot schedule for boot disks
- A load balancer rule that routes to VMs
Show answer
Answer: A. An immutable definition used to create VMs
Templates are immutable, so a change means creating a new template and updating the group. They are not editable in place and they do not hold running VMs.
Which signals can drive MIG autoscaling?
- Average CPU utilization
- Load balancer serving capacity
- A time-based schedule
- Number of disks attached
- The project billing budget
Show answer
Answer: A. Average CPU utilization, B. Load balancer serving capacity, C. A time-based schedule
CPU utilization, load balancing serving capacity and schedules are autoscaling inputs. Disk count and billing budget are not.
True or false: autoscaling and autohealing are the same feature.
Show answer
Answer: False
False. Autoscaling changes the number of VMs to match load. Autohealing recreates a VM that fails its health check.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
