interrupts

The command chmod g+s sales sets the setgid bit on the directory sales, which means that any new file or subdirectory created within sales will inherit the group ownership of the directory. The command chmod 2775 sales does the same thing, but also sets the permissions of the directory to rwxrwxr-x, which means that the owner, group, and others can read, write, and execute files in the directory. Both commands ensure that new files created within the directory sales are owned by the group sales. The other commands are either invalid or do not affect the group ownership of new files. References:
* Linux Essentials - Linux Professional Institute Certification Programs1
* Exam 101 Objectives - Linux Professional Institute

This command will run dbmaint in the background and make it immune to hangup signals, which means it will continue to run even when the user logs out of the system. The nohup command prefixes the command with nohup, which intercepts the SIGHUP signal that is sent to the process when the terminal session ends.
The output of the command is redirected to a file called nohup.out by default, unless specified otherwise. The
& symbol puts the command in the background, allowing the user to run other commands in the same shell.
The other commands are incorrect for the following reasons:
* A, job -b dbmaint: This command is invalid and will not work. There is no job command in Linux, and the -b option is not a valid option for any command. The command that is used to list the background jobs in the current shell session is jobs, and it does not have a -b option either.
* B, dbmaint &>/dev/pts/null: This command will run dbmaint in the background, but it will not prevent it from being terminated when the user logs out of the system. The &> symbol redirects both the standard output and standard error of the command to a file or device, in this case /dev/pts/null.
However, this device does not exist, and the redirection will fail. Even if the device was /dev/null, which is a special device that discards any output sent to it, the command would still be susceptible to hangup signals and would not survive the logout.
* D, bg dbmaint: This command will not run dbmaint in the background, but it will try to resume a stopped background job with the name dbmaint. The bg command is used to move a stopped foreground process to the background and continue its execution. However, if there is no such process with the name dbmaint, the command will fail. Even if there was such a process, it would still be terminated when the user logs out of the system, unless it was disowned or prefixed with nohup.
* E, wait dbmaint: This command will not run dbmaint in the background, but it will wait for a background process with the name dbmaint to finish and return its exit status. The wait command is used to pause the execution of the current shell until one or more background processes complete.
However, if there is no such process with the name dbmaint, the command will fail. Even if there was such a process, it would still be terminated when the user logs out of the system, unless it was disowned or prefixed with nohup.
:
How to Run Linux Commands in Background | Linuxize
How to Run Linux Commands in Background | phoenixNAP KB
How to Run Linux Commands in the Background - MUO
How to Run Linux Commands in Background & Bring Them Back

Huclock