Question 670
After a lab configuration change, verify: A lab system needs a controlled reboot after updates but the operator plans to unplug the virtual power without syncing writes. Which result most directly proves the desired system state?
Explanation
Correct Answer
The host restarts cleanly, and journal boot IDs show the new boot. This check confirms the expected effect of: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes. It distinguishes the intended result from the original failure mechanism: An orderly reboot coordinates service shutdown and filesystem synchronization.
Incorrect Answers
The VM reaches its powered-off state rather than returning to login after restart. That verifies a separate lab task: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.
After generating and rebooting the fixture, `journalctl --list-boots` shows earlier boot entries. That verifies a separate lab task: A lab incident must be reconstructed after reboot but `journalctl -b -1` has no previous-boot records due to volatile journaling. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.
`systemctl get-default` reports `multi-user.target`, including after reboot. That verifies a separate lab task: A multi-user server is configured to boot into a graphical session, while the training task requires a command-line default. It does not validate the implementation required here: Use `sudo systemctl reboot` after closing applications and checking there are no pending critical writes.