
Answer-first summary for fast verification
Answer: Change the load balancer frontend configuration to use the Premium Tier network, and add the new instance group.
The correct answer is B because Google Cloud Load Balancing's Premium Tier is required for cross-region load balancing. In Standard Tier, backends must be in the same region as the forwarding rule, which prevents distributing traffic to us-east1 from the existing us-central1 load balancer. By upgrading to Premium Tier, the load balancer becomes global, allowing a single external IP address to distribute traffic across multiple regions. The community discussion strongly supports this with 100% consensus on B, citing Google's documentation that explicitly states Premium Tier enables backends in any region, while Standard Tier restricts backends to the same region. Other options are less suitable: A (using NEGs) doesn't solve the cross-region limitation of Standard Tier; C (creating a new Standard Tier load balancer) would require multiple IP addresses and wouldn't provide a single global endpoint; D (Cloud VPN with Private Access) is for private connectivity, not public load balancing across regions.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your company has an application instance group deployed behind a Google Cloud load balancer in the us-central1 region using the Standard Tier network service tier. The infrastructure team plans to expand to a second region, us-east1. You need to configure a single external IP address to distribute new connections to the instance groups in both regions.
What should you do?
A
Change the load balancer backend configuration to use network endpoint groups instead of instance groups.
B
Change the load balancer frontend configuration to use the Premium Tier network, and add the new instance group.
C
Create a new load balancer in us-east-2 using the Standard Tier network, and assign a static external IP address.
D
Create a Cloud VPN connection between the two regions, and enable Google Private Access.
No comments yet.