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.
An organization hosts a multi-tier web application on Google Cloud Compute Engine virtual machines. The application receives external traffic from internet users worldwide and requires HTTP(S) request routing based on the URL path:
/video/* must be directed to a dedicated video-processing backend service.Which Google Cloud load balancer should you deploy to meet these requirements?
An Internal Application Load Balancer is a Layer 7 proxy load balancer built on Envoy proxies that distributes HTTP and HTTPS traffic internally among microservices and backends located inside a Virtual Private Cloud (VPC) network or connected hybrid networks.
The requirement were to provide URL path-based routing exclusively for internal microservices communicating within a private VPC network or accessed by internal corporate users across Cloud VPN or Cloud Interconnect.
An External Application Load Balancer is a Layer 7 proxy load balancer that distributes incoming HTTP, HTTPS, and HTTP/2 traffic from external clients across backend instances, containers, or serverless endpoints. Because it operates at the Application Layer (OSI Layer 7), it inspects incoming HTTP request headers, hostnames, cookies, and URI paths rather than just IP packets.
/video/* and intelligently forwards matched requests to the video-processing backend service, while directing default traffic to the frontend service.
Because the scenario explicitly requires routing decisions based on URL paths (/video/*) from external internet clients, only a Layer 7 HTTP(S) load balancer provides the required application-level inspection and URL map routing capabilities. Layer 4 load balancers cannot inspect or route on application-layer data.
An External Passthrough Network Load Balancer is a regional Layer 4 load balancer built on Google's Andromeda network virtualization stack. It distributes non-proxied TCP and UDP traffic across backend instances located within the same region without terminating the client connection.
/video/*.The workload required load balancing raw TCP or UDP protocols (such as gaming servers, DNS, or custom protocols), needed maximum throughput with sub-millisecond latency, or required direct access to unmodified client IP packets at the operating system level without proxy termination.
An External Proxy Network Load Balancer is a Layer 4 reverse proxy that terminates incoming client TCP or SSL connections at Google's edge network and forwards the traffic to backend services in Google Cloud over high-performance internal connections.
/video/* or maintain URL routing maps for distinct backend services.The application used custom, non-HTTP TCP-based protocols that required global Anycast IP termination and centralized SSL offloading, such as custom IoT protocols, financial trading endpoints, or secure email gateways.
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