nerdexam
Broadcom-VMware

2V0-620 · Question #149

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 have specific recognized statuses, and 'Disabled' is a valid state for a plug-in that has been added but not yet activated.

Section 5 – Administer and Maintain vSphere

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

(20 responses)
  • A
    85% (17)
  • B
    5% (1)
  • D
    10% (2)

Why each option

vSphere Client plug-ins have specific recognized statuses, and 'Disabled' is a valid state for a plug-in that has been added but not yet activated.

ADisabledCorrect

After a plug-in is added to the vSphere Client, it can be set to either Enabled or Disabled state via the plug-in manager. 'Disabled' is a valid and recognized status indicating the plug-in is registered but not currently active. Administrators can toggle this state without removing the plug-in.

BUnknown

'Unknown' is not a standard, valid status displayed in the vSphere Client plug-in manager for a successfully added plug-in.

CStopped

'Stopped' is not a recognized plug-in status in the vSphere Client; plug-ins use Enabled/Disabled terminology, not running-state terminology.

DInstalled

'Installed' is not a labeled status field in the vSphere Client plug-in manager interface; the state reflects activation, not installation.

Concept tested: vSphere Client plug-in manager valid statuses

Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-BE3A4D0E-3A53-4F0E-9C3A-7F6B0C5F8D2E.html

Topics

#vSphere client#plug-in management#plug-in status

Community Discussion

No community discussion yet for this question.

Full 2V0-620 Practice