Instiq
Chapter 5 · Managing, monitoring, and troubleshooting network operations·v1.0.0·Updated 6/15/2026·~14 min

What's changed: Created Professional Cloud Network Engineer Chapter 5 (Domain 5 "Operations": logging network components (VPN/Router/VPC SC/Cloud NGFW/Firewall Insights/VPC Flow Logs/Cloud DNS/Cloud NAT/NCC) with Google Cloud Observability, networking metrics monitoring, Application Load Balancer connection draining/traffic redirect, VPN/Interconnect/Cloud Router BGP troubleshooting, VPC Flow Logs/firewall logs/Packet Mirroring, Network Intelligence Center = Network Topology/Connectivity Tests/Performance Dashboard/Firewall Insights/Network Analyzer/Flow Analyzer).

5.2Network Intelligence Center

Key points

Understand monitoring/troubleshooting with Network Intelligence Center: Network Topology (visualize throughput and traffic flows), Connectivity Tests (diagnose route/firewall misconfigurations), Performance Dashboard (packet loss and latency: Google-wide/project-scoped), Firewall Insights (monitor/improve rules), Network Analyzer (auto-detect failures/suboptimal configs/utilization warnings), and Flow Analyzer (evaluate traffic via VPC Flow Logs).

Network Intelligence Center (NIC) gathers network visualization, diagnosis, and optimization tools in one place. Pick the right tool by symptom.

5.2.1Visualization and diagnosis

To see configuration and traffic as a map, use Network Topology (visualize throughput and flows). Diagnose "A can't reach B" without sending real packets using Connectivity Tests, pinpointing routes, firewall misconfigurations, NAT, and more. For performance, use the Performance Dashboard to inspect packet loss and latency, both Google-wide and project-scoped. Map "statically diagnose unreachability = Connectivity Tests" and "quantify slow/dropping = Performance Dashboard."

5.2.2Optimization and analysis

Monitor and improve firewall rules with Firewall Insights (detect unused/shadowed rules and over-permissive allows). For network-wide problems, Network Analyzer continuously auto-detects failures, suboptimal configurations, and utilization warnings (signs of IP/quota exhaustion). Evaluate traffic trends with Flow Analyzer (aggregating VPC Flow Logs). Map "find unused/over-permissive firewall rules = Firewall Insights" and "auto-detect misconfig/exhaustion signs = Network Analyzer."

Exam point

Common: symptom → tool. E.g., "statically diagnose why A→B fails" = Connectivity Tests; "visualize topology and flows" = Network Topology; "quantify packet loss/latency" = Performance Dashboard; "find unused/over-permissive rules" = Firewall Insights; "auto-detect misconfig or IP-exhaustion signs" = Network Analyzer; "evaluate traffic trends via Flow Logs" = Flow Analyzer.

Warning

Watch the mix-ups: (1) Connectivity Tests is config-based static diagnosis—no real traffic (use Performance Dashboard/Flow Logs for measured). (2) Network Analyzer (automatic config diagnosis) vs Firewall Insights (rule-specific) differ in scope. (3) Network Topology visualizes; root-cause reachability diagnosis is Connectivity Tests.

Diagram of choosing by symptom: Network Topology (visualize)/Connectivity Tests (static diagnosis)/Performance Dashboard (loss-latency), and Firewall Insights/Network Analyzer/Flow Analyzer.
Pick the tool by symptom

5.2.3Section summary

  • Visualize = Network Topology; static reachability diagnosis = Connectivity Tests; performance = Performance Dashboard
  • Firewall optimization = Firewall Insights; auto-detect config/exhaustion = Network Analyzer
  • Evaluate traffic trends = Flow Analyzer (aggregating VPC Flow Logs)

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. To diagnose why "VM-A can't reach VM-B" in terms of routes/firewalls without sending real traffic, which is best?

Q2. To visualize network topology and real traffic flows/throughput as a map, which is best?

Q3. To find and improve unused or shadowed over-permissive firewall rules, which is best?

Q4. To auto-detect network-wide misconfigurations and IP/quota-exhaustion signs continuously, which is best?

Q5. To inspect measured packet loss and latency both Google-wide and project-scoped, which is best?

Check your understandingPractice questions for Chapter 5: Managing, monitoring, and troubleshooting network operations

Keep track of your progress

The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.