Google Cloud Compute Engine: Provisioning Instances for High Availability and Autoscaling

Provisioning Instances for High Availability and Autoscaling

Question

You have deployed a proof-of-concept application by manually placing instances in a single Compute Engine zone.

You are now moving the application to production, so you need to increase your application availability and ensure it can autoscale.

How should you provision your instances?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B.

https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups

When moving an application to production, it is important to ensure high availability and scalability. One way to achieve this is by using managed instance groups and load balancing. Here is a detailed explanation of each of the answers:

A. Create a single managed instance group, specify the desired region, and select Multiple zones for the location.

This option involves creating a managed instance group in a specific region and selecting multiple zones for the location. This means that instances will be automatically distributed across multiple zones in the region, which improves availability and reduces the risk of downtime due to a single zone failure. In addition, managed instance groups support autoscaling, which means that instances can be automatically added or removed based on demand. This allows the application to handle increased traffic without manual intervention.

B. Create a managed instance group for each region, select Single zone for the location, and manually distribute instances across the zones in that region.

This option involves creating a managed instance group for each region, selecting a single zone for the location, and manually distributing instances across the zones in that region. This option provides some level of availability, but it requires manual intervention to ensure that instances are evenly distributed across zones. In addition, this option does not support autoscaling across multiple regions.

C. Create an unmanaged instance group in a single zone, and then create an HTTP load balancer for the instance group.

This option involves creating an unmanaged instance group in a single zone and then creating an HTTP load balancer for the instance group. This option provides some level of availability, but it requires manual intervention to ensure that instances are evenly distributed across the zone. In addition, unmanaged instance groups do not support autoscaling, which means that additional instances need to be manually added as demand increases.

D. Create an unmanaged instance group for each zone, and manually distribute the instances across the desired zones.

This option involves creating an unmanaged instance group for each zone and manually distributing the instances across the desired zones. This option provides some level of availability, but it requires manual intervention to ensure that instances are evenly distributed across zones. In addition, unmanaged instance groups do not support autoscaling, which means that additional instances need to be manually added as demand increases.

In conclusion, option A is the best choice for ensuring high availability and scalability. It involves creating a managed instance group in a specific region, selecting multiple zones for the location, and enabling autoscaling. This allows the application to handle increased traffic without manual intervention and provides automatic failover in case of zone failure.