Question 381 of 1,049
AZ-104 Implement and Manage Virtual Networking Practice Question
Exhibit
Troubleshooting summary: VM1 to VM2 on TCP 1433 shows Status = Blocked; connection troubleshooting reports that the destination is reachable at the route level; the administrator needs the specific allow or deny rule name.
Based on the exhibit, which Network Watcher tool should the administrator use to identify the exact NSG rule that is blocking TCP 1433 traffic?
⚠ Common exam trap
A common mix-up: candidates confuse 'Connection troubleshoot' (which tests end-to-end connectivity but not rule-level blocking) with 'IP flow verify' (which explicitly evaluates NSG rules), leading them to select A instead of B.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
IP flow verify
IP flow verify is the correct Network Watcher tool because it tests whether a packet is allowed or denied to or from a specific virtual machine based on a 5-tuple (source IP, destination IP, source port, destination port, and protocol). By specifying TCP 1433 as the destination port, the tool evaluates all effective security rules (NSG and ASG) and returns the exact rule name and direction that is blocking the traffic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Connection troubleshoot
Why it's wrong here
Connection troubleshoot performs an end-to-end diagnostic from a source VM to a destination and returns connectivity status, latency, and the path through the network. Although it can reveal that a connection is failing and sometimes the hop at which packets are dropped, it does not enumerate the NSG rules that were evaluated or point to the specific rule that blocked the traffic. It is useful for reachability, not for rule-level attribution.
When this WOULD be correct
If the question asked which tool to use to test TCP connectivity over a specific port between two VMs and report latency, packet loss, and hop-by-hop path, then Connection troubleshoot would be correct.
- ✓
IP flow verify
Why this is correct
IP flow verify takes a source/destination IP, port, protocol, and direction, then simulates the traffic against the effective NSG security rules on the target NIC. It reports either Allowed or Denied and, when denied, identifies the exact NSG rule (including the rule name and priority) that caused the verdict. This makes it the correct tool when you need to determine which NSG rule is affecting a specific traffic flow.
- ✗
Next hop
Why it's wrong here
Next hop is a routing diagnostic that shows the effective route for a specific destination, listing the next hop type (such as VirtualNetwork, Internet, or VirtualAppliance) and the associated route table. It focuses only on the routing layer; NSG rules are applied after routing and are never considered by this tool. Therefore, even if the next hop is correct, a denied flow may be caused by an NSG, which Next hop cannot identify.
When this WOULD be correct
Use Next hop when troubleshooting routing issues, such as determining why traffic is taking an unexpected path (e.g., traffic destined for a VM is being sent to a virtual appliance instead of directly to the VM).
- ✗
Packet capture
Why it's wrong here
Packet capture installs an agent on the VM and captures raw network traffic to a file for offline inspection. While you can manually examine captured packets and correlate them with firewall logs, the tool itself does not automatically report which NSG rule allowed or denied the flow, nor does it parse the NSG rule set. It is a deep forensic method that takes time to configure and analyze, making it less direct and slower than IP flow verify for this specific question.
When this WOULD be correct
Packet capture would be correct when the question asks to capture and analyze network traffic to diagnose a performance issue or inspect application-level protocol details, such as verifying if a specific SQL query is being sent over TCP 1433.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓IP flow verifyCorrect answer▾
Why this is correct
IP flow verify takes a source/destination IP, port, protocol, and direction, then simulates the traffic against the effective NSG security rules on the target NIC. It reports either Allowed or Denied and, when denied, identifies the exact NSG rule (including the rule name and priority) that caused the verdict. This makes it the correct tool when you need to determine which NSG rule is affecting a specific traffic flow.
✗Connection troubleshootWrong answer — click to see why▾
Why this is wrong here
Connection troubleshoot tests end-to-end connectivity between a source and destination VM, but it does not identify which specific NSG rule is blocking traffic; it only reports connectivity success or failure.
★ When this WOULD be the correct answer
If the question asked which tool to use to test TCP connectivity over a specific port between two VMs and report latency, packet loss, and hop-by-hop path, then Connection troubleshoot would be correct.
Why candidates choose this
Candidates may think 'troubleshoot' implies diagnosing blocking rules, but Connection troubleshoot is for broader connectivity checks, not rule-level analysis.
✗Next hopWrong answer — click to see why▾
Why this is wrong here
Next hop identifies the next hop IP address and route for a packet, but it does not evaluate NSG rules to determine if traffic is allowed or blocked.
★ When this WOULD be the correct answer
Use Next hop when troubleshooting routing issues, such as determining why traffic is taking an unexpected path (e.g., traffic destined for a VM is being sent to a virtual appliance instead of directly to the VM).
Why candidates choose this
Candidates may confuse network path analysis with security rule evaluation, thinking that identifying the next hop will reveal where the traffic is blocked.
✗Packet captureWrong answer — click to see why▾
Why this is wrong here
Packet capture captures raw network packets for deep analysis but does not identify which specific NSG rule is blocking traffic; it requires manual inspection of captured data and does not correlate with NSG rules.
★ When this WOULD be the correct answer
Packet capture would be correct when the question asks to capture and analyze network traffic to diagnose a performance issue or inspect application-level protocol details, such as verifying if a specific SQL query is being sent over TCP 1433.
Why candidates choose this
Candidates may think packet capture can directly show blocked packets, but it lacks integration with NSG rule evaluation and requires additional analysis to determine rule blocking.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.