Exam AZ-700 topic 4 question 19 discussion

Answer is B. The Connection Monitor is established per region. And depending on the region we can connect multiple VMS, VMSS, endpoints and on-premises devices. Since, we have two regions only, we will need to Connection Monitors.

Tested Source : must be in the same region / VM or VMSS Target : region doesn't matter / VM, URL, etc. ConnecitonMonitor1 : VM1, VM3 --> other resources ConnecitonMonitor2 : VM2 --> other resources

B - 2 - Connection monitor is a regional resource - https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#before-you-begin

Appeared on Exam November -2023

B Is Honey.. As per MS guidelines *Region: Select a region for your connection monitor. You can select only the source VMs that are created in this region. Here you see only VMs or Virtual Machine Scale Sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale Sets are grouped into the subscription that they belong to * Destination can be anywhere as per this Destinations: You can monitor connectivity to an Azure VM, an on-premises machine, or any endpoint (a public IP, URL, or FQDN) by specifying it as a destination. In a single test group, you can add Azure VMs, on-premises machines, Office 365 URLs, Dynamics 365 URLs, and custom endpoints. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal

2 in my opinion. At least two because we have two regions and the as the documentation says "You can select only the source VMs that are created in this region" - we need to measure from East US where is located VM1, VM3 and from UK West where is VM2. Not more than two because in each one we can play with groups of sources and destinations. - Connection Monitor 1 from UK West --- Source VM2 --- Destinations App1 and ST1 - Conection Monitor 2 from East US --- Source Groups VM1, VM3 --- Destinations App1 and ST1 https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-overview#create-a-connection-monitor-1

At this link: https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#create-test-groups-in-a-connection-monitor It states as part of the test group creation process: To choose Azure agents, select the Azure endpoints tab. Here you see only VMs or Virtual Machine Scale Sets that are bound to the region that you specified when you created the connection monitor. This confirms that you would need 1 connection monitor per region. So the correct answer is B.

Correct: B

In exam Feb, 2023

Connection monitor is regional resource but destination VM can be in any region.

Connection monitor resource is a region-specific Azure resource

will go with B .. per region 1 monitor but can add multiple sources and destinations

my previous answer was wrong, sorry for the confusion: In the UK West region, there is only a single virtual machine (VM2). You do not need to create a connection monitor for this resource, as there are no other resources in the region to connect to. In the East US region, there are two virtual machines (VM1 and VM3) and an App Service (App1). To check the latency between these resources, you would need to create the following connection monitors: VM1 and VM3: This connection monitor would test the latency between VM1 and VM3 in the East US region. VM1 and App1: This connection monitor would test the latency between VM1 and App1 in the East US region. VM3 and App1: This connection monitor would test the latency between VM3 and App1 in the East US region. Overall, you would need to create a total of three connection monitors to check the latency between all of the resources in the East US region.

To check the latency between the resources in the table you provided, you would need to create a minimum of four connection monitors. The correct answer is therefore D. A connection monitor in Azure Network Watcher is a tool that allows you to continuously test connectivity between two resources. It sends a series of packets to a specified destination at a specified interval, and measures the round-trip time (RTT) of the packets. In this case, you would need to create at least one connection monitor for each pair of resources that you want to monitor. For example: VM1 and App1 (located in the same resource group and VNet) VM2 and St1 (located in different resource groups and VNets) VM3 and VM1 (located in the same region, but with different resource groups and VNets) This would require a minimum of four connection monitors to cover all of the resources in the table.

B is correct

each connection monitor can have multiple sources and destinations, but can only be set up in 1 region, because question provides 2 regions, we need 2 separate connection monitors, so B

Takes a few seconds to try to create a connection monitor in the portal : Connection Monitor enables you to monitor connectivity in your Azure and hybrid network. Select your preferred subscription and REGION from which monitoring will be performed.