Examkin

Soru

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

An enterprise is migrating a custom media-rendering workstation service to Google Cloud Compute Engine instances hosted in a single regional VPC network. The service receives raw, non-HTTP TCP traffic on port 8900 from on-premises client workstations connected across Dedicated Interconnect. You must design a solution that satisfies two core requirements:
1. Route incoming internal traffic across the backend instances while preserving the original client source IP addresses for security auditing.
2. Allow on-premises client workstations to resolve the internal domain name of the load balancer using Cloud DNS.

Which combination of Google Cloud networking services should you plan?

  1. Provision an Internal Passthrough Network Load Balancer targeting the backend instance group, and create a Cloud DNS private zone with an inbound DNS forwarding entry point.Cevap
  2. B
    Provision an Internal Application Load Balancer targeting the backend instance group, and create a Cloud DNS private zone with an outbound DNS forwarding policy.
  3. C
    Provision an External Proxy Network Load Balancer targeting the backend instance group, and create a Cloud DNS public zone with DNSSEC enabled.
  4. D
    Provision an External Passthrough Network Load Balancer targeting the backend instance group, and create a Cloud DNS peering zone.

Cevap

Provisioning an Internal Passthrough Network Load Balancer targeting the backend instance group, alongside a Cloud DNS private zone configured with inbound DNS forwarding, meets all protocol, IP preservation, and DNS resolution requirements.
Selecting an Internal Passthrough Network Load Balancer correctly handles regional, private non-HTTP TCP traffic while preserving original client source IP addresses because it is a non-proxied Layer 4 load balancer. Pairing this with a Cloud DNS private zone configured for inbound DNS forwarding allows on-premises systems connected via Dedicated Interconnect to query GCP internal DNS entry points.

Adım Adım Çözüm

1
Analyze protocol and traffic path requirements
Traffic is raw non-HTTP TCP on port 8900 originating internally over Dedicated Interconnect.
This eliminates external load balancers and L7 (HTTP/HTTPS) load balancers which require HTTP/HTTPS traffic protocols.
2
Evaluate source IP preservation constraints
Internal Passthrough Network Load Balancer is selected.
Passthrough load balancers route packets directly to backends without proxying, preserving the original client source IP address required for security auditing.
3
Determine DNS forwarding architecture for on-premises clients
Cloud DNS private zone with inbound DNS forwarding policy is selected.
Inbound DNS forwarding provides internal IP entry points for on-premises DNS resolvers to query private DNS zones hosted inside Google Cloud.

Anahtar Kavram

Selecting Layer 4 vs Layer 7 load balancers and configuring Cloud DNS Inbound Forwarding for hybrid network architecture.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

Bu konudan daha fazla soru