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 multi-region web API on Compute Engine Managed Instance Groups (MIGs) and needs to configure external Layer 7 load balancing. The solution must meet these requirements:
Which load balancing architecture and configuration should you implement?
The global external Application Load Balancer is an Envoy proxy-based, global Layer 7 load balancer operating in Premium Tier behind a single global Anycast IP address. It pairs global URL maps for advanced HTTP(S) traffic steering and actions with global backend services for health checking, capacity management, and security policy enforcement.
UTILIZATION or RATE), allowing compute capacity in each region to scale out during traffic spikes and scale in when idle.weightedBackendServices to shift traffic gradually between stable and canary backend services without enabling conflicting session affinity (which is overridden by weighted splitting).requestMirrorPolicy copies matched requests on a fire-and-forget basis to a MIG-based debugging backend, while operational dashboards alert on the primary backend service because mirrored requests do not emit Cloud Logging or Cloud Monitoring telemetry.LocalityLbPolicy, consistentHash (when RING_HASH or MAGLEV is used), and outlierDetection to evict unhealthy endpoints.Unlike regional external Application Load Balancers (which lack global Anycast routing and load-balancer-capacity MIG autoscaling) and classic Application Load Balancers (which lack weighted traffic splitting, header routing, and traffic mirroring), the global external Application Load Balancer is the only external Layer 7 mode that satisfies every scaling, routing, security, and observability requirement simultaneously.
A regional external Application Load Balancer is an Envoy proxy-based Layer 7 load balancer deployed strictly within a single Google Cloud region and always operating in Standard Tier. It uses regional URL maps and regional backend services to expose HTTP(S) workloads on a regional external IP address.
weightedBackendServices, requestMirrorPolicy, outlierDetection, and circuitBreakers within a region.The workload operated within a single region due to jurisdictional or data-residency compliance requiring regional TLS termination in Standard Tier, and MIG autoscaling relied on CPU or custom metrics rather than load balancer serving capacity.
Although both regional and global external Application Load Balancers share the same Envoy-based traffic management primitives (weightedBackendServices, requestMirrorPolicy, and headerAction), choosing the regional mode sacrifices global Anycast distribution and load-balancer-driven MIG autoscaling.
This configuration pairs a global external Application Load Balancer with a Cloud Run serverless Network Endpoint Group (NEG) as the destination for requestMirrorPolicy to avoid paying for idle debugging VMs, while attempting to track mirrored requests through Cloud Monitoring.
requestMirrorPolicy is not supported for serverless NEG backends (nor for internet NEGs or Private Service Connect backends). Both the primary and mirrored backend services must use Managed Instance Groups (MIGs), zonal NEGs (GCE_VM_IP_PORT), or hybrid NEGs.The debugging service were hosted on a small MIG or zonal NEG (such as GKE Pods with container-native load balancing) rather than a serverless NEG, and operational alerting in Cloud Monitoring targeted the primary backend service.
Using Cloud Run for cost optimization is effective for primary request-serving routes, but traffic mirroring imposes strict backend type and observability constraints that prevent serverless NEGs from acting as mirror targets.
The classic Application Load Balancer is Google Cloud's legacy global Layer 7 proxy load balancer (built on Google Front End infrastructure rather than the Envoy-based traffic management data plane). When deployed in Premium Tier, it provides a global Anycast IP address and basic host-and-path routing to backend services.
weightedBackendServices): The classic mode does not support percentage-based canary traffic splitting in its URL maps.requestMirrorPolicy): Mirroring production requests to a debugging backend service is not supported on classic Application Load Balancers.weightedBackendServices, requestMirrorPolicy, outlierDetection, faultInjectionPolicy, and headerAction transformations.The application only required basic host-and-path routing with global Anycast IP delivery, Cloud Armor, and MIG autoscaling based on load balancer serving capacity, without needing canary traffic splitting, header-based routing, or request mirroring.
A frequent exam pitfall is assuming all global external Application Load Balancers support the exact same URL map capabilities. While classic and global modes both support MIG autoscaling on serving capacity, only the Envoy-based global mode unlocks advanced traffic management (weightedBackendServices and requestMirrorPolicy).
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