You have an SAP production landscape on Azure that contains the virtual machines shown in the following table. VM1 cannot connect to an employee self-service application hosted on VM2. You need to…

Question

Exhibit

Options

• AConnection troubeshoot
• BConnection monitor
• CIP flow verify
• DNetwork Performance Monitor

• A
  77% (27)
• B
  17% (6)
• D
  6% (2)

Explanation

Connection Troubleshoot (A) performs an on-demand connectivity check between VM1 and VM2, returning a pass/fail result along with the specific hop or rule causing the failure - ideal for immediate point-in-time diagnosis. IP Flow Verify (C) complements this by checking whether the NSG (Network Security Group) rules on either VM are blocking the specific traffic flow, which is a very common cause of VM-to-VM connectivity failures in Azure.

Connection Monitor (B) is wrong here because it's designed for continuous monitoring and alerting over time, not for diagnosing an active, immediate connectivity problem. Network Performance Monitor (D) is a Log Analytics-based solution focused on measuring latency and packet loss across hybrid or ExpressRoute networks - too broad and infrastructure-level for a targeted VM-to-VM application issue.

Memory tip: Think of it as a two-step "CSI" approach - Connection Troubleshoot tests if you can get there, and IP Flow Verify checks if the gates (NSG rules) are open. Together they cover the path and the policy.

No community discussion yet for this question.