Question 830
Network operations reports SSH timeouts from VM vm-tools (10.12.1.6) to VM vm-prod (10.12.2.7) on TCP/22. Both are in Azure and the destination VM has an NSG at subnet and NIC scope. The engineer must identify which NSG rule permits or denies this specific flow, without changing any rules first. Which Network Watcher diagnostic is most appropriate?
Explanation
Correct Answer
IP flow verify evaluates a packet tuple against applicable Azure network security group rules and reports whether traffic is allowed or denied, along with the matched rule. Enter the appropriate VM interface and flow direction, source and destination IP addresses, TCP protocol and ports. This directly determines whether the SSH timeout is attributable to an NSG decision. If the flow is allowed, subsequent diagnostics should examine route, guest firewall or SSH daemon rather than assume all connectivity failures are caused by NSGs.
Incorrect Answers
Connection Monitor can gather recurrent connectivity and latency observations, which helps diagnose intermittent path problems. This task instead seeks the NSG rule that evaluates one specified TCP/22 flow right now. A repeated reachability test does not directly replace IP flow verify’s targeted security rule result for the VM network interface.
Next hop answers which route and next-hop type the VM will use to reach a destination. It does not identify the subnet or NIC NSG rule that allows or denies a packet. The administrator already has a specific source/destination and port; choose IP flow verify for the requested packet-filter diagnosis.
Effective routes list the route table entries applicable to a network interface. They are valuable when traffic follows an unexpected path, but the output is not an NSG rule-match evaluation. A correct route can coexist with a denying NSG. Use IP flow verify to test the specific flow against NSG security rules.