An enterprise is designing a scalable, highly available compute infrastructure on Google Cloud for a stateless web service. The deployment must satisfy the following architectural requirements: All virtual machines (VMs) across multiple zones in a region must be provisioned with identical base hardware, security configurations, and operating system images. Newly launched VM instances must automatically install dependencies and initialize application services upon boot. Dynamic environment variables (such as backend API endpoints and environment tags) must be passed to instances without baking them into persistent disk images. The compute pool must automatically scale out during traffic spikes and self-heal failed instances. Which strategy should the architect implement to automate and standardize this resource configuration?

Define an instance template with the required machine specifications, attach a startup script and custom metadata key-value pairs, and use this template to configure a regional Managed Instance Group (MIG) with autoscaling.: ### What Instance Templates and Managed Instance Groups Are An **instance template** is an immutable Google Cloud resource used to define VM instance properties such as machine type, boot disk image, labels, network interfaces, service accounts, and metadata. A **regional Managed Instance Group (MIG)** uses this instance template to deploy, autoscale, and manage identical compute instances across multiple availability zones in a single region. ### How It Meets the Requirements - **Standardized Base Configuration**: The instance template enforces uniform compute hardware, base OS images, and IAM service accounts across all VMs deployed in the group. - **Automated Initialization**: The `startup-script` (or `startup-script-url`) metadata key instructs the Compute Engine guest agent to execute initialization tasks, install required dependencies, and launch runtime services upon boot. - **Dynamic Configuration Injection**: Custom instance **metadata key-value pairs** allow developers to pass dynamic configuration values (such as API endpoints and stage flags) that startup scripts or applications query via the local metadata server (`http://metadata.google.internal/computeMetadata/v1/`). - **Autoscaling and Self-Healing**: A regional MIG automatically provisions new instances during demand spikes and recreates unhealthy instances across zones. ### Key Advantages and Capabilities - **Immutable Configuration Management**: Prevents configuration drift by ensuring all VMs instantiate from the identical declarative template. - **Decoupled Architecture**: Keeps base disk images generic while parameterizing environments via metadata. - **High Availability**: Distributes instances automatically across multiple zones within the region. - **Automated Lifecycle Operations**: Supports rolling updates, canary deployments, and health-check driven auto-healing. ### Why This Is Optimal Using instance templates paired with regional MIGs is the foundational Google Cloud best practice for deploying stateless, autoscaling compute workloads, providing seamless lifecycle automation and configuration consistency.

StudyCerts

Standardize Mig Instance Templates Startup Metadata | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Standardize Mig Instance Templates Startup Metadata

Section: Infrastructure orchestration, resource configuration, and patch management

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise is designing a scalable, highly available compute infrastructure on Google Cloud for a stateless web service. The deployment must satisfy the following architectural requirements:

All virtual machines (VMs) across multiple zones in a region must be provisioned with identical base hardware, security configurations, and operating system images.
Newly launched VM instances must automatically install dependencies and initialize application services upon boot.
Dynamic environment variables (such as backend API endpoints and environment tags) must be passed to instances without baking them into persistent disk images.
The compute pool must automatically scale out during traffic spikes and self-heal failed instances.

Which strategy should the architect implement to automate and standardize this resource configuration?

Configure a single standalone virtual machine with all dependencies pre-installed, create an unmanaged instance group, and apply OS Config patch deployment policies to inject runtime parameters.

Define an instance template with the required machine specifications, attach a startup script and custom metadata key-value pairs, and use this template to configure a regional Managed Instance Group (MIG) with autoscaling.

Deploy standalone Compute Engine instances across individual zones using custom machine images, packaging initialization commands inside SSH public key comments and user metadata.

Provision a regional Managed Instance Group directly from a machine image, and use Cloud Run functions to intercept instance creation events and push runtime configuration files over SSH.

Professional Cloud Architect

Standardize Mig Instance Templates Startup Metadata

Related questions