A Linux system administrator notices that the journal logs on a production server are not persistent across reboots, which is necessary for troubleshooting ongoing issues that occur after system restarts. What's the BEST step the administrator should take to ensure journal logs are retained after a reboot?
Implement logrotate on /run/log/journal to ensure the logs are preserved after reboots.
Modify the 'Storage=' setting in '/etc/systemd/journald.conf' to 'persistent' and reboot the server.
Create the /var/log/journal directory and restart the systemd-journald service.
Reboot the server to trigger a new instance of systemd-journald, which will then keep the logs.