A company has deployed a Global External HTTP(S) Load Balancer with a backend service that points to an instance group in us-central1. The load balancer's frontend uses a reserved static external IP address. Users in Europe report high latency, while users in Asia cannot reach the application at all. The application works fine when accessed directly via the instance group's internal IPs from within us-central1. Which action should be taken to resolve the issue?
Trap 1: Enable Cloud CDN on the backend service to cache content closer to…
Incorrect. Cloud CDN caches static content at edge locations, but it does not address connectivity issues or high latency for dynamic content. The application may not be cacheable, and CDN does not change the backend location.
Trap 2: Configure a DNS A record for the load balancer's IP address with a…
Incorrect. Configuring a DNS A record with a low TTL does not affect the load balancer's routing or backend location. It only controls how quickly DNS changes propagate.
Trap 3: Ensure the backend service's 'Enable Global Access' checkbox is…
Incorrect. The 'Enable Global Access' checkbox is a setting for Internal Load Balancers, not for Global External HTTP(S) Load Balancers. It is not applicable here.
- A
Change the load balancer to a regional load balancer and deploy additional instance groups in other regions.
Correct. Changing to a regional load balancer and deploying additional instance groups in other regions reduces latency and allows users in Asia to reach a local backend. This ensures global performance and availability.
- B
Enable Cloud CDN on the backend service to cache content closer to users.
Why wrong: Incorrect. Cloud CDN caches static content at edge locations, but it does not address connectivity issues or high latency for dynamic content. The application may not be cacheable, and CDN does not change the backend location.
- C
Configure a DNS A record for the load balancer's IP address with a low TTL.
Why wrong: Incorrect. Configuring a DNS A record with a low TTL does not affect the load balancer's routing or backend location. It only controls how quickly DNS changes propagate.
- D
Ensure the backend service's 'Enable Global Access' checkbox is selected in the instance group's network settings.
Why wrong: Incorrect. The 'Enable Global Access' checkbox is a setting for Internal Load Balancers, not for Global External HTTP(S) Load Balancers. It is not applicable here.