Q: 1
You have a hybrid environment that uses ExpressRoute to connect an on-premises network and
Azure.
You need to log the uptime and the latency of the connection periodically by using an Azure virtual
machine and an on-premises virtual machine.
What should you use?
Options
Discussion
Option C but only because Connection Monitor can actually track both latency and uptime across ExpressRoute hops. If this was just about internet endpoints, D might make sense. Anyone see docs saying otherwise?
Don’t think A works here. C is designed to actually monitor connectivity and latency between Azure and on-prem via ExpressRoute. Azure Monitor just pulls logs and basic metrics, not real path testing. Makes sense to me, but let me know if you read it differently.
Yep, has to be C. Only Connection Monitor checks both uptime and latency across hybrid, especially with ExpressRoute. Azure Monitor is more for collecting generic metrics, it won't test the actual network path. That's how I see it, but happy to hear other thoughts if someone disagrees.
C is right. Only Connection Monitor can do end-to-end uptime and latency checks between Azure VMs and on-prem via ExpressRoute. A looks tempting but Azure Monitor doesn't test the network connection itself, just aggregates metrics. Pretty sure this is a common trap on practice tests.
Is the requirement to monitor just ExpressRoute or all network links? If it’s only ExpressRoute, that could affect which option fits.
Nah, I don't think Azure Monitor (A) is enough for this one. C is the right pick here because Connection Monitor is designed specifically to track uptime and latency between Azure and on-prem, especially over ExpressRoute. Option A's a common trap since it's more about resource metrics, not network paths.
Every freakin Azure networking question lately wants Connection Monitor. C, since it tracks uptime and latency between Azure and on-prem, exactly what they're asking for. Pretty sure that's what you'd see on practice tests.
Maybe C, had something like this in a mock and Connection Monitor was the right call.
C/D? If internet-facing endpoints, D could fit, but hybrid with ExpressRoute sounds like C is expected.
C here, since Connection Monitor is built for checking both uptime and latency between Azure and on-prem across ExpressRoute. Azure Monitor doesn't do network-level checks like this. Pretty sure that's what the question wants, but open to corrections.
Be respectful. No spam.