The correct answer is A. The certificate was not signed by a trusted authority, which was forcefully ignored during the tests. The key indicator in the output is the message: "SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway." This error means that the client system cannot validate the certificate chain because it does not recognize or trust the certificate authority (CA) that issued the server certificate.
In TLS/SSL validation, the client must verify that the server's certificate chains up to a trusted root CA present in the local trust store. If the issuer (in this case, ca1.comptia.org) is not included in the client's trusted certificate authorities, the verification fails. However, the phrase "continuing anyway" indicates that the validation failure was bypassed-likely due to a testing flag such as -k or --insecure in curl-allowing the connection despite the trust issue.
Option B is incorrect because the certificate validity dates show it is valid from 2024 to 2034, not expired.
Option C is incorrect because wildcard certificates (e.g., *.newapp.comptia.org) are commonly used and not inherently insecure when properly managed.
Option D is incorrect because the cipher suite shown (ECDHE-RSA-AES256-GCM-SHA384) is considered strong and modern, not outdated.
From a Linux+ security perspective, proper certificate validation is critical. Administrators should ensure that the issuing CA is trusted by installing the correct CA certificates rather than bypassing validation, which exposes systems to man-in-the-middle attacks and other security risks.

The correct answer is B. shred because it is specifically designed to securely delete data by overwriting files multiple times, making data recovery extremely difficult or practically impossible. In Linux environments, simply deleting a file or directory does not remove the actual data from the disk; instead, it only removes the file's reference from the filesystem. Until that space is overwritten, the data can potentially be recovered using forensic tools.
The shred command mitigates this risk by overwriting the contents of files with random data repeatedly before deletion. This aligns with security best practices outlined in Linux+ objectives, particularly in the domain of data protection and secure data disposal. When used with appropriate options (such as recursive handling through scripting or combining with other commands), shred can be applied to files within directories to ensure secure deletion.
Option A (dd) is incorrect because while dd can overwrite disks or partitions with zeros or random data, it is not specifically designed for secure deletion of directories and requires careful manual targeting. Misuse can lead to accidental data loss.
Option C (unlink) is incorrect because it simply removes a file name from the filesystem, similar to rm, without overwriting the data. Therefore, the data remains recoverable.
Option D (rm) is also incorrect because it removes files or directories at the filesystem level but does not securely erase the data. Even with options like -r or -f, it does not overwrite file contents.
From a Linux+ security standpoint, shred is the most appropriate utility among the given options for secure data destruction, helping ensure sensitive information cannot be recovered.

Container lifecycle management is a core topic within the Automation, Orchestration, and Scripting domain of CompTIA Linux+ V8. Administrators must understand the difference between creating containers, starting containers, and executing commands within running containers.
The correct command is docker run -it app-01-image. The docker run command performs three actions at once: it creates a new container from the specified image, starts the container, and optionally attaches the administrator's terminal to it. The -i option keeps standard input open, while the -t option allocates a pseudo- terminal (TTY). Together, these options allow the administrator to interactively connect to the container immediately after it is created.
The other options are incorrect for the following reasons. docker start is used only to start an existing stopped container and does not create a new container from an image. Additionally, -t and -d are not valid options for attaching an interactive terminal during container startup. docker build is used to build a Docker image from a Dockerfile and cannot be used to create or connect to a container. docker exec is used to run commands inside an already running container and therefore cannot be used to create a container.
Linux+ V8 documentation emphasizes that docker run is the primary command used when administrators want to instantiate containers from images and interact with them. This command is commonly used during testing, development, and troubleshooting workflows.

Environment variables in Linux can exist either locally within a shell or be exported to child processes.
CompTIA Linux+ V8 emphasizes the distinction between shell variables and environment variables, as this affects how applications inherit configuration values.
Option D, export ENABLE_AUTH=1, is the correct choice because it both assigns the variable and marks it for export to the environment. Once exported, the variable becomes available to all subsequently executed commands and child processes spawned from the current shell. This behavior is required when applications or scripts rely on environment variables for configuration.
Option B, ENABLE_AUTH=1, only sets a shell-local variable. While it is accessible within the current shell session, it is not inherited by child processes unless explicitly exported. Option A, let ENABLE_AUTH=1, performs arithmetic evaluation and does not export the variable. Option C incorrectly assigns the output of a command substitution and does not set the desired value.
Linux+ V8 documentation highlights export as the correct mechanism for making variables available system- wide within a user session. Therefore, the correct answer is D.

User and group management is a core System Management topic in CompTIA Linux+ V8. When adding a user to an additional group-such as the docker group-care must be taken not to alter the user's primary group.
The correct command is sudo usermod -aG docker user. The -G option specifies a supplementary group, and the -a (append) option ensures the user is added to the group without removing existing group memberships.
This is especially important because omitting -a would overwrite the user's supplementary groups.
Option B, usermod -g docker user, changes the user's primary group, which is not desired. Options A and D misuse groupmod, which is intended for modifying group properties, not user membership.
Linux+ V8 documentation explicitly warns that failing to use -a with -G can unintentionally remove a user from all other supplementary groups, potentially causing access issues.
Therefore, the correct and safe command is C. sudo usermod -aG docker user.