Setting the setgid bit on a shared directory causes newly created files and subdirectories to inherit the directory's group ownership, allowing members of the same group to collaborate consistently on new files.

This issue falls under the Troubleshooting domain of the CompTIA Linux+ V8 objectives, specifically service startup failures and certificate-related errors. The provided output clearly indicates that the NGINX service fails during startup due to an inability to locate the private key file.
The critical error message is:
cannot load certificate key " /etc/pki/nginx/private/server.key " : No such file or directory This message confirms that NGINX is explicitly configured to look for the private key in the directory /etc/pki
/nginx/private/. However, the directory listing shows that the private directory exists but is empty, while the server.key file is located in /etc/pki/nginx/ instead. Because NGINX cannot find the private key at the configured path, the configuration test (nginx -t) fails, and systemd prevents the service from starting.
Option C correctly identifies the root cause: the private key is not in the correct location. Moving server.key into /etc/pki/nginx/private/ (or updating the NGINX configuration to match the current location) would resolve the issue. Linux+ V8 documentation stresses that service failures often result from misaligned configuration paths rather than corrupted files.
The other options are incorrect. Option A incorrectly refers to renaming a certificate file and does not address the path issue. Option B suggests a key mismatch, which would generate a different SSL error rather than a
"file not found" error. Option D is also incorrect because private keys should not have executable permissions like 0755; typically, they are restricted (for example, 0600) for security reasons.
Therefore, the web service is not responding because the private key file is not located in the directory expected by the NGINX configuration. The correct answer is C.

See the solution in Explanation below.
Explanation:
Archive Tab - Create the archive from Ann's home directory
Correct Command:
tar -cvf /tmp/ann.tar -C /home/ ann
Extract Tab - Extract the archive into Joe's home directory
Correct Command:
tar -xvf /tmp/ann.tar -C /home/ joe
This performance-based question tests file archiving and restoration using tar, a core System Management skill in the CompTIA Linux+ V8 objectives. The task requires preserving Ann's files and placing them correctly into Joe's home directory.
# Archive Phase Explanation
The goal of the first step is to archive Ann's entire home directory without embedding the full path (/home
/ann) inside the archive. This is accomplished using the -C option.
Command breakdown:
tar # archive utility
-c # create an archive
-v # verbose output (optional but allowed)
-f /tmp/ann.tar # specifies the archive file
-C /home/ # changes directory before archiving
ann # archives the ann directory only
This results in a clean archive containing Ann's files without absolute paths, which is best practice and explicitly covered in Linux+ V8 documentation.
# Extract Phase Explanation
The second step extracts the archived files into Joe's home directory.
Command breakdown:
-x # extract
-v # verbose
-f /tmp/ann.tar # specifies the archive
-C /home/joe # extracts files directly into Joe's home directory
This ensures Joe receives Ann's files correctly under /home/joe/ann or directly under /home/joe depending on post-extraction handling, which matches Linux+ expectations for administrative user transitions.

The docker ps command lists all running containers, allowing the administrator to verify whether the application's containers are active.

Creating a swap file with dd if=/dev/zero of=/swapfile bs=1024 count=65536 allocates additional swap space that MySQL can use when RAM is exhausted.
Formatting and enabling a swap partition with mkswap /dev/sda2; swapon -v /dev/sda2 brings another swap device online, further increasing the system's swap capacity.