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 migrating from legacy VPC Packet Mirroring (HTTP and ICMP) to out-of-band Network Security Integration (NSI) with self-managed deep packet inspection (DPI) appliances in a producer VPC, exporting CEF alerts to Google SecOps SIEM.
After associating a global network firewall policy containing an HTTP MIRROR rule with the consumer project, you observe:
Which configuration resolves these issues and completes the integration?
--is_mirroring_collector, decapsulate GENEVE before forwarding CEF syslog events via Bindplane to Google SecOps SIEM, and monitor /mirroring/dropped_packets_count in Cloud Monitoring.This end-to-end out-of-band Network Security Integration (NSI) workflow consolidates session-based traffic mirroring in a global network firewall policy, routes GENEVE-encapsulated packets to third-party DPI appliances, exports threat telemetry to Google SecOps SIEM, and tracks pipeline health via Cloud Monitoring.
MIRROR rule to the global network firewall policy (pointing to a security profile group containing a CUSTOM_MIRRORING security profile) restores ICMP capture.Network ID, Endpoint ID, Profile ID). Allowing UDP port 6081 from the producer subnet gateway address or local subnet range (plus load balancer health checks) delivers packets to an internal passthrough Network Load Balancer configured with an instance group backend and --is_mirroring_collector. The DPI appliance then decapsulates GENEVE and inspects the original payload./mirroring/dropped_packets_count, /mirroring/mirrored_packets_count, and /mirroring/mirrored_bytes_count) verify packet drops.This design follows Google Cloud's native NSI data-plane mechanics, avoids unsupported NEG or regional policy configurations, and pairs deep packet inspection with dedicated SIEM ingestion and drop-level observability.
--is_mirroring_collector to accept raw HTTP and ICMP ports, and inspect VPC Flow Logs on the collector instances before forwarding CEF alerts to Google SecOps SIEM.This option attempts to preserve legacy VPC Packet Mirroring alongside Network Security Integration (NSI) by modifying policy priority, passing unencapsulated traffic directly to the producer load balancer, and relying on VPC Flow Logs on the collector VMs to audit packet delivery.
1000 and cannot be modified. More importantly, NSI Packet Mirroring always takes precedence at the workload level, causing the data plane to disregard all existing VPC Packet Mirroring policies.--is_mirroring_collector prevents the internal passthrough Network Load Balancer from functioning as a Packet Mirroring collector.Network ID, Endpoint ID, and Profile ID), requiring appliances to decapsulate UDP port 6081 traffic.--is_mirroring_collector is enabled, any non-mirrored traffic reaching the load balancer is automatically dropped.Adjusting filter specificity works only when resolving overlaps between multiple legacy VPC Packet Mirroring policies (where narrower CIDR ranges or specific protocols take precedence) in environments where NSI is not deployed.
apply_security_profile_group) to decrypt HTTPS payloads and inspect ICMP, route mirrored traffic to a GKE LoadBalancer Service collector in the producer VPC, and monitor the load balancer's collector-destination metrics for dropped mirrored packets before exporting alerts to Google SecOps SIEM.This option attempts to replace self-managed NSI appliances with Cloud IDS, combine it with Cloud NGFW Layer 7 inspection policies for TLS decryption, terminate mirrored flows on a GKE LoadBalancer Service, and rely on collector-side metrics to track packet drops.
apply_security_profile_group) and Cloud IDS are used together on the same traffic, firewall policy rules take over and traffic is not mirrored for Cloud IDS inspection./mirroring/dropped_packets_count metric is only reported at the individual mirrored VM instance level in Cloud Monitoring.Cloud IDS (without overlapping Cloud NGFW L7 inspection policies) is ideal when you want a fully managed IDS for unencrypted internal traffic or HTTP backends behind a load balancer, rather than self-managed DPI appliances behind an NSI producer load balancer.
This approach attempts to resolve the routing, policy, and logging failures by using a regional network firewall policy, opening the producer firewall to consumer CIDR ranges, attaching a network endpoint group (NEG) backend to the internal passthrough Network Load Balancer, and relying on Firewall Rules Logging for mirrored packet visibility.
MIRROR and do-not-mirror actions referencing security profile groups.NONE (5-tuple hash) session affinity, disabled backend subsetting, and the --is_mirroring_collector forwarding rule flag.This would only be partially relevant if you were deploying standard inline Layer 4 application load balancing without Packet Mirroring, where regional firewall policies, consumer source CIDRs, and NEG backends are valid constructs.
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