Examtopics

コメント(17)

• C, Agreed reference : https://cloud.google.com/compute/docs/tutorials/high-availability-autohealing

  Pro Tip: Use separate health checks for load balancing and for autohealing. Health checks for load balancing detect unresponsive instances and direct traffic away from them. Health checks for autohealing detect and recreate failed instances, so they should be less aggressive than load balancing health checks. Using the same health check for these services would remove the distinction between unresponsive instances and failed instances, causing unnecessary latency and unavailability for your users.

  👍 81

  ReyBan2020/05/04

• A. Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy(HTTP)

  This is a possible answer. This answer assumes that the existing backend is configured correctly.

  B. Create an HTTP load balancer with a backend configuration that references an existing instance group. Define a balancing mode and set the maximum RPS to 10.

  This is a possible answer. This answer assumes that the existing backend is configured correctly. This answer adds an additional step over answer A.

  C. Create a managed instance group. Set the Autohealing health check to healthy(HTTP)

  This is only a partial solution. The default configuration is auto scaling enabled. You still need to create the HTTP Load Balancer.

  D. Create a managed instance group. Verify that the auto scaling setting is on.

  This is only a partial solution. Creating a Managed Instance Group with Auto Scaling is required, but you still need to create the HTTP Load Balancer.

  Therefore the best answer is A in my opinion.

  👍 21

  bryanchew2020/04/04

• A is the right answer

  👍 2

  Suresh2905872022/12/02