Examkin

Soru

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

A global fleet logistics provider is architecture-planning its next-generation management platform on Google Cloud Compute Engine. The platform requires two distinct traffic paths:

1. Public internet-facing HTTPS web portals accessible to dispatchers globally, requiring low-latency distribution of static web content and media assets using edge cache nodes.
2. Internal-only high-performance gRPC microservice communication between private backend instances located across multiple subnets within the same Virtual Private Cloud (VPC) network.

Which TWO load balancing solutions should the lead cloud architect select to fulfill these requirements? (Select TWO.)

  1. Deploy a Global External Application Load Balancer for the public dispatcher portal and enable Cloud CDN on its backend service.Cevap
  2. B
    Deploy an External SSL Proxy Load Balancer for the public dispatcher portal and enable Cloud CDN on its backend service.
  3. Deploy an Internal Application Load Balancer to manage the internal backend gRPC microservice communication.Cevap
  4. D
    Deploy a Regional External Application Load Balancer to route internal gRPC microservice communication between private Compute Engine instances.

Cevap

The architectural requirements are met by deploying a Global External Application Load Balancer with Cloud CDN for the public internet portal, and an Internal Application Load Balancer for private HTTP/2 and gRPC microservice communication.
To serve global HTTPS traffic with edge caching, a Global External Application Load Balancer with Cloud CDN integration is required. For private inter-service gRPC communication within a VPC, an Internal Application Load Balancer provides Layer 7 internal load balancing with native gRPC/HTTP2 support.

Adım Adım Çözüm

1
Analyze public internet traffic and CDN requirements
Identified Layer 7 HTTP(S) requirements along with static content caching at Google edge locations.
Cloud CDN requires an HTTP(S) backend attached to a Global External Application Load Balancer.
2
Analyze internal microservice communication requirements
Identified private internal VPC traffic using gRPC protocol over HTTP/2.
Internal Application Load Balancers are Layer 7 proxy load balancers operating on private internal IP addresses with native support for HTTP/2 and gRPC.
3
Evaluate and eliminate non-conforming load balancer options
Disqualified SSL Proxy LB (does not support Cloud CDN) and Regional External LB (exposes private workloads to public internet).
Matching protocol capabilities and exposure scope to load balancer features prevents security breaches and architectural misconfigurations.

Anahtar Kavram

Selecting GCP Load Balancers based on Traffic Scope (External vs. Internal), Protocol (Layer 4 vs. Layer 7 / gRPC), and Cloud CDN Integration
Bu soruyu puanla

Konular

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

Bu konudan daha fazla soru