2V0-622 · Question #124
An administrator wants to power on a virtual machine (VM) while connected to an ESXi host using SSH. The VM has the following Name and ID: -VM Name = SQL001 -VMID = 12345 Which command would…
The correct answer is A. vim-cmd vmsvc/power.on 12345. The correct ESXi command-line tool for VM power operations is vim-cmd, and it requires the numeric VMID, not the VM name.
Question
An administrator wants to power on a virtual machine (VM) while connected to an ESXi host using SSH. The VM has the following Name and ID:
-VM Name = SQL001 -VMID = 12345 Which command would successfully power on the virtual machine?
Options
- Avim-cmd vmsvc/power.on 12345
- Bvim-cmd vmsvc/power.on SQL001
- Cvmware-vim-cmd vmsvc/power.on 12345
- Dvmware-vim-cmd vmsvc/power.on SQL001
How the community answered
(56 responses)- A88% (49)
- B7% (4)
- C2% (1)
- D4% (2)
Why each option
The correct ESXi command-line tool for VM power operations is vim-cmd, and it requires the numeric VMID, not the VM name.
The vim-cmd utility is the correct command on ESXi hosts for interacting with the VMware infrastructure API from the shell. The vmsvc/power.on subcommand takes a numeric VMID as its argument, which in this case is 12345. Using the correct tool name and the numeric ID is the only form that will successfully power on the VM.
vim-cmd is the correct tool, but vmsvc/power.on requires a numeric VMID, not a string VM name like SQL001; passing a name will result in an error.
vmware-vim-cmd is not a valid ESXi command; the correct binary name is vim-cmd, so this command will fail with a 'command not found' error regardless of the argument.
vmware-vim-cmd is not a valid ESXi command, and additionally the argument SQL001 is a name rather than the required numeric VMID, making this doubly incorrect.
Concept tested: ESXi vim-cmd power on VM using VMID
Source: https://knowledge.broadcom.com/external/article/315964/using-the-vimcmd-command-on-esxi.html
Topics
Community Discussion
No community discussion yet for this question.