This scenario clearly indicates a memory exhaustion condition, which falls under the Troubleshooting domain of the CompTIA Linux+ V8 objectives. The most critical clue is the log entry stating that mysqld invoked oom-killer.
The OOM (Out-Of-Memory) killer is a Linux kernel mechanism that activates when the system runs critically low on available memory and cannot satisfy memory allocation requests. When this happens, the kernel selects a process-typically one consuming a large amount of memory-and forcibly terminates it to protect overall system stability. In this case, the MySQL daemon (mysqld) was identified as the process responsible for triggering the OOM condition.
The journalctl output explicitly confirms this behavior. Linux+ V8 documentation emphasizes that when the OOM killer is invoked, it is almost always due to physical memory exhaustion or insufficient swap space, not user intervention or application bugs alone. The additional log line showing mems_allowed=0 further supports the conclusion that the process could not allocate memory from available memory nodes.
The fact that uptime -p reports only 2 minutes of uptime strongly suggests that the system was either rebooted automatically or manually following the memory exhaustion event. Systems may reboot as part of recovery procedures after severe resource exhaustion, especially in production environments.
The other options can be ruled out. There is no indication of a user-initiated kill signal, filesystem corruption, or network connectivity issues. Network outages would not generate OOM killer messages, and filesystem errors would appear as I/O or disk-related errors in the logs.
Linux+ V8 best practices recommend addressing OOM issues by increasing system memory, tuning MySQL memory parameters, configuring swap space, or adjusting OOM scoring.
Therefore, the correct explanation is A. The process exhausted server memory.

In Linux system management, controlling processes and job execution is a fundamental skill covered extensively in the CompTIA Linux+ V8 objectives. The command shown combines two important concepts:
nohup and background execution using &.
The nohup command is used to run a process immune to hangup signals, meaning the process continues running even after the user logs out or the terminal session ends. By default, nohup detaches the process from the controlling terminal and redirects standard output and standard error to a file named nohup.out. When the ampersand (&) is appended, the process is immediately placed into the background, allowing the shell prompt to return without waiting for the command to finish.
Linux provides job control mechanisms that allow users to manage background and foreground processes within a shell session. The fg command is specifically designed to bring a background job into the foreground and reattach it to the current terminal. Once a job is in the foreground, it can receive input from the terminal and display output directly, and it can also be interrupted using signals such as Ctrl+C.
The other answer choices do not fulfill this requirement. The renice command is used to change the scheduling priority of a running process but does not affect terminal attachment. The jobs command only lists background and stopped jobs associated with the current shell and does not modify their execution state. The exec command replaces the current shell process with a new process, which is unrelated to resuming or attaching background jobs.
According to Linux+ V8 documentation and job control best practices, the correct command to attach a background process to the current terminal is fg. Therefore, option D is the correct answer.

In Linux, the ability to execute a program by typing only its name depends on whether the directory containing the executable is included in the user's PATH environment variable. The PATH variable defines a colon-separated list of directories that the shell searches when a command is entered.
Option C, export PATH=$PATH:/home/user/scripts, correctly appends the /home/user/scripts directory to the existing PATH variable. Once this command is executed, any executable script located in that directory can be run simply by typing its filename, provided the script has execute permissions. This behavior is explicitly covered in the Linux+ V8 objectives related to environment variables and shell configuration.
The other options are incorrect. Option A incorrectly attempts to redefine the SHELL variable and uses invalid syntax. Option B modifies the TERM variable, which controls terminal type and has nothing to do with command execution. Option D attempts to create an alias using invalid syntax and would not affect command lookup behavior.
Linux+ V8 documentation emphasizes modifying the PATH variable as the standard and recommended method for simplifying script execution. This approach is commonly used by developers and administrators who frequently run custom scripts.
Therefore, the correct answer is C.