Examkin

Soru

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

An enterprise is planning the networking architecture for an enterprise resource planning (ERP) platform deployed on Compute Engine. The public-facing frontend tier relies on a Global External Application Load Balancer integrated with Cloud CDN. The architecture team must now select a load balancer for an internal backend service hosted on Compute Engine instances across multiple zones in the europe-west1 region. This internal microservice receives high-volume, non-HTTP raw TCP traffic on a custom port from other VPC workloads. The load balancing solution must provide maximum performance without terminating TCP connections, while preserving the original internal client IP addresses. Which load balancing solution should you select?

  1. An Internal Passthrough Network Load Balancer in the europe-west1 regionCevap
  2. B
    An Internal Application Load Balancer in the europe-west1 region
  3. C
    An External Proxy Network Load Balancer
  4. D
    A Regional External Application Load Balancer

Cevap

Select an Internal Passthrough Network Load Balancer in the europe-west1 region.
The correct architecture requires an Internal Passthrough Network Load Balancer because it operates at Layer 4 for internal VPC traffic, supports arbitrary non-HTTP raw TCP protocols, does not terminate TCP connections, and preserves client IP addresses directly.

Adım Adım Çözüm

1
Analyze traffic scope and visibility requirements
Traffic originates solely from internal VPC workloads, requiring an internal load balancing service rather than an external one.
Internal VPC traffic should be routed securely within the network without exposed public IP endpoints.
2
Identify the protocol and OSI layer constraints
The application uses a custom non-HTTP raw TCP protocol, ruling out Layer 7 Application Load Balancers.
Layer 7 (Application) load balancers only support HTTP, HTTPS, and gRPC traffic types.
3
Evaluate TCP termination and IP preservation requirements
Passthrough Layer 4 load balancing is required because proxy-based load balancers terminate TCP connections and do not natively preserve original client IP addresses without PROXY protocol support.
Internal Passthrough Network Load Balancers pass packets directly through to backend instances without connection termination, preserving source client IPs and minimizing processing latency.

Anahtar Kavram

Selecting GCP Network Load Balancers based on Traffic Scope, Protocol Layer, and Passthrough vs. Proxy Behavior
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

Bu konudan daha fazla soru