QuestionQ3

Designing and planning a cloud solution architecture

You have an application that will run on Compute Engine. You must design an architecture that accounts for a disaster recovery plan requiring the application to fail over to another region if a regional outage occurs. What should you do?

  • A Deploy the application on two Compute Engine instances in the same project but in a different region. Use the first instance to serve traffic, and use the HTTP load balancing service to fail over to the standby instance in case of a disaster.
  • B Deploy the application on a Compute Engine instance. Use the instance to serve traffic, and use the HTTP load balancing service to fail over to an instance on your premises in case of a disaster.
  • C Deploy the application on two Compute Engine instance groups, each in the same project but in a different region. Use the first instance group to serve traffic, and use the HTTP load balancing service to fail over to the standby instance group in case of a disaster.
  • D Deploy the application on two Compute Engine instance groups, each in a separate project and a different region. Use the first instance group to serve traffic, and use the HTTP load balancing service to fail over to the standby instance group in case of a disaster.
Explanation

A global HTTP load balancer can distribute traffic across backend instance groups in multiple regions and automatically direct traffic to a healthy region when the primary region becomes unavailable. Using one Compute Engine instance group per region provides independent, scalable application backends for regional disaster recovery. The backend groups should be in the same project for the standard configuration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!