Global Load Balancing Solution for Reliable Operations and In-Transit Encryption | WebsiteName

Global Load Balancing Solution

Question

You need to design a solution for global load balancing based on the URL path being requested.

You need to ensure operations reliability and end-to-end in- transit encryption based on Google best practices.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B.

https://cloud.google.com/load-balancing/docs/https/url-map

For global load balancing based on the URL path being requested, and ensuring operational reliability and end-to-end in-transit encryption based on Google best practices, the recommended approach is to use the HTTPS load balancer with URL maps. Therefore, option B is the correct answer.

Here's a detailed explanation for each option:

A. Create a cross-region load balancer with URL Maps: This option involves creating a load balancer that distributes traffic across multiple regions. While this approach can help with availability and performance, it does not provide end-to-end in-transit encryption based on Google best practices.

B. Create an HTTPS load balancer with URL Maps: This option involves creating a load balancer that supports HTTPS traffic and URL-based routing. HTTPS provides end-to-end encryption between the client and the load balancer, and URL-based routing can route traffic to the appropriate backend service based on the URL path being requested. This option is recommended by Google for global load balancing with end-to-end encryption.

C. Create appropriate instance groups and instances. Configure SSL proxy load balancing: This option involves creating instance groups and instances and using SSL proxy load balancing to distribute traffic. While SSL proxy load balancing can provide encryption between the client and load balancer, it does not provide end-to-end encryption to the backend services.

D. Create a global forwarding rule. Configure SSL proxy load balancing: This option involves creating a global forwarding rule and using SSL proxy load balancing to distribute traffic. Like option C, SSL proxy load balancing can provide encryption between the client and load balancer, but it does not provide end-to-end encryption to the backend services.

In summary, the best option to achieve global load balancing based on the URL path being requested and ensuring operational reliability and end-to-end in-transit encryption based on Google best practices is to create an HTTPS load balancer with URL Maps.