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!
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise is implementing an automated provisioning and elasticity strategy using Terraform to deploy a mission-critical, stateless serving workload across multiple Google Cloud regions. The deployment must satisfy the following architectural requirements:
Which configuration should you define in your Terraform templates to achieve this architecture?
Define a global google_compute_instance_template, deploy a google_compute_region_instance_group_manager in each region configured with an ANY_SINGLE_ZONE distribution shape, and attach a google_compute_region_autoscaler.
Define a global google_compute_instance_template, deploy a google_compute_region_instance_group_manager in each region with an EVEN target distribution shape and an application health check autohealing policy, and attach a google_compute_region_autoscaler.
Define separate zonal google_compute_instance_template resources per zone, create individual zonal google_compute_instance_group_manager resources in each zone, and attach individual google_compute_autoscaler resources.
Define a global google_compute_instance_template, deploy a stateful google_compute_region_instance_group_manager in each region configured with stateful disks, and attach a google_compute_region_autoscaler to manage scaling.
Define a global google_compute_instance_template, deploy a google_compute_region_instance_group_manager in each region configured with an ANY_SINGLE_ZONE distribution shape, and attach a google_compute_region_autoscaler.
Define a global google_compute_instance_template, deploy a google_compute_region_instance_group_manager in each region with an EVEN target distribution shape and an application health check autohealing policy, and attach a google_compute_region_autoscaler.
A regional Managed Instance Group (MIG) manages homogeneous Compute Engine virtual machine instances across multiple zones within a single region. The group's VM configuration, including machine type, boot disk image, network settings, and startup metadata, is defined using a global instance template. Elasticity and resilience are managed by coupling the regional MIG manager with a regional autoscaler and an application autohealing policy.
StudyCerts
StudyCertsEVEN guarantees that instance counts across selected zones do not differ by more than one instance, ensuring adequate failover capacity during a zonal outage.google_compute_region_autoscaler allows the group to scale out or in dynamically based on metrics such as CPU utilization while respecting the EVEN multi-zone distribution shape.This pattern represents the Google Cloud architectural best practice for stateless, high-availability web tiers. Regional MIGs combined with EVEN distribution shapes, regional autoscaling, and dedicated autohealing health checks deliver multi-zone fault tolerance and zero-touch elasticity natively.
Define separate zonal google_compute_instance_template resources per zone, create individual zonal google_compute_instance_group_manager resources in each zone, and attach individual google_compute_autoscaler resources.
Define a global google_compute_instance_template, deploy a stateful google_compute_region_instance_group_manager in each region configured with stateful disks, and attach a google_compute_region_autoscaler to manage scaling.