Exam AZ-103 topic 4 question 26 discussion

IMO Task2 should be Connection troubleshoot. It's like an Azure version of traceroute and could be more useful than the Next hop in this case.

Refer below same question for correct answer : https://www.examtopics.com/exams/microsoft/az-102/view/11/ Task1 - IP Flow Verify Task2 - Connection Troubleshoot

- Task1 - IP Flow Verify - Task2 - Connection Troubleshoot

Agreed IP Flow Verify and Connection Troubleshoot https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview

It's from Az-103, do we need to study this for Az-104?

Connection Troubleshoot is used between Azure Resources. If you want to check connectivity for external hosts, you should use the Next Hop. So, I think, answer is correct.

So what is the consensus here? Next hop or Connection Tshoot?

IP flow verify then tests the communication and informs you if the connection succeeds or fails. If the connection fails, IP flow verify tells you which security rule allowed or denied the communication First is IP flow verify

ist Verify IP Flow: Quickly diagnose connectivity issues from or to the internet and from or to the on-premises environment. For example, confirming if a security rule is blocking ingress or egress traffic to or from a virtual machine. IP flow verify is ideal for making sure security rules are being correctly applied. When used for troubleshooting, if IP flow verify doesn’t show a problem, you will need to explore other areas such as firewall restrictions. 2nd.connection troubleshoot Connection Troubleshoot. Azure Network Watcher Connection Troubleshoot is a more recent addition to the Network Watcher suite of networking tools and capabilities. Connection Troubleshoot enables you to troubleshoot network performance and connectivity issues in Azure. reference azure offical book page no.364

Task1 - IP Flow Verify Task2 - Connection Troubleshoot

The answr is Correct ,erify IP Flow Purpose: Quickly diagnose connectivity issues from or to the internet and from or to the on-premises environment. For example, confirming if a security rule is blocking ingress or egress traffic to or from a virtual machine. Next Hop Purpose: To determine if traffic is being directed to the intended destination by showing the next hop. This will help determine if networking routing is correctly configured.

Task1 - IP Flow Verify Task2 - Connection Troubleshoot

the answer is 1: IP Flow verify 2: Connection troubleshoot https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview

Task1 - IP Flow Verify Task2 - Connection Troubleshoot

1. IP Flow Verify. Explanation -> The IP flow verify capability enables you to specify a source and destination IPv4 address, port, protocol (TCP or UDP), and traffic direction (inbound or outbound). IP flow verify then tests the communication and informs you if the connection succeeds or fails. If the connection fails, IP flow verify tells you which security rule allowed or denied the communication, so that you can resolve the problem. Ref: https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview#diagnose-network-traffic-filtering-problems-to-or-from-a-vm 2. Connection Troubleshoot. Explanation -> The connection troubleshoot capability enables you to test a connection between a VM and another VM, an FQDN, a URI, or an IPv4 address. The test returns similar information returned when using the connection monitor capability, but tests the connection at a point in time, rather than monitoring it over time. Ref: https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview#connection-troubleshoot

imho task1 security group view. key is security rule. task2 ip flow verify. key is connectivity to an external host.

The connection troubleshoot capability enables you to test a connection between a VM and another VM, an FQDN, a URI, or an IPv4 address. The test returns similar information returned when using the connection monitor capability, but tests the connection at a point in time, rather than monitoring it over time, as connection monitor does.