Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A company is deploying an e-commerce web application across multiple Google Cloud regions, including us-central1 and europe-west1, to serve customers worldwide with minimal latency. The application serves standard HTTP and HTTPS web traffic, and the architecture requires a single external IP address that automatically routes incoming traffic to the nearest healthy backend instance group.
Which Google Cloud load balancing solution should the company implement?
The Global External Application Load Balancer is a proxy-based Layer 7 (HTTP/HTTPS) load balancer built on Google's globally distributed Google Front End (GFE) network. It enables organizations to distribute external web traffic across backends located in multiple Google Cloud regions using a single global Anycast IP address.
us-central1 and europe-west1), routing requests to the closest available backend group.Because the requirements specify multi-region backends, HTTP/HTTPS web traffic, and a single anycast IP address, the Global External Application Load Balancer is the exact design pattern recommended by Google Cloud for global web workloads.
The Regional External Application Load Balancer is a managed Layer 7 (HTTP/HTTPS) proxy service implemented within a specific Google Cloud region using Envoy proxies. It is designed to route external HTTP/HTTPS traffic to backends located strictly inside that single region.
us-central1 and europe-west1.The workload was localized to a single region to satisfy regional data residency requirements or if multi-region global distribution and Anycast IP routing were not needed.
The Regional Internal Network Load Balancer is a software-defined, non-proxied Layer 4 (TCP/UDP) load balancer built directly on Google Cloud's Andromeda virtualization stack. It routes internal traffic between services inside a VPC network within a single region.
The scenario involved private, internal microservices within a single VPC and region communicating over non-HTTP protocols or requiring extreme Layer 4 throughput.
The Global External Proxy Network Load Balancer (formerly TCP/SSL Proxy) is a Layer 4 proxy-based load balancer that distributes non-HTTP TCP traffic to backend services across multiple Google Cloud regions using a global Anycast IP address.
The application required global load balancing over raw TCP protocols other than HTTP/HTTPS (such as custom binary protocols or real-time gaming backends).
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