VCP550 · Question #79
An administrator needs to create an alarm to monitor when a specific ESXi host in an HA/DRS cluster becomes disconnected from other vSphere components like HA agents or the vCenter server. Which proce
The correct answer is A. Define a Host type alarm, monitor for the event Cannot connect host, and supply a conditional. Monitoring a specific ESXi host for disconnection requires a Host type alarm using the 'Cannot connect host' event, which directly captures failures in host-to-vCenter and HA agent communication.
Question
An administrator needs to create an alarm to monitor when a specific ESXi host in an HA/DRS cluster becomes disconnected from other vSphere components like HA agents or the vCenter server. Which process must the administrator use to accomplish this?
Options
- ADefine a Host type alarm, monitor for the event Cannot connect host, and supply a conditional
- BDefine a Cluster type alarm, monitor for the event Cannot connect host, and supply a conditional
- CDefine a Cluster type alarm, monitor for the event Host status changed, and supply a specific label
- DDefine a Host type alarm, monitor for the condition Host status changed, and supply a specific label
How the community answered
(17 responses)- A76% (13)
- B12% (2)
- C6% (1)
- D6% (1)
Why each option
Monitoring a specific ESXi host for disconnection requires a Host type alarm using the 'Cannot connect host' event, which directly captures failures in host-to-vCenter and HA agent communication.
Defining the alarm on a Host type object scopes it to the specific ESXi host in question rather than the entire cluster. The 'Cannot connect host' event is the precise trigger that fires when vSphere loses connectivity to the host from vCenter Server or HA agents, matching the described monitoring requirement exactly.
A Cluster type alarm applies to the cluster object as a whole, not to a specific host, so it cannot target an individual host's disconnection event.
A Cluster type alarm is the wrong object scope for monitoring a single host, and 'Host status changed' is a general condition that does not specifically capture the network or agent disconnection scenario described.
'Host status changed' is a broad condition that does not specifically indicate a host has lost connectivity to vCenter or HA agents; 'Cannot connect host' is the event that precisely maps to the described disconnection scenario.
Concept tested: Defining host disconnection alarms in vCenter
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-52088CB4-C629-4BA4-A92A-9B5EA4F65CC1.html
Topics
Community Discussion
No community discussion yet for this question.