A healthcare enterprise is designing a network architecture on Google Cloud to receive high-throughput medical imaging telemetry transmitted via a non-HTTP raw TCP protocol from external hospital networks across the public internet. The solution must terminate TLS/SSL encryption at the load balancing tier, support Server Name Indication (SNI) to route requests to appropriate backend Compute Engine instance groups, and scale across multiple regions. Which Google Cloud load balancer architecture should be planned to satisfy these requirements?
- Global External Proxy Network Load Balancer configured with a Target SSL Proxy frontendAnswer
- BExternal Passthrough Network Load Balancer configured with a backend service and health checks
- CGlobal External Application Load Balancer configured with HTTPS target proxies and URL maps
- DInternal Passthrough Network Load Balancer configured with a global access enabling flag
Answer
Global External Proxy Network Load Balancer configured with a Target SSL Proxy frontend
The Global External Proxy Network Load Balancer utilizing a Target SSL Proxy is specifically designed for non-HTTP TCP traffic that requires TLS offloading at the Google edge. It supports Server Name Indication (SNI), enabling multiple SSL certificates on a single IP address, and can route traffic to backend instance groups across multiple Google Cloud regions.
Step-by-Step Solution
Key Concept
Selecting GCP Load Balancers Based on Protocol, SSL Offloading, and Traffic Scope
Estimated Time:2m 0s