An administrator needs to modify a virtual machine alert to increase the threshold value of the trigger. Once connected to the vCenter Server, the administrator navigates to the virtual machine to make the change. However, the administrator is unable to edit the alarm. What is the reason that this alarm cannot be edited?

Question

Accepted Answer

A. The alarm was not defined on this inventory object. vSphere alarms are inherited down the inventory hierarchy - an alarm defined on a datacenter or cluster appears on all child objects such as individual VMs. However, you must navigate to the specific object where the alarm was originally created to edit it; the alarm definition is not local to the child object, so the edit option is unavailable there.

Answer

B. The administrator is not the owner of this inventory object. vSphere does not have an 'owner' concept for inventory objects that restricts alarm editing; access is controlled by roles and privileges, not object ownership.

Answer

C. The alarm was not created by the administrator. Alarm editing permission is based on where the alarm was defined in the hierarchy and the user's privileges, not on which specific account originally created it.

Answer

D. The alarm has not been acknowledged. Acknowledging an alarm clears its visual alert state but has no effect on whether the alarm definition can be modified; acknowledgment and editing are unrelated operations.

An administrator needs to modify a virtual machine alert to increase the threshold value of the trigger. Once connected to the vCenter Server, the administrator navigates to the virtual machine to mak

Question

Options

How the community answered

Why each option

Topics

Community Discussion