Examkin

Question

Difficulty: HardPlanning Network Load Balancing, Cloud DNS, and Cloud CDN

An enterprise is planning a high-availability multi-region network architecture on Google Cloud. The workload requirements specify:
1. Global HTTPS web traffic must support edge caching for static assets and path-based routing to Compute Engine managed instance groups deployed in both `us-central1` and `europe-west3`.
2. Internal microservice RPC traffic running a non-HTTP raw TCP protocol on port 8443 within `us-central1` must be load-balanced with minimal latency across private Compute Engine instances without exposing public IP addresses.

Which TWO load balancing and network service configurations should you select to fulfill these requirements? (Select TWO.)

  1. Deploy a Global External Application Load Balancer with Cloud CDN enabled on the backend services for the web application.Answer
  2. Deploy an Internal Passthrough Network Load Balancer in us-central1 for the internal raw TCP microservice backends.Answer
  3. C
    Deploy a Regional External Application Load Balancer with Cloud CDN enabled to serve edge-cached content for the multi-region web application.
  4. D
    Deploy an Internal Application Load Balancer to load balance the raw TCP microservices operating on port 8443.

Answer

To satisfy the architectural requirements, deploy a Global External Application Load Balancer with Cloud CDN for global HTTPS traffic and static edge caching, and deploy an Internal Passthrough Network Load Balancer for private, low-latency Layer 4 TCP microservice traffic.
The solution requires two distinct load balancing tiers based on protocol and network scope. For public HTTPS traffic spanning multiple regions with edge caching requirements, a Global External Application Load Balancer integrated with Cloud CDN is mandatory. For private, high-performance microservices using a raw TCP protocol, an Internal Passthrough Network Load Balancer provides regional Layer 4 traffic distribution without exposing external IP endpoints.

Step-by-Step Solution

1
Analyze public web application requirements.
Requirements call for global HTTPS routing, multi-region backends, and edge caching.
Global External Application Load Balancer is the only Google Cloud load balancer that supports multi-region HTTP(S) backends with Cloud CDN edge caching.
2
Analyze internal microservices traffic requirements.
Requirements demand private IP load balancing for non-HTTP raw TCP traffic on port 8443 in us-central1.
Internal Passthrough Network Load Balancers provide high-performance Layer 4 load balancing using internal VPC IP addresses for non-HTTP protocols.

Key Concept

GCP Load Balancer Protocol and Scope Selection (L7 Global HTTP(S) vs L4 Internal Passthrough TCP)
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic