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 runs a multi-project Google Cloud workload across us-central1 and us-east1 using VPC Network Peering and a Dedicated Interconnect to an on-premises data center. Users report intermittent timeouts, and Performance Dashboard in project-a shows:
us-east1-b and us-central1-a, while the Google Cloud view shows normal baseline loss.Which approach should you use to isolate the packet loss to the peered VPC path and trace potential bottlenecks or drops along the Dedicated Interconnect?
project-a to reach the on-premises subnet over Dedicated Interconnect, and query networking.googleapis.com/vm_flow/external_rtt in Cloud Monitoring to determine whether packet loss originates on the peered VPC link or the on-premises router.external_rtt DoPerformance Dashboard sends synthetic TCP probes to the external IP addresses of Compute Engine VMs (if assigned) to evaluate packet loss along Google Cloud's internal edge paths used by external traffic. In Cloud Monitoring, networking.googleapis.com/vm_flow/external_rtt (on gce_instance) records a passive distribution of TCP round-trip times between local VMs and public internet endpoints.
external_rtt does not measure peering or hybrid links: The vm_flow/external_rtt metric tracks passive TCP handshake/ACK timing toward internet clients, providing no visibility into internal VPC Network Peering packet loss or on-premises router drops.vm_flow/external_rtt measures passive TCP RTT (which can also be skewed by application-level ACK delays) rather than packet loss percentages.interconnect / interconnect_attachment Cloud Monitoring metrics.You were diagnosing high latency between Compute Engine VMs with external IP addresses and public internet users across specific countries or cities, rather than tracing VPC peering packet loss and Dedicated Interconnect bottlenecks.
networking.googleapis.com/all_gcp/vm_traffic/zone_pair_median_rtt in Cloud Monitoring to isolate project-a's peered VPC latency, and use Network Topology to view one-minute packet loss percentages across the Dedicated Interconnect physical connections.The networking.googleapis.com/all_gcp/vm_traffic/zone_pair_median_rtt metric (on resource type networking.googleapis.com/Location) reports the median TCP round-trip time (RTT) for VM-to-VM traffic aggregated across all Google Cloud projects. Meanwhile, Network Topology renders an interactive infrastructure graph displaying VPCs, peering links, and regional Dedicated Interconnect connections with overlaid traffic metrics.
all_gcp/vm_traffic/zone_pair_median_rtt metric reflects global Google-wide averages across every customer project, so it cannot isolate project-a's specific peered VPC traffic or diagnose project-level latency anomalies.networking.googleapis.com/vm_flow/rtt on gce_instance, whereas all_gcp/vm_traffic/zone_pair_median_rtt cannot even be queried with Monitoring Query Language (MQL) and serves only as a Google-wide baseline.interconnect and interconnect_attachment resource types in Cloud Monitoring.You wanted to build a custom Cloud Monitoring dashboard tracking Google-wide zone-pair baseline latency alongside hourly throughput visualizations on hybrid links, rather than isolating project-level peering loss and one-minute Interconnect drops.
networking.googleapis.com/cloud_netslo/active_probing/probe_count in Cloud Monitoring filtered by remote_location_type=network_peering, use Network Topology to inspect VPC peering and regional VLAN attachment throughput paths, and check interconnect and interconnect_attachment drop and error metrics in Cloud Monitoring.This workflow combines Performance Dashboard, Cloud Monitoring, and Network Topology to correlate project-specific packet loss anomalies with underlying VPC peering paths and hybrid Cloud Interconnect infrastructure. While Performance Dashboard establishes that the us-east1-b to us-central1-a issue is specific to the project rather than a Google-wide outage, Cloud Monitoring and Network Topology provide the granular filtering and path visibility required for root-cause analysis.
networking.googleapis.com/cloud_netslo/active_probing/probe_count on the gce_zone_network_health resource in Cloud Monitoring and filtering by remote_location_type=network_peering alongside result=failure isolates packet loss specifically across VPC Network Peering connections.interconnect and interconnect_attachment exposes one-minute granularity data for outbound drops, inbound/outbound errors, and capacity utilization.metric[failure] / (metric[failure] + metric[success]) using remote_zone, remote_region, and remote_location_type (cloud, external, or network_peering).No single Network Intelligence Center console view exposes both peered VPC probe breakdowns and Dedicated Interconnect drop counters. Synthesizing Performance Dashboard's Google-wide baseline comparison with Cloud Monitoring's granular probe and Interconnect metrics and Network Topology's visual path mapping pinpoints exactly where packets are being dropped.
Performance Dashboard provides Per Project and Google Cloud views to display active probing packet loss and passive TCP round-trip time (RTT) latency. Within its View options panel, you can switch the Traffic type between Cross-zonal (VM-to-VM) and To the internet (VM-to-internet), select up to five Google Cloud regions, and inspect zone-pair heatmaps.
network_peering packet loss from intra-project packet loss.network_peering probes requires exporting and querying the underlying gce_zone_network_health metrics directly in Cloud Monitoring.You only needed to determine whether total cross-zonal packet loss between us-east1-b and us-central1-a was localized to your project versus affecting all of Google Cloud, rather than isolating peered VPC links and diagnosing Dedicated Interconnect drops.
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