Examkin

Soru

Zorluk: ZorPlanning Network Load Balancing, Cloud DNS, and Cloud CDN

A financial technology company is planning the networking architecture on Google Cloud for two distinct backend services running on Compute Engine instances:

1. External edge sensors transmit non-HTTP raw TCP traffic over the internet and require the backend instances to inspect the original client IP address directly.
2. Internal microservices execute high-throughput RPC operations over TCP between instances located in the same Virtual Private Cloud (VPC) network.

Which TWO load balancing solutions should the cloud engineer select to satisfy these architecture requirements? (Select TWO.)

  1. Deploy an External Passthrough Network Load Balancer for the external edge sensor traffic.Cevap
  2. Deploy an Internal Passthrough Network Load Balancer for the internal RPC microservice traffic.Cevap
  3. C
    Deploy an External Application Load Balancer for the external edge sensor traffic.
  4. D
    Configure Cloud CDN attached to the Internal Passthrough Network Load Balancer to cache RPC response packets.

Cevap

Select the External Passthrough Network Load Balancer for external raw TCP traffic requiring client IP preservation, and select the Internal Passthrough Network Load Balancer for internal high-throughput TCP RPC traffic within the VPC network.
For external non-HTTP raw TCP traffic that requires preserving client source IP addresses, an External Passthrough Network Load Balancer is the correct Layer 4 choice because packets are routed directly to backend instances without proxy termination. For internal TCP-based RPC traffic between instances in the same VPC, an Internal Passthrough Network Load Balancer delivers low-latency, high-throughput private Layer 4 load balancing.

Adım Adım Çözüm

1
Analyze the protocol and client IP requirements for the external workload.
The external workload uses non-HTTP raw TCP traffic and requires client source IP preservation.
Proxy load balancers (like External Application or SSL Proxy Load Balancers) terminate TCP connections and substitute source IPs unless HTTP headers or PROXY protocol are supported. An External Passthrough Network Load Balancer directly routes packets to backends while preserving original IP headers.
2
Analyze the networking boundary and protocol requirements for the internal workload.
The internal workload requires low-latency, high-throughput RPC over TCP between Compute Engine instances inside the VPC.
An Internal Passthrough Network Load Balancer provides private, regional Layer 4 load balancing natively within GCP VPC networks.
3
Verify service compatibility for Cloud CDN and L7 proxies against the requirements.
Reject options utilizing Layer 7 proxies or Cloud CDN for non-HTTP raw TCP and internal Layer 4 traffic.
Cloud CDN and Application Load Balancers operate strictly at Layer 7 (HTTP/HTTPS).

Anahtar Kavram

GCP Network Load Balancer Selection Matrix based on Layer 4 vs Layer 7, Public vs Internal scope, and client IP preservation.
Bu soruyu puanla

Konular

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

Bu konudan daha fazla soru