Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is deploying a new internet-facing IoT telemetry ingestion platform in a standalone Google Cloud VPC network with backends in us-central1 and europe-west1. External devices worldwide connect over the public internet using a custom, non-HTTP binary protocol over TCP encapsulated in TLS.
The application architecture has the following requirements:
PROXY protocol headers.Which load balancer configuration should you select?
A global external Application Load Balancer is a managed Layer 7 reverse proxy load balancer built on Envoy-based Google Front Ends (GFEs) in the Premium Tier. It distributes HTTP, HTTPS, HTTP/2, HTTP/3, and gRPC traffic behind a single global anycast IP address to backends located across multiple Google Cloud regions, external endpoints, or Cloud Storage buckets.
PROXY protocol header (PROXY_V1) to a raw TCP stream, Application Load Balancers append the client IP address into the HTTP X-Forwarded-For header, which non-HTTP binary backends cannot parse.The IoT telemetry platform communicated over HTTPS, HTTP/2, gRPC, or WebSockets rather than a custom non-HTTP binary protocol, and the backend application expected client IP addresses in the X-Forwarded-For HTTP header.
A cross-region internal proxy Network Load Balancer (INTERNAL_MANAGED load-balancing scheme) is an Envoy-based Layer 4 reverse proxy load balancer that distributes internal TCP traffic to backends across multiple Google Cloud regions. It uses a global forwarding rule bound to a regional internal IP address within a VPC subnet and requires GLOBAL_MANAGED_PROXY proxy-only subnets in every region where backends or frontends reside.
targetTcpProxies). When configured with TLS routes, the load balancer inspects the unencrypted Server Name Indication (SNI) hostname in the ClientHello packet and performs TLS passthrough, forwarding the still-encrypted byte stream directly to the backend VMs without offloading decryption.PROXY protocol on the target TCP proxy to relay the internal client's source IP address to backends.The telemetry clients were internal VPC workloads or on-premises systems connected via Cloud Interconnect or Cloud VPN, and the application required SNI-based routing with end-to-end TLS passthrough rather than edge TLS termination.
A global external proxy Network Load Balancer (EXTERNAL_MANAGED load-balancing scheme) is a Layer 4 reverse proxy load balancer built on Envoy-based Google Front Ends (GFEs) in the Premium Network Service Tier. It terminates incoming client connections at Google's network edge and opens new connections to backend instances or network endpoint groups (NEGs) across one or more Google Cloud regions.
us-central1 or europe-west1) with available capacity.targetSslProxies), the load balancer terminates client TLS connections at the GFE edge and initiates separate TCP or SSL connections to the backends, reducing cryptographic CPU overhead on your VMs.PROXY protocol (PROXY_V1) on the target proxy prepends a header carrying the client's original source IP address, destination IP, and port numbers to the backend.1 to 65535 and allows port remapping between the forwarding rule and backend instances.Compared to an Application Load Balancer (which requires HTTP/HTTPS semantics), a passthrough Network Load Balancer (which cannot offload TLS at the edge), or a regional/internal load balancer (which cannot serve global internet clients across multiple regions from a single anycast VIP), the global external proxy Network Load Balancer with a target SSL proxy is the only managed Google Cloud option that satisfies every protocol, routing, and offloading requirement.
A regional external passthrough Network Load Balancer is a Layer 4 load balancer built on Google Maglev that forwards incoming internet traffic directly to backend VMs in a single region without terminating client connections. Packets arrive at the backend with their original source IP, destination IP, and port information intact, and responses return directly to the client via Direct Server Return (DSR).
us-central1 and europe-west1 would require deploying separate regional load balancers and relying on DNS-based routing rather than a single global anycast IP address.PROXY protocol headers.The application ran in a single region, required UDP or non-TCP IP protocols (such as ESP or GRE), or needed Direct Server Return and native packet-level source IP preservation without any TLS offloading at the load balancer.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated