VCP550 · Question #21
What is a valid plug-in status for a plug-in that has been added to a vSphere client?
The correct answer is A. Disabled. vSphere Client plug-ins can have one of several statuses after being added; Disabled is a valid and recognized status in the Plug-in Manager.
Question
What is a valid plug-in status for a plug-in that has been added to a vSphere client?
Options
- ADisabled
- BUnknown
- CStopped
- DInstalled
How the community answered
(38 responses)- A95% (36)
- C3% (1)
- D3% (1)
Why each option
vSphere Client plug-ins can have one of several statuses after being added; Disabled is a valid and recognized status in the Plug-in Manager.
After a plug-in is added to the vSphere Client, it can be in one of two primary operational states: Enabled or Disabled. Disabled is a valid status indicating the plug-in has been registered but is not currently active. Administrators can toggle plug-ins between Enabled and Disabled from the Plug-in Manager interface.
Unknown is not a defined plug-in status in the vSphere Client Plug-in Manager and does not appear as an assignable state for registered plug-ins.
Stopped is not a valid plug-in status in the vSphere Client; plug-ins are tracked as Enabled or Disabled, not by service-like running states.
Installed is not a recognized status label in the vSphere Client Plug-in Manager; the status field reflects operational state, not installation presence.
Concept tested: vSphere Client plug-in valid status values
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-76B07CF9-E50A-4766-891A-B53E7CA91C8E.html
Topics
Community Discussion
No community discussion yet for this question.