2V0-621 · 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. On ESXi hosts, the vim-cmd utility powers on VMs by their numeric VMID, making vim-cmd vmsvc/power.on 12345 the correct syntax.
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
(18 responses)- A89% (16)
- C6% (1)
- D6% (1)
Why each option
On ESXi hosts, the vim-cmd utility powers on VMs by their numeric VMID, making vim-cmd vmsvc/power.on 12345 the correct syntax.
The vim-cmd command is the correct CLI utility available on ESXi hosts for managing virtual machines via the vmsvc namespace. The power.on subcommand requires a numeric VMID as its argument, not the VM display name. Using vim-cmd vmsvc/power.on 12345 matches both the correct tool name and the correct identifier type.
vim-cmd vmsvc/power.on requires a numeric VMID, not a string VM name like SQL001; passing the name instead of the ID will cause the command to fail.
vmware-vim-cmd is not a valid command on ESXi hosts; the correct utility name is vim-cmd, so this command would return a command not found error.
vmware-vim-cmd is not a valid ESXi command, and even if it were, the argument would need to be a numeric VMID rather than the VM display name SQL001.
Concept tested: ESXi vim-cmd CLI syntax for VM power operations
Source: https://knowledge.broadcom.com/external/article?legacyId=1006195
Topics
Community Discussion
No community discussion yet for this question.