A financial services company is planning the Google Cloud networking architecture for a high-frequency telemetry service deployed on Compute Engine instances across two subnets in the us-central1 region. The service receives internal traffic originating from on-premises systems connected via Cloud Interconnect. The application uses a proprietary non-HTTP TCP protocol and strictly requires that backend instances receive the original client source IP address intact for security auditing. Which Google Cloud load balancer should you select to meet these technical requirements?
- Internal Passthrough Network Load BalancerAnswer
- BInternal Application Load Balancer
- CExternal Passthrough Network Load Balancer
- DRegional External Application Load Balancer
Answer
Internal Passthrough Network Load Balancer
The Internal Passthrough Network Load Balancer is a regional Layer 4 load balancer that handles internal TCP/UDP traffic within Google Cloud or connected on-premises networks via Cloud Interconnect. Because it is non-proxied (passthrough), it preserves the client's original source IP address in the packet header and supports non-HTTP TCP traffic.
Step-by-Step Solution
Key Concept
Selecting GCP Load Balancers based on Traffic Scope (Internal vs External), OSI Layer (L4 Passthrough vs L7 Proxy), and Client IP Preservation
Estimated Time:2m 0s