Q: 12
An administrator has received reports of high CPU ready times on several Virtual Machines (VMs)
running within a VMware Cloud Foundation (VCF) with error" F.iain and has been tasked with
collecting detailed metrics for all running Virtual Machines from each ESX host.
com.vmware.esx.setungs_aaemon.sonware.scan_spec.".
What is the cause of this error?
Options
Discussion
I saw a similar scenario in official labs, and missing the default image always throws this kind of settingsdaemon scan_spec error. So it's A. Check the VMware docs or hit the hands-on labs to see this in action. Pretty confident here.
Had something like this in a mock, would option B not make sense if the cluster image was recently changed or parts removed?
A for sure
A imo. I remember a similar question from an exam report, and it was always about the cluster not having a default image set so the compliance scan fails right away.
B or D? Saw both come up as distractors in practice exams and the official guide so not sure.
A tbh, it's all about the cluster missing a default image which is needed for vLCM scans. The error ties directly to image assignment, not component removal or drivers. Pretty sure that's it unless I missed something in the scenario.
A saw something similar in practice tests and the official guide covers this cluster image assignment missing scenario.
Option D's a trap here, error's about missing cluster image not driver/firmware. Pretty sure it's A.
A had something like this in a mock. Missing default cluster image causes those compliance scan errors.
Be respectful. No spam.
