What should you do?

You are hosting an application from Compute Engine virtual machines (VMs) in usCcentral1Ca. You want to adjust your design to support the failure of a single Compute Engine zone, eliminate downtime, and minimize cost.

What should you do?
A . C Create Compute Engine resources in usCcentral1Cb.
CBalance the load across both usCcentral1Ca and usCcentral1Cb.
B . C Create a Managed Instance Group and specify usCcentral1Ca as the zone.
CConfigure the Health Check with a short Health Interval.
C . C Create an HTTP(S) Load Balancer.
CCreate one or more global forwarding rules to direct traffic to your VMs.
D . C Perform regular backups of your application.
CCreate a Cloud Monitoring Alert and be notified if your application becomes unavailable.
CRestore from backups when notified.

Answer: A

Explanation:

Choosing a region and zone You choose which region or zone hosts your resources, which controls where your data is stored and used. Choosing a region and zone is important for several reasons:

Handling failures

Distribute your resources across multiple zones and regions to tolerate outages. Google designs zones to be independent from each other: a zone usually has power, cooling, networking, and control planes that are isolated from other zones, and most single failure events will affect only a single zone. Thus, if a zone becomes unavailable, you can transfer traffic to another zone in the same region to keep your services running. Similarly, if a region experiences any disturbances, you should have backup services running in a different region. For more information about distributing your resources and designing a robust system, see Designing Robust Systems. Decreased network latency To decrease network latency, you might want to choose a region or zone that is close to your point of service. https://cloud.google.com/compute/docs/regions-zones#choosing_a_region_and_zone