A SaaS organization is designing a multi-tier solution on Google Cloud Compute Engine. The public web application requires HTTPS load balancing across multiple regions, acceleration of static website assets, and domain resolution. The internal backend service processes non-HTTP raw TCP streaming data from private VPC resources and requires preservation of client source IP addresses. Which TWO network architecture decisions should you recommend to fulfill these requirements?
- Deploy a Global External Application Load Balancer with Cloud CDN enabled on the backend service for the public web application.Answer
- Deploy an Internal Passthrough Network Load Balancer for the internal streaming backend service.Answer
- CDeploy an External Application Load Balancer for the internal streaming backend service to enable Layer 7 inspection of raw TCP data.
- DEnable Cloud CDN directly on the Internal Passthrough Network Load Balancer backend service to accelerate internal microservice responses.
Answer
The architecture should use a Global External Application Load Balancer with Cloud CDN for the web application and an Internal Passthrough Network Load Balancer for the internal raw TCP streaming service.
For public web traffic needing global HTTPS termination and caching, Global External Application Load Balancers with Cloud CDN are recommended. For internal VPC microservices handling raw TCP protocols that require client IP preservation, Internal Passthrough Network Load Balancers operate at Layer 4 and fulfill all requirements.
Step-by-Step Solution
Key Concept
Selecting GCP load balancers based on protocol layer (L4 vs L7), traffic scope (internal vs external), and Cloud CDN integration support.
Estimated Time:1m 30s