Q: 2
A customer complains of poor VM performance. Which TWO infrastructure metrics would provide the
BEST starting point for analysis?
Options
Discussion
A and B tbh, I've seen similar questions in practice and tape backup (C) is a bit of a distractor here. Disk IOPS latency is way more relevant for VM performance. Anyone else think C was a trap?
A and B tbh, C is tempting but tape speed isn't usually tied to active VM slowness. Seen this type on other exams.
I'd go A and B here.
A and B tbh, D is a trap because switch LEDs don't reflect VM-level issues at all.
A and B, those are the two metrics you want to check first for VM lag. CPU ready time spots processor contention, while disk IOPS latency will show storage issues. Could be wrong, but these cover most performance problems in my experience. Agree?
A and B tbh, those target CPU and storage bottlenecks which are usually the core issues for VM performance. Tape and switch status aren't really relevant to VM slowdowns. Pretty sure this is the right pair, but open to other views.
A and C would be my first guess, since CPU ready time is definitely relevant for VM lag, but I thought tape backup speed (C) could impact overall performance too if jobs are running during peak hours. Not totally certain though. Maybe someone disagrees?
Agreed, A and B.
Maybe A and B had something like this in a mock, those are the usual starter metrics for VM slowdowns.
Not C or D. CPU ready time (A) and disk IOPS latency (B) are the key VM perf metrics-always start there for bottleneck hunting. Tape and switch LEDs just don't tell you anything about hypervisor contention. Seen questions like this before, pretty sure it's A and B.
Be respectful. No spam.
