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 team manages a global external Application Load Balancer serving a production API. Currently, requests matching /api/v2/ are split using weighted backend services: 90% to prod-v1-bes and 10% to prod-canary-bes (both backed by Managed Instance Groups).
You need to test a new debugging service (debug-bes) against live /api/v2/ traffic under these requirements:
/api/v2/ requests to debug-bes on a fire-and-forget basis without impacting live user latency or responses.debug-bes uses a supported backend type and that your team can verify mirrored request processing.Which configuration should you implement?
requestMirrorPolicy with mirrorPercent: 20.0 alongside weightedBackendServices in the URL map's routeAction, configure debug-bes with a serverless NEG backend to minimize idle capacity, and monitor Cloud Load Balancing metrics for debug-bes to verify mirrored request volume.Serverless network endpoint groups (NEGs) allow an Application Load Balancer to route live user traffic to fully managed serverless compute platforms such as Cloud Run, App Engine, or Cloud Functions. Under normal routing, Cloud Load Balancing automatically emits request logs to Cloud Logging and HTTP status/latency metrics to Cloud Monitoring for each backend service.
requestMirrorPolicy) on an Application Load Balancer is only supported when both the primary and mirrored backend services use Managed Instance Groups (MIGs), zonal NEGs, or hybrid NEGs. It is explicitly not supported for serverless NEGs, internet NEGs, or Private Service Connect backends.debug-bes will show zero mirrored traffic even when mirroring is active.requestMirrorPolicy fails backend compatibility requirements.You were routing live production traffic to debug-bes via weightedBackendServices rather than mirroring traffic—in that case, serverless NEGs are supported and standard Cloud Load Balancing metrics and logs are generated.
requestMirrorPolicy referencing debug-bes (backed by a Managed Instance Group) alongside weightedBackendServices in the URL map's routeAction without mirrorPercent to mirror a subset of requests proportionally, and inspect Cloud Monitoring load balancer metrics for debug-bes to analyze mirrored error rates.mirrorPercent and using load balancer metrics doesIn an Application Load Balancer URL map, requestMirrorPolicy is configured inside routeAction alongside primary routing actions such as weightedBackendServices. The optional mirrorPercent field controls what fraction of matching requests are duplicated to the mirror target.
mirrorPercent is omitted, the mirrored backend service receives all (100%) matching requests—even when the primary traffic is split across multiple weightedBackendServices. Without mirrorPercent: 20.0, debug-bes receives five times the intended traffic load, risking overload.debug-bes will remain empty and cannot be used to analyze mirrored request rates or HTTP error codes.requestMirrorPolicy does not inherit percentages or weights from weightedBackendServices; sampling must be explicitly configured with mirrorPercent (0 to 100.0).debug-bes instances themselves.You intended to mirror 100% of /api/v2/ requests to debug-bes and verified request handling through application logs on the debug-bes instances rather than Cloud Monitoring load balancer metrics.
requestMirrorPolicy referencing debug-bes with mirrorPercent: 20.0 alongside weightedBackendServices in the URL map's routeAction, back debug-bes with a Managed Instance Group or zonal NEG, and verify mirrored traffic using application logs or telemetry on debug-bes.Request mirroring (requestMirrorPolicy) is a Layer 7 traffic management action configured in an Application Load Balancer URL map (routeAction). When a request matches a route rule, the load balancer forwards the request to the primary backend service and asynchronously sends an identical duplicate to the configured mirror backend service on a fire-and-forget basis, never waiting for or returning the mirror's response to the client.
mirrorPercent: 20.0 inside requestMirrorPolicy limits mirrored traffic to 20% of matching /api/v2/ requests. Because the load balancer ignores responses, errors, and latency from debug-bes, live users experience zero impact.requestMirrorPolicy with weightedBackendServices in the same routeAction maintains the 90% prod-v1-bes and 10% prod-canary-bes distribution for client-facing responses while sampling 20% of matched requests.debug-bes with a Managed Instance Group (MIG) or zonal NEG satisfies the requirement that both primary and mirrored backend services use MIGs, zonal NEGs, or hybrid NEGs. Because mirrored requests do not generate Cloud Logging or Cloud Monitoring metrics at the load balancer, inspecting application logs or host-level telemetry directly on debug-bes is the proper way to verify processing.mirrorPercent granularity: Accepts values from 0 to 100.0; omitting it defaults to mirroring 100% of matching requests.headerAction (requestHeadersToAdd) can inject a custom header such as x-weighted-picked-backend to record whether prod-v1-bes or prod-canary-bes served the primary request.debug-bes must be sized to handle 20% of /api/v2/ request volume independently.This approach provides native Layer 7 path-based (/api/v2/) and percentage-based (20.0) request duplication directly within the global external Application Load Balancer while respecting all backend and observability constraints.
prod-v1-bes and prod-canary-bes Managed Instance Group subnets with a TCP filter, and forward the mirrored packets to debug-bes via an internal passthrough Network Load Balancer configured with --is-mirroring-collector.VPC Packet Mirroring is a Layer 3/Layer 4 network-level feature that clones raw ingress and egress network packets directly at Compute Engine VM virtual network interfaces (vNICs) and forwards them to collector appliances behind an internal passthrough Network Load Balancer whose forwarding rule is created with --is-mirroring-collector.
INGRESS, EGRESS, or BOTH). It cannot inspect HTTP URL paths like /api/v2/ or sample 20% of HTTP requests.tcpdump hosts), not parsed HTTP requests to an Application Load Balancer backend service (debug-bes). A standard web application backend cannot process raw mirrored TCP flows addressed to different destination IPs without specialized decapsulation or tap tooling.prod-v1-bes and prod-canary-bes VMs.--is-mirroring-collector and NONE session affinity; non-mirrored traffic sent to it is dropped.You needed out-of-band network security monitoring or deep packet inspection (such as IDS appliances analyzing full multi-packet TCP flows) at the VPC subnet or VM level rather than Layer 7 HTTP request mirroring.
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