
An internal Application Load Balancer is an HTTP and HTTPS load balancer that gets an internal IP address from one of your subnets, so only clients inside the VPC network can reach it. It runs health checks against its backend service and stops sending requests to unhealthy instances. A regional internal Application Load Balancer runs on Google-managed Envoy proxies that take their addresses from a dedicated proxy-only subnet, and by default it only accepts clients in its own region. For the Professional Cloud Network Engineer exam, the useful details are where this load balancer fits, what the proxy-only subnet requires, and how global access extends its reach.
The standard pattern for a multi-tier application pairs an external load balancer for the web tier with an internal Application Load Balancer for an HTTP middle tier. The internal load balancer keeps the middle tier private to the VPC network while still giving it health-checked distribution across its instances.
The two load balancers stay separate for a reason. Anything reachable through the external load balancer's frontend has a public entry point, so a tier that must stay private gets its own internal load balancer rather than another route through the external one.
The regional internal Application Load Balancer is built on Google-managed Envoy proxies, and those proxies need addresses of their own. They take them from a proxy-only subnet, which has a few requirements:
REGIONAL_MANAGED_PROXY.The proxies end each client connection and open a new one to the backend from a proxy-only subnet address. As a result, the backends never see the client VM addresses. Proxied client traffic reaches them from the proxy-only subnet range.
Because of that proxy design, the backends need firewall rules that admit two sources. The first is the Google health check ranges, 35.191.0.0/16 and 130.211.0.0/22, so the health check probes can reach the instances. The second is the proxy-only subnet range, so the proxied client traffic can reach them. If either source is missing, the backends stay unhealthy and receive no traffic.
An internal Application Load Balancer is a proxy, and that has three consequences:
By default, a regional internal load balancer only accepts traffic from clients in the same region as its forwarding rule. Turning on global access on the forwarding rule lets clients in other regions of the VPC network reach the existing internal IP address.
For a regional internal Application Load Balancer, the backend service, URL map, target proxy and forwarding rule all belong together in one region. Because the components cannot be split across regions, serving clients elsewhere in the VPC network is a setting on the forwarding rule rather than a redesign, and global access keeps the same load balancer type.
Global access is also separate from the VPC network's dynamic routing mode. The dynamic routing mode controls how Cloud Router shares learned routes across regions, such as routes received over VLAN attachments, while global access controls which regions' clients a regional internal load balancer accepts.
Global access also supports designs that survive the loss of a region. When a regional internal load balancer runs in each of two regions with global access enabled, clients in any region can reach either frontend. Cloud DNS routing policies with health checks can then steer clients to a healthy region, so the service keeps running if one region fails.
On the Professional Cloud Network Engineer exam, we would read an internal HTTP scenario in this order: confirm the traffic is HTTP or HTTPS and the source address does not need to stay in the IP header, check that a proxy-only subnet exists and that firewall rules admit both the health check ranges and the proxy-only range, and then decide whether clients outside the load balancer's region need global access.
Our Professional Cloud Network Engineer practice exams cover internal Application Load Balancers and proxy-only subnets alongside global access and load balancer health checks, with detailed explanations that drill these distinctions.