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 VPC Packet Mirroring in us-central1 to mirror all IPv4 traffic from production VMs in prod-vpc to self-managed intrusion detection Network Virtual Appliances (NVAs) in a peered network (collector-vpc). Your design must meet these requirements:
us-central1 must serve as the collector endpoint.collector-vpc must allow all mirrored traffic and load balancer health checks.How should you design and configure the collector infrastructure?
us-central1 in collector-vpc, running the guest environment and listening on 0.0.0.0. Create an internal passthrough Network Load Balancer with a regional HTTP health check on port 80, a backend service with NONE session affinity and subsetting disabled, and a new forwarding rule using TCP on all ports with --is-mirroring-collector. Create ingress firewall rules allowing 0.0.0.0/0, 130.211.0.0/22, and 35.191.0.0/16.This architecture pairs a regional managed instance group (MIG) of multi-zone NVA collectors with a properly configured regional internal passthrough Network Load Balancer designated as a Packet Mirroring collector in us-central1.
us-central1. Omitting external IP addresses keeps the appliances isolated from direct internet access while the Google Cloud guest environment configures local routes for the load balancer VIP and the NVA software binds to 0.0.0.0.--is-mirroring-collector, --ip-protocol=TCP, and --ports=all (avoiding L3_DEFAULT), backed by a backend service with NONE session affinity (5-tuple hash) and backend subsetting disabled, satisfies every Packet Mirroring load balancer constraint.0.0.0.0/0 permits unencapsulated mirrored packets carrying any original IPv4 source address, while allowing 130.211.0.0/22 and 35.191.0.0/16 permits Google Cloud TCP-based HTTP health check probes on port 80.prod-vpc workloads to mirror packets across VPC Network Peering into collector-vpc within the same region.80 ensures Google Cloud health checkers route traffic only to operational NVAs.Unlike proxy load balancers, L3_DEFAULT configurations, or single-instance collectors, this design follows all Google Cloud VPC Packet Mirroring requirements while providing regional fault tolerance and strict perimeter isolation.
us-central1 in collector-vpc. Configure an internal passthrough Network Load Balancer with a regional HTTP health check on port 80, a backend service with NONE session affinity and subsetting disabled, and a new forwarding rule using UDP on port 6081 with --is-mirroring-collector. Create a single ingress firewall rule allowing UDP port 6081 from the collector-vpc subnet gateway address.This option places a single NVA instance behind an internal passthrough Network Load Balancer and configures the collector firewall and forwarding rule specifically for GENEVE-encapsulated UDP port 6081 traffic from the local subnet gateway.
6081 from the local subnet gateway drops all unencapsulated mirrored TCP, UDP, and ICMP packets arriving from prod-vpc.130.211.0.0/22 and 35.191.0.0/16 causes the regional HTTP health check on port 80 to fail.6081 from the producer subnet gateway applies to Network Security Integration (NSI) out-of-band Packet Mirroring, which uses GENEVE headers—not standard VPC Packet Mirroring.You were deploying Network Security Integration out-of-band mirroring instead of VPC Packet Mirroring, added at least two collectors across multiple zones, and included firewall rules for the Google Cloud health check IP ranges.
us-central1 in collector-vpc. Configure an internal passthrough Network Load Balancer with a regional HTTP health check on port 80, a backend service using CLIENT_IP session affinity and CONSISTENT_HASH_SUBSETTING enabled, and a forwarding rule using protocol L3_DEFAULT with --is-mirroring-collector. Create ingress firewall rules allowing prod-vpc subnet CIDRs, 130.211.0.0/22, and 35.191.0.0/16.This approach deploys a multi-zone regional managed instance group (MIG) of internal-only NVAs, but configures the internal passthrough Network Load Balancer with CLIENT_IP session affinity, backend subsetting, an L3_DEFAULT forwarding rule, and narrow prod-vpc source firewall rules.
L3_DEFAULT protocol on the internal forwarding rule.NONE (5-tuple hash) and backend subsetting disabled; CLIENT_IP affinity and CONSISTENT_HASH_SUBSETTING violate these prerequisites.prod-vpc from external or hybrid sources carries those original source IP addresses rather than prod-vpc subnet CIDRs. Restricting the firewall rule to prod-vpc ranges drops mirrored external-to-VM flows.TCP or UDP (typically TCP with --ports=all), never L3_DEFAULT.0.0.0.0/0 (or full expected client ranges) on ingress.It were configured for a standard next-hop internal passthrough Network Load Balancer routing inline traffic with L3_DEFAULT and subsetting, rather than a Packet Mirroring collector endpoint.
us-central1 in collector-vpc alongside a dedicated proxy-only subnet. Create a regional internal proxy Network Load Balancer with a regional HTTP health check on port 80, and update an existing forwarding rule to add the --is-mirroring-collector flag. Create ingress firewall rules allowing traffic from 0.0.0.0/0, 130.211.0.0/22, and 35.191.0.0/16.This option attempts to use a regional internal proxy Network Load Balancer with a proxy-only subnet and a single-zone MIG, while trying to retroactively enable --is-mirroring-collector on a pre-existing forwarding rule.
--is-mirroring-collector attribute must be specified when the forwarding rule is created; it cannot be added by updating an existing forwarding rule.proxy-only subnets are required by Envoy-based proxy load balancers, whereas passthrough Network Load Balancers forward packets directly via the Andromeda virtualization stack without proxies.The workload were a standard internal TCP application tier requiring Envoy proxying, rather than a Packet Mirroring collector architecture requiring a newly created passthrough forwarding rule and multi-zone redundancy.
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