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.
You are troubleshooting connectivity failures between an on-premises host (10.30.0.2) and a Compute Engine VM (10.10.0.99) running in a Shared VPC service project (svc-app) over a Cloud VPN tunnel connected to the host project (host-net). Using the Network Management API, you enabled VPC Flow Logs (with a secondary sampling rate of 1.0) on both the Cloud VPN tunnel and the VM's subnet (west-subnet), and you enabled logging on all custom VPC firewall rules.
When you analyze the logs in Cloud Logging within the host-net project during a failed TCP port 443 connection attempt and an ICMP ping test from 10.30.0.2 to 10.10.0.99, you observe the following:
networkmanagement.googleapis.com/vpc_flows shows both TCP/443 and ICMP packets traversing the Cloud VPN tunnel (reporter="SRC_GATEWAY").networkmanagement.googleapis.com/vpc_flows for west-subnet shows zero ingress flow records for 10.30.0.2 -> 10.10.0.99, even though VM-initiated egress packets (10.10.0.99 -> 10.30.0.2) appear in west-subnet flow logs.compute.googleapis.com/firewall shows repeated disposition: "DENIED" entries every 5 seconds for TCP/443 from 10.30.0.2 to 10.10.0.99, but no entries for the ICMP traffic.Which analysis accurately explains these correlated log observations?
west-subnet ingress logs indicates packets are being dropped inside the Cloud VPN tunnel; meanwhile, the repeated DENIED entries reflect an egress deny rule blocking return traffic from 10.10.0.99.In Google Cloud VPC networking, VPC Flow Logs interacts asymmetrically with ingress and egress firewall evaluation. Ingress packets are sampled after ingress firewall rules are enforced, whereas egress packets are sampled before egress firewall rules are evaluated. Additionally, Google Cloud VPC firewall rules are stateful, meaning once an inbound connection is allowed, return traffic is permitted automatically without triggering egress firewall rules.
DENY rule never reach the VPC Flow Logs sampler on west-subnet—rather than proving a drop inside the Cloud VPN tunnel.reporter="SRC_GATEWAY" records in networkmanagement.googleapis.com/vpc_flows demonstrates that both TCP/443 and ICMP packets successfully traversed the Cloud VPN tunnel and entered the VPC.DENY rule cannot block return traffic for an established inbound connection, nor would an egress DENY rule on 10.10.0.99 log 10.30.0.2 -> 10.10.0.99 as the denied 5-tuple.DENY firewall rule drops them immediately afterward.This would be plausible only if the Cloud VPN tunnel's own flow logs showed zero packets reaching the VPC and the firewall logs instead showed src_ip=10.10.0.99 hitting an egress DENY rule on newly initiated outbound connections.
Correlating gateway flow logs (SRC_GATEWAY) with subnet flow logs is a primary method for isolating whether packet loss occurs across the hybrid tunnel or at the VM's ingress firewall boundary.
10.30.0.2 after they traverse the Cloud VPN tunnel and before west-subnet VPC Flow Logs can sample ingress traffic, while VPC Firewall Rules Logging records only TCP and UDP connections (repeating denied 5-tuples every 5 seconds) and excludes ICMP.Tracing hybrid packet flows across Google Cloud requires correlating gateway-level VPC Flow Logs, subnet-level VPC Flow Logs, and VPC Firewall Rules Logging while accounting for where each telemetry mechanism sits in the packet pipeline and which IP protocols each log stream supports.
SRC_GATEWAY): With VPC Flow Logs enabled on the Cloud VPN tunnel via the Network Management API, networkmanagement.googleapis.com/vpc_flows captures packets traversing the VPN gateway. Because VPC Flow Logs supports TCP, UDP, ICMP, ESP, and GRE, both the TCP/443 and ICMP packets from 10.30.0.2 are recorded at the gateway, proving the VPN tunnel and routing to the VPC are healthy.west-subnet ingress logs vs. present egress logs: VPC Flow Logs samples ingress packets after ingress firewall rules and egress packets before egress firewall rules. Because an explicit ingress DENY rule blocks 10.30.0.2 -> 10.10.0.99 before ingress sampling occurs, zero ingress flow records appear on west-subnet despite a 1.0 secondary sampling rate. Meanwhile, outbound packets initiated by 10.10.0.99 are sampled before egress firewall evaluation and appear normally.DENIED logs without ICMP logs: Explicitly configured DENY firewall rules with logging enabled emit a failed connection record for each unique dropped 5-tuple and repeat every 5 seconds while packets persist (implied deny ingress rules do not support logging). Because VPC Firewall Rules Logging supports only TCP and UDP, the dropped ICMP packets generate no entries in compute.googleapis.com/firewall.networkmanagement.googleapis.com/vpc_flows and compute.googleapis.com/firewall are written to the host project (host-net).ALLOW rules log once per connection (until a 10-minute idle timeout or TCP RST), while DENY rules log every 5 seconds per active denied 5-tuple.reporter="SRC_GATEWAY" tunnel logs against subnet flow logs immediately isolates drops occurring at the VM firewall boundary.This correlation eliminates false leads such as Cloud VPN tunnel drops, Shared VPC project misrouting, or sampling gaps. To resolve the outage, inspect jsonPayload.rule_details.reference in the TCP/443 DENIED firewall log entries and adjust the blocking ingress rule's priority, protocol/port scope, or source CIDR ranges to permit 10.30.0.2.
west-subnet ingress flow logs and ICMP firewall logs are being written to the svc-app service project rather than host-net, because Shared VPC subnet flow logs and VM firewall logs are routed to the project containing the target Compute Engine instance.In a Shared VPC architecture, the VPC network, subnets, Cloud VPN tunnels, and firewall rules are defined and managed centrally in the host project (host-net), while Compute Engine VMs reside in service projects (svc-app). Because network telemetry is bound to the project that owns the VPC network, both VPC Flow Logs and VPC Firewall Rules Logging write their log entries exclusively to the host project, never to the service projects.
host-net: The observation confirms that VM-initiated egress flows from 10.10.0.99 on west-subnet are visible in host-net, proving that west-subnet flow logs are not routed to svc-app.host-net: The compute.googleapis.com/firewall log in host-net is already recording DENIED events targeting 10.10.0.99 on TCP/443.compute.googleapis.com/firewall because VPC Firewall Rules Logging records only TCP and UDP connections regardless of project placement.networkmanagement.googleapis.com/vpc_flows and compute.googleapis.com/vpc_flows) and firewall logs are stored in the host project.dest_vpc.project_id identifies the host project while dest_instance.project_id identifies the service project owning the VM.west-subnet ingress records in host-net occur because ingress traffic is dropped by an ingress firewall rule before VPC Flow Logs samples it.This explanation would apply if the VM were attached to a standalone VPC in svc-app connected via VPC Network Peering to host-net, in which case each project would independently store its own subnet flow logs and firewall rule logs.
When troubleshooting Shared VPC workloads, always query Cloud Logging or Log Analytics in the host project and filter by jsonPayload.dest_instance.project_id or jsonPayload.instance.project_id to isolate traffic for a specific service project VM.
west-subnet VPC Flow Logs omit ingress packets because the _Default log bucket has not been upgraded to Log Analytics to ingest VM-level ingress telemetry, and ICMP is absent from compute.googleapis.com/firewall because firewall rules logging only logs connections after 10 minutes of inactivity.Upgrading a Cloud Logging bucket (such as _Default) with Log Analytics (enable_analytics = true) enables SQL querying and powers Flow Analyzer visualizations in Network Intelligence Center. Separately, the 10-minute idle timer in VPC Firewall Rules Logging governs connection tracking state for already active TCP and UDP connections when logging is newly enabled on a matching firewall rule.
networkmanagement.googleapis.com/vpc_flows) regardless of whether the destination bucket is upgraded to Log Analytics. Moreover, both Cloud VPN tunnel flow logs and west-subnet egress flow logs are already visible in host-net.compute.googleapis.com/firewall regardless of idle duration because VPC Firewall Rules Logging records only TCP and UDP traffic.enable_analytics = true) is required for Flow Analyzer dashboards, not for standard Logs Explorer flow log collection.This would apply if Flow Analyzer in Network Intelligence Center displayed no data because the _Default bucket lacked Log Analytics while Logs Explorer still contained the flow records, and if an already established ALLOW TCP connection failed to log immediately after enabling logging on its matching rule.
Always distinguish between control/data-plane log generation (governed by API configuration, sampling, and firewall evaluation order) and storage-bucket analytics capabilities (governed by Log Analytics upgrades for SQL and Flow Analyzer).
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