Sticking with A for this, since Log Analytics workspace natively supports KQL and is built for monitoring workloads like SQL on VM. Minimal setup compared to Event Hubs. Pretty sure that's what MS expects here, but correct me if I've missed some edge case.
Q: 8
You have an instance of SQL Server on Azure Virtual Machine named SQL1.
You need to monitor SQL1 and query the metrics by using Kusto query language. The solution must
minimize administrative effort.
Where should you store the metrics?
Options
Discussion
Option A is right here. Log Analytics workspace is built for Kusto queries and makes monitoring SQL on VMs straightforward. Event Hubs (B) isn’t really for metric analysis, more for streaming events. Anyone disagree?
Seriously, Microsoft loves shoving everything into Log Analytics these days. Option A since it's KQL native and way less hassle than piping to Event Hubs or rolling custom storage. Let me know if I'm missing something but pretty confident here.
A , Log Analytics workspace is where you get native KQL support with minimal setup. Event Hubs would need extra steps just to get those queries working. Pretty sure A lines up best with what the question asks, but open if anyone disagrees.
I don’t think it’s A. Option B could also store metrics and integrate with analytics tools, especially if you need to stream data elsewhere. Feels like a common trap to assume Log Analytics is always the go-to.
Probably A here. Log Analytics workspace is KQL native and keeps admin work low.
B , Event Hubs could work if you're thinking about streaming telemetry data and plugging it into other analytics tools. I figured it's less admin effort than setting up the workspace from scratch. Maybe I'm missing a KQL native angle here though.
A , Log Analytics workspace is the only one built for KQL with low admin work.
A tbh . Shrinking the log just frees up disk space, it doesn't address PAGELATCH_UP wait types. Those usually point to tempdb or hot page contention, not something you fix by messing with the log file. Trap answer here! Someone else see it differently?
Its A, official guide and practice labs both mention Log Analytics for KQL with least admin effort.
Be respectful. No spam.
Question 8 of 35