Examkin

Question

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

A company is architecture-planning a global application on Google Cloud Compute Engine. The application serves HTTPS web traffic to internet users worldwide and requires edge caching to minimize latency for static assets. In addition, the application processes real-time, non-HTTP TCP traffic on port 7000 within a single region, where backend instances must receive packets with the original client source IP address intact. Which combination of Google Cloud networking services meets these requirements according to Google recommended practices?

  1. Deploy a Global External Application Load Balancer with Cloud CDN enabled for the HTTPS traffic, and an External Passthrough Network Load Balancer for the port 7000 TCP traffic.Answer
  2. B
    Deploy a Global External Proxy Network Load Balancer with Cloud CDN enabled for the HTTPS traffic, and an Internal Passthrough Network Load Balancer for the port 7000 TCP traffic.
  3. C
    Deploy an External Passthrough Network Load Balancer with Cloud CDN enabled for the HTTPS traffic, and a Global External Application Load Balancer for the port 7000 TCP traffic.
  4. D
    Deploy a Regional External Application Load Balancer with Cloud CDN enabled for the HTTPS traffic, and a Global External Proxy Network Load Balancer for the port 7000 TCP traffic.

Answer

Deploy a Global External Application Load Balancer with Cloud CDN enabled for the HTTPS traffic, and an External Passthrough Network Load Balancer for the port 7000 TCP traffic.
The correct choice pairs a Global External Application Load Balancer with Cloud CDN for the HTTPS traffic and an External Passthrough Network Load Balancer for the raw TCP traffic on port 7000. Global External Application Load Balancers provide HTTP(S) reverse-proxy capabilities and integrate directly with Cloud CDN at edge locations. External Passthrough Network Load Balancers operate at Layer 4 (regional) and pass incoming traffic straight to backend VMs without terminating connections, preserving the client's original IP address.

Step-by-Step Solution

1
Analyze the web traffic requirements (HTTPS protocol, global scope, static media edge caching).
Identify that a Global External Application Load Balancer (Layer 7) paired with Cloud CDN is required for global edge caching of HTTPS assets.
Cloud CDN integrates with HTTP(S) Layer 7 load balancers to cache static content at Google edge points of presence globally.
2
Analyze the non-HTTP TCP traffic requirements (port 7000, regional scope, public internet accessibility, client IP preservation).
Identify that an External Passthrough Network Load Balancer (Layer 4) is required.
Passthrough load balancers route packets directly to backend instances without terminating the connection, preserving the original client source IP address.
3
Combine the service choices into a unified network architecture plan.
Select the option that pairs the Global External Application Load Balancer (with Cloud CDN) for HTTPS with the External Passthrough Network Load Balancer for TCP port 7000.
This configuration satisfies all protocol, scope, performance, and IP preservation requirements.

Key Concept

Selecting GCP Load Balancer Types based on Protocol (Layer 4 vs Layer 7), Scope, Cloud CDN Integration, and Client IP Preservation Requirements
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic