An organization is designing the Google Cloud networking architecture for a two-tier application deployed on Compute Engine instances. The architecture has two primary traffic requirements:
1. A public-facing web frontend accepting external HTTPS requests from internet clients with a requirement to cache static media assets at edge locations.
2. An internal backend microservice communicating via raw TCP with other internal workloads in the same Virtual Private Cloud (VPC), requiring strict preservation of client source IP addresses.
Which TWO load balancing solutions should the organization select to meet these requirements?
- Deploy a Global External Application Load Balancer with Cloud CDN enabled for the frontend web tier.Cevap
- Deploy an Internal Passthrough Network Load Balancer for the internal backend microservice tier.Cevap
- CDeploy an Internal Application Load Balancer with Cloud CDN enabled for the frontend web tier.
- DDeploy an External Proxy Network Load Balancer for the internal backend microservice tier.
Cevap
The architecture requires a Global External Application Load Balancer with Cloud CDN enabled for the public frontend, and an Internal Passthrough Network Load Balancer for the internal TCP backend service.
To satisfy public HTTPS traffic and static media edge caching, a Global External Application Load Balancer with Cloud CDN is required. To satisfy internal VPC TCP traffic while preserving original client source IP addresses, an Internal Passthrough Network Load Balancer is the correct architectural choice because passthrough load balancers do not terminate TCP connections.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Load Balancers based on traffic scope (internal vs. external), OSI layer (L4 vs. L7), Cloud CDN compatibility, and client IP preservation requirements.