
Network Intelligence Center groups several Google Cloud network analysis tools, and three of them are easy to confuse because they all relate to firewall rules and reachability. Connectivity Tests simulate the path a packet would take through your configuration. Firewall Insights studies how firewall rules behave over time using data from Firewall Rules Logging. Network Analyzer reads your network configuration continuously and reports problems without depending on logs or traffic. For the Professional Cloud Network Engineer exam, the distinction that matters most is what data each tool works from, because that decides which questions it can answer.
Connectivity Tests analyze your network configuration and simulate the path a packet would take between two endpoints. The analysis evaluates VPC routes, firewall rules, Shared VPC setup, VPC Network Peering, Cloud Interconnect VLAN attachments, and the path to internet destinations or on-premises IP addresses. The result shows each step along the path, whether the packet would be delivered or dropped, and the reason for a drop, such as a specific firewall rule denying it or no matching route.
Because the analysis works from configuration, Connectivity Tests can attribute a drop to a particular rule or route without anyone signing in to VMs, sending probe traffic or waiting for traffic records to accumulate. That attribution is what separates them from probe tools and traffic logs, which can show that something failed but not which configuration caused it.
The same design sets their limits. Connectivity Tests mostly analyze configuration at the moment you run them, so they can miss problems that only appear under load. They do not measure live traffic, which means they say nothing about how requests are spread across backends or how much bandwidth a link carries, and they only check the source and destination pairs you define.
Firewall Insights studies how your firewall rules behave over time. It works from data generated by Firewall Rules Logging, so logging must be enabled on the rules you care about. With that in place, it provides two kinds of information:
Firewall Insights findings also point out unused rules and unused rule attributes. All of this comes from logged rule hits, so without Firewall Rules Logging on the relevant rules, Firewall Insights has nothing to analyze.
Network Analyzer reads your network configuration automatically and keeps its insights current as the configuration changes. It does not depend on logs or traffic. It reports configuration problems such as invalid routes, IP address use and service setup issues. Its VPC network insights call out firewall setups that expose workloads to ingress from the internet, across all of your networks in one view.
Because it works from configuration, Network Analyzer does not measure how much of an allow rule is actually used. Observed rule usage comes from Firewall Insights.
The data source points to the right tool:
Network Intelligence Center also includes Network Topology, which keeps about six weeks of history as hourly snapshots of resources, connections and traffic metrics.
We would keep Connectivity Tests, Firewall Insights and Network Analyzer for configuration and rule behavior on the Professional Cloud Network Engineer exam, and look to Cloud Monitoring when the question is about live traffic volume, distribution or alerting.
Our Professional Cloud Network Engineer practice exams cover Network Intelligence Center alongside VPC Flow Logs and Firewall Rules Logging, with detailed explanations that drill these distinctions.