You have an on-premises network.
You have an Azure subscription that contains three virtual networks named VNET1. VNET2. and VNET3. The virtual networks are peered and connected to the on-premises network. The subscription contains the virtual machines shown in the following table.
You need to monitor connectivity between the virtual machines and the on-premises network by using Connection Monitor.
What is the minimum number of connection monitors you should deploy?
To monitor connectivity between the virtual machines and the on-premises network using Connection Monitor, you need to consider the region-specific nature of the Connection Monitor resource in Azure Network Watcher. In this scenario, the virtual machines are located in two different regions: West US and Central US. As Connection Monitor is region-specific, you need to deploy one Connection Monitor in each region to cover all virtual machines. Therefore, the minimum number of connection monitors required is 2.
Connection monitor resource: A region-specific Azure resource. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#before-you-begin
The correct answer is A. 1. Azure’s Connection Monitor in Network Watcher provides unified, end-to-end connection monitoring1. It supports hybrid and Azure cloud deployments, and it can monitor communication between a virtual machine (VM) or virtual machine scale set and another endpoint1. In this scenario, you have an on-premises network and three virtual networks (VNET1, VNET2, and VNET3) in Azure that are peered and connected to the on-premises network. You need to monitor the connectivity between these virtual machines and the on-premises network. Since all the virtual networks are peered and connected to the on-premises network, you can use a single connection monitor to monitor the connectivity between the virtual machines and the on-premises network.
Cleared Exam today 26 Feb, This question was there in exam.
So you came back, scrolled through all of the ~450 questions until you found the ones which where in your exam and posted this because of altruism? I dont think so.
Why wouldn't you believe that? This is a great deed from someone who just took the exam and is back to help the others. I appreciate this.
good notice my loyal minion! that creature has posted same message on 34 questions I have used the power of google to track it! Its a marketing bot. or a very strange being
you are right !!
You should thank him instead
so what? you could've passed while getting this specific question wrong
this kind of answer deserve to be banned
Answer: B Select a region for your connection monitor. You can select only the source VMs that are created in this region. As we have two regions, we need to create to connection monitors. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#create-a-connection-monitor
this question came in the exam 25/9/2023
Its B Region: Select a region for your connection monitor. You can select only the source VMs that are created in this region. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#before-you-begin
I think this is the right reason to choose B, may I ask if you tried it on the lab?
The answer is B. 2 minimum connection monitors. The reason is you have on-premises network and Azure(Cloud) network. So, you need 2. This is nothing to do with the location: West US and Central US. This is a trap! Someone people said it's to do with these 2 locations. But that is the wrong explanation. If you only have 1 kind of network(Azure Cloud/on-premises, then you need minimum 1 connection monitor.
You need 1 C monitor to check connectivity between west US and op-prem. Another to check between central US and on-prem So 2.
Azure's Connection Monitor is a feature within Network Watcher that enables you to monitor communication at a regular interval and visualize network performance parameters. Since the virtual networks (VNET1, VNET2, and VNET3) are peered and connected to the on-premises network, the communication between any virtual machine within these VNets and the on-premises network can be seen as part of a single connected network. Given that the VNets are peered, the minimum number of connection monitors you would need to deploy to monitor connectivity from all virtual machines in your Azure subscription to the on-premises network would be: A. 1 One connection monitor can track the connectivity of multiple virtual machines to a single on-premises endpoint as long as they are within peered VNets and there are no restrictions preventing communication between these networks. You can configure the connection monitor with all the virtual machines as sources and the on-premises network as the destination.
The correct answer is A. 1. Azure’s Connection Monitor in Network Watcher provides unified, end-to-end connection monitoring. It supports hybrid and Azure cloud deployments, and it can monitor communication between a virtual machine (VM) or virtual machine scale set and another endpoint. In this scenario, you have an on-premises network and three virtual networks (VNET1, VNET2, and VNET3) in Azure that are peered and connected to the on-premises network. You need to monitor the connectivity between these virtual machines and the on-premises network. Since all the virtual networks are peered and connected to the on-premises network, you can use a single connection monitor to monitor the connectivity between the virtual machines and the on-premises network.
B is right
This was on my exam. I think the suggested answer to the question is correct.
2 regions = 2 connection monitors
By deploying one Connection Monitor from any VM, you can effectively monitor the connectivity for all VMs across the peered virtual networks to the on-premises network. The question is asking for a minimum number.
The correct answer is A. 1. Azure’s Connection Monitor in Network Watcher provides unified, end-to-end connection monitoring1. It supports hybrid and Azure cloud deployments, and it can monitor communication between a virtual machine (VM) or virtual machine scale set and another endpoint. In this scenario, you have an on-premises network and three virtual networks (VNET1, VNET2, and VNET3) in Azure that are peered and connected to the on-premises network. You need to monitor the connectivity between these virtual machines and the on-premises network. Since all the virtual networks are peered and connected to the on-premises network, you can use a single connection monitor to monitor the connectivity between the virtual machines and the on-premises network.
As for now - correct response is A - 1. When comes to MS Azure Docs, it barely mention a case like this. But it says that is Cross-Region and Cross-Workspace. The line which says "A region-specific Azure resource" is for the service itself where is gonna to deploy, store logs, etc., not for the regions which it can monitor.
So what is the answer A or B? :)
I think answer is A = 1 Connection monitor will be enough since Vnets are peered Also, here says max Connection non per region is 100 https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#scale-limits
Connection monitor resource: A region-specific Azure resource. All the following entities are properties of a connection monitor resource. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal
I checked the portal https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal The unique parameter is the "region" while creating a connection monitor and nothing else. Since we have 2 regions in this question, the answer shud be 2