Explanation:
The Network Load Balancer (NLB) is a regional Layer 4 load balancer, meaning traffic from Asia must traverse long distances to reach the us-central1 backend, causing high latency. The HTTP(S) Load Balancer (Option B) is a global Layer 7 load balancer. It uses Google's global frontend infrastructure to terminate user connections closer to their location (e.g., in Asia) and routes traffic over Google's optimized backbone network to the us-central1 backend. This reduces latency compared to a direct regional NLB setup. Policy-based routes (A) and Dynamic Routing (C) do not address cross-region latency. Reducing DNS TTL (D) affects DNS update speed, not latency.
Ultimate access to all questions.
To reduce latency for users in Asia accessing your web application currently hosted in us-central1, you've configured a network load balancer without performance improvement. What is the recommended solution?
A
Configure a policy-based route rule to prioritize the traffic.
B
Configure an HTTP load balancer, and direct the traffic to it.
C
Configure Dynamic Routing for the subnet hosting the application.
D
Configure the TTL for the DNS zone to decrease the time between updates.
No comments yet.