Question 690
An Azure VM is reattached from subnet `admin` to subnet `isolated` with no guest OS, SSH daemon, source IP or credentials change. Subnet `isolated` has a different NSG from `admin`. The same management client can no longer establish SSH over TCP/22, and the administrator must diagnose the network-policy difference before changing rules. What is the most targeted first check?
Explanation
Correct Answer
The effective security rules for the NIC aggregate the subnet- and NIC-associated inbound NSG rules. Checking the TCP/22 flow and its source/destination constraints isolates the policy introduced by the move; if permitted, verifying effective routes is the appropriate next diagnostic.
Incorrect Answers
Moving a NIC to `isolated` changes which subnet-level NSG applies; Azure does not keep inheriting `admin` subnet rules after the move. Reviewing only the old association misses the likely new cause of the SSH failure.
Azure evaluates both subnet and NIC network security groups where both apply. A NIC-level Allow cannot universally override a matching Deny at the subnet layer, so ignoring the new subnet is unsafe.
Adding a NIC Allow without identifying the current denial may be ineffective if the new subnet has a restrictive inbound rule. The case explicitly requests diagnosis before altering production network policy.