Azure Network Watcher Connection Monitor for Latency

AZ-700 By islever Editorial Last updated

Monitor networks

Short answer

D Create a Connection Monitor resource in the West US 2 region to monitor latency to both the on-premises datacenter and East US 2.

Question

You have an on-premises datacenter in Seattle. You have an Azure subscription that contains an Azure Network Watcher resource in the West US 2 Azure region. You need to document network latency between the on-premises datacenter and the West US 2 region and between the on-premises datacenter and the East US 2 public Azure region. The solution must minimize administrative effort. What should you do first?
  1. Run the Get-AzNetworkWatcherConnectionMonitor cmdlet.
  2. Run the Get-AzNetworkWatcherReachabilityProvidersList cmdlet.
  3. Create a Network Watcher resource in the East US 2 region.
  4. Create a Connection Monitor resource in the West US 2 region. Correct Answer

Key Takeaways

The core concept tested is the capability of a single Connection Monitor instance to monitor multiple endpoints across different regions, avoiding the need for redundant resources.

This question addresses using Azure Network Watcher's Connection Monitor to measure network latency between on-premises sites and multiple Azure regions while minimizing administrative overhead.

Common mistake: Most learners incorrectly select creating a new resource in East US 2, failing to recognize that one Connection Monitor can cover all required destinations.

Expert Analysis

Why the Answer Is Correct

Connection Monitor is a feature within Azure Network Watcher designed to provide continuous monitoring of communication metrics like latency and packet loss. A key architectural advantage is that a single Connection Monitor resource can define multiple endpoint pairs (source-destination) regardless of their geographic location. Since the West US 2 region already has a Network Watcher and presumably the infrastructure to support a Connection Monitor, you can configure it to monitor both the Seattle datacenter and the East US 2 public Azure region from this single point.

Why the Other Options Are Wrong

Option C suggests creating a Network Watcher in East US 2. This adds unnecessary administrative effort because Network Watcher is a regional control plane; you do not need a separate instance in every region to perform monitoring tasks if you are leveraging features like Connection Monitor which can span regions. Option B lists reachability providers, which is for discovery, not active measurement of latency. Option A runs a cmdlet to get existing monitors, but does not address the setup or configuration needed to document the specific latencies requested.

Community Comment Notes

Community consensus strongly supports Option D. Users noted that Connection Monitor is the correct tool for documenting latency between regions. One user asked why D is correct when a Connection Monitor might already exist, highlighting confusion about whether to create a new one or use an existing one; however, in the context of exam questions, "Create" often implies ensuring the resource exists or configuring the solution, and since no existing monitor was stated, creating/configuring it in the available region is the standard answer. The comments reinforce that Connection Monitor is the specific feature for measuring these metrics.

Exam Strategy

When asked to minimize administrative effort in Azure networking scenarios, look for services that allow centralized management or cross-region capabilities rather than deploying duplicate resources in every region.

Frequently Asked Questions

Can one Connection Monitor monitor endpoints in different Azure regions?

Yes, a single Connection Monitor resource can monitor multiple endpoint pairs, including those in different Azure regions and on-premises locations.

Why not create a Network Watcher in East US 2?

Network Watcher is a regional control plane. You don't need a new instance in every region to perform monitoring; Connection Monitor in one region can handle cross-region checks.

More AZ-700 FAQ →

Community Votes

D
83%
C
17%

83% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. Saba53 👍 2 Answered D
    D should be correct - Create a Connection Monitor resource in the West US 2 region
  2. Vokuhila 👍 2 Answered D
    Use connection monitor if you want to document the latency between regions
  3. a250fb0 👍 1 Answered D
    To document network latency between your on-premises datacenter and Azure regions (West US 2 and East US 2), you need to use Azure Network Watcher's Connection Monitor. This tool measures communication metrics such as latency, reachability, and packet loss between endpoints.
  4. LearnICC 👍 1 Answered C
    why D ? there is already a Connection Monitor resource in the West US 2 region

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Private Endpoint UDR Routing Prerequisite

S-grade

Minimum Azure Service Endpoints for Peered VNets

S-grade

Logging Application of Specific NSG Rules

S-grade

Azure DNS Private Resolver Minimum Deployment

S-grade

Practice All AZ-700 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-700 Practice Test →

← Back to AZ-700 Study Guide