Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team is deploying an internal HTTP(S) inventory API on Google Kubernetes Engine (GKE) across us-central1 and europe-west1. The service must meet the following requirements:
Which load balancer should you choose?
An Internal passthrough Network Load Balancer is a Layer 4 load balancer built on the Andromeda network virtualization stack. It distributes TCP, UDP, and other IP protocol traffic directly to backend VMs or endpoints without terminating client connections.
us-central1 and europe-west1.You were load balancing non-HTTP(S) Layer 4 traffic (such as a database cluster or custom TCP/UDP service) hosted within a single region, needed to preserve client source IP addresses, and wanted clients in any region to reach it privately.
A Cross-region internal Application Load Balancer is an Envoy proxy-based, Layer 7 load balancer designed for internal HTTP and HTTPS traffic. It distributes requests across globally distributed backend services located in multiple Google Cloud regions behind an internal IP address.
GCE_VM_IP_PORT zonal NEGs) in both us-central1 and europe-west1 allows the load balancer to automatically fail over traffic to the healthy region if one region goes down.GLOBAL_MANAGED_PROXY proxy-only subnets.Unlike regional internal options, the cross-region mode is the only internal Layer 7 load balancer capable of spanning backends across multiple regions while natively providing cross-region failover and global internal client access.
A Global external Application Load Balancer is a Layer 7 proxy load balancer implemented on globally distributed Google Front Ends (GFEs) and Envoy proxies. It provides a single global Anycast external IP address for internet-facing HTTP(S) workloads.
The inventory API needed to be exposed to public internet users globally and protected against external DDoS or web attacks while distributing traffic across us-central1 and europe-west1.
A Regional internal Application Load Balancer is a proxy-based Layer 7 load balancer built on Envoy proxies that distributes internal HTTP(S) traffic behind a regional internal IP address.
us-central1 and europe-west1 under a single regional backend service, the load balancer cannot automatically fail over to healthy GKE backends in another region during a regional outage.REGIONAL_MANAGED_PROXY).Your GKE backends were deployed in only one region (for example, strictly in us-central1 for data residency) and you simply needed internal clients in other regions to reach that single-region deployment over HTTP(S).
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