1V0-601 · Question #107
You are the VMware Administrator for the local city government. When you arrive at your desk, you find that there are several alarms referring to an outage caused by an overnight driver update. When…
The correct answer is B. vCenter Configuration Manager (vCCM). See the full explanation below for the reasoning.
Question
You are the VMware Administrator for the local city government. When you arrive at your desk, you find that there are several alarms referring to an outage caused by an overnight driver update. When you ask your colleagues about the driver update, no one seems to know anything about it. Which solution will help in determining the problem?
Options
- AA PowerShell script to gather hardware driver versioning information
- BvCenter Configuration Manager (vCCM)
- CThe vCenter Virtual Appliance
- DvProtect
How the community answered
(20 responses)- A5% (1)
- B75% (15)
- C15% (3)
- D5% (1)
Community Discussion
5The answer is B, vCenter Configuration Manager. vCCM is specifically built to track and audit configuration changes across your vSphere environment, so when a mystery driver update causes alarms overnight, it gives you a full change history to pinpoint exactly what changed, when, and on which hosts.
Solid, and the exam trap worth a dedicated card is the distinction between vCCM for configuration drift and change history versus vRealize Log Insight for event and syslog analysis, because the two get swapped constantly under pressure.
The answer is B, vCenter Configuration Manager, and the reasoning is straightforward once you focus on the actual problem, which is an undocumented change, not just a broken driver. A PowerShell script (option A) is the obvious trap here because it feels like the technical, hands-on move, but it only tells you what driver version is running right now, not who changed it or when, so you are still in the dark about the source. vCCM tracks configuration drift and change history across your environment, which is exactly the audit-trail capability you need when colleagues deny touching anything. Make a card for this one with the front asking what VMware tool provides configuration change tracking and compliance auditing, because the exam loves to test whether you can distinguish between a tool that reads current state versus one that records change history.
Think of your city hall's paper trail. Every permit issued, every zoning change approved, every inspection signed off gets logged in a central records book so that six months later you can flip back and say, "Here is exactly who changed what and when." vCenter Configuration Manager is that records book for your virtual infrastructure, tracking configuration drift and change history across your hosts so that even if no human coworker will admit to touching the driver, the system's audit trail can tell you which host was changed, what the driver version was before and after, and roughly when it happened. Option B is correct because vCCM gives you the historical change visibility to trace an unauthorized or unacknowledged update, which is precisely the kind of forensic detail you need here. A PowerShell script in option A could tell you what driver version is on a host right now, but it cannot reach back in time and show you the change event that caused the alarm.
Good breakdown, and to add one more angle, vCCM does not just log that a change happened but can also flag it against a compliance baseline so you get both the forensic trail and an automatic "this violated policy X" signal in the same tool, which is something a PowerShell one-liner definitely cannot do on its own.