Question 640
After completing this practical task on a local virtualization classroom: A team is shutting down a disposable server immediately but an operator issues `reboot` instead of a power-off. Which operational safeguard helps keep the result correct and safe?
Explanation
Correct Answer
Include explicit action and target hostname in approved shutdown runbooks. This guards against recurrence of: Poweroff and reboot invoke different system state transitions. Confirm the lab's final state by: The VM reaches its powered-off state rather than returning to login after restart.
Incorrect Answers
Trend memory and paging activity together under representative workload. That control is best suited to a separate scenario: A running VM has adequate memory by `free -h` but swap usage spikes and the team assumes the application is leaking. It is not the best safeguard for the current mechanism: Poweroff and reboot invoke different system state transitions.
Use precise filters in incident collection to retain reproducible evidence. That control is best suited to a separate scenario: A system journal contains many warnings and the student must isolate kernel-related messages for the current boot. It is not the best safeguard for the current mechanism: Poweroff and reboot invoke different system state transitions.
Include validation, supported reload or restart, and functional checks in deployment procedures. That control is best suited to a separate scenario: An application configuration was changed on disk, but the running daemon still uses the previous settings. It is not the best safeguard for the current mechanism: Poweroff and reboot invoke different system state transitions.