220-1102 Operating Systems Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  taskkill

  Why it's wrong here

  `taskkill` is a process-management command that terminates running applications or processes by image name or PID. While it supports remote targeting via the `/s`, `/u`, and `/p` switches (for computer, username, and password), it only ends user-mode or system processes, and it cannot initiate a Windows shutdown or restart. The underlying API it uses (`TerminateProcess`) is fundamentally different from the `ExitWindowsEx` function used by the shutdown command. Thus, `taskkill` will not shut down the remote operating system and is the wrong choice.

• ✓

  shutdown

  Why this is correct

  The `shutdown` command is the built-in Windows utility designed to shut down, restart, or log off a local or remote computer. To remotely shut down a machine in a domain, you would use `shutdown /s /m \\computername`, where `/s` specifies a full shutdown and `/m` targets the remote host. This command leverages the remote shutdown RPC interface and requires the user to have administrative privileges on the target system. It is the standard, reliable method for remotely shutting down a domain-joined Windows computer, making it the only correct option here.

• ✗

  net stop

  Why it's wrong here

  The `net stop` command is specifically designed to stop a Windows service or driver, not to shut down the operating system. It requires a service name as an argument, and while you can stop a service on a remote machine using `net stop \\computername service`, doing so does not power off or restart that computer. Even in a domain environment, `net stop` cannot trigger an OS-level shutdown; it only changes the running state of a service. Therefore, it is entirely incorrect for remotely shutting down the target machine.

• ✗

  wmic

  Why it's wrong here

  WMIC can query WMI objects to trigger a shutdown via the `Win32_OperatingSystem` class, but it requires the target machine to have WMI enabled, appropriate firewall rules, and the user to have administrative privileges on the remote system—conditions not guaranteed in a standard domain environment. It is tempting because WMIC is often used for remote system management tasks like querying hardware or software inventories, where it would be the correct choice for retrieving configuration data rather than executing a shutdown command.

Go deeper

Related to this question