Question 1
Choose 1
The development team asks a Linux administrator to help diagnose a connectivity issue that is occurring with a newly developed software. The Linux administrator reviews the following output:
$ wget -vvv https://api.newapp.comptia.org/v2/health
Resolving proxy.comptia.org (proxy.comptia.org)... connected.
ERROR: The certificate of ' api.newapp.comptia.org ' is not trusted.
ERROR: The certificate of ' api.newapp.comptia.org ' does not have a known issuer.
Which of the following actions is the best way to resolve the issue?
$ wget -vvv https://api.newapp.comptia.org/v2/health
Resolving proxy.comptia.org (proxy.comptia.org)... connected.
ERROR: The certificate of ' api.newapp.comptia.org ' is not trusted.
ERROR: The certificate of ' api.newapp.comptia.org ' does not have a known issuer.
Which of the following actions is the best way to resolve the issue?
Correct answer:
A. Verify the remote certificate is trustworthy, and add it to the local trusted certificates repository.
Explanation:
The wget error messages indicate that the certificate presented by api.newapp.comptia.org is not trusted because its issuer is not recognized by the local system. The best solution is to verify that the remote certificate is valid (signed by a legitimate CA) and then add that CA certificate to the local trusted certificate store.
Correct Option:
A. Verify the remote certificate is trustworthy, and add it to the local trusted certificates repository.
The error "not trusted" and "does not have a known issuer" means the local system lacks the root or intermediate CA certificate that signed the remote server's certificate. After verifying the certificate's chain (confirming it is not malicious), the administrator should add the appropriate CA certificate to the system's trust store (e.g., /etc/pki/ca-trust/source/anchors/ on RHEL, or /usr/local/share/ca-certificates/ on Debian) and update the trust store. This resolves the error permanently without bypassing security.
Incorrect Options:
B. Replace the remote certificate with a new self-signed CA and application certificate –
Replacing the remote certificate would affect all users, not just this server. A self-signed certificate would still be untrusted by default unless its CA is added locally. This is not the best solution.
C. Replace the expired CA certificate to permanently resolve the problem –
The error does not mention certificate expiration; it mentions issuer trust. The certificate may not be expired at all. This assumes an expiration issue that is not indicated.
D. Add option --no-check-certificate to wget command to permanently resolve the problem –
Using --no-check-certificate disables certificate validation entirely, exposing the system to man‑in‑the‑middle attacks. It is a temporary workaround, not a permanent resolution, and does not fix the root cause.
Reference:
man wget – --no-check-certificate option (insecure, not recommended for permanent use)
Red Hat / Debian documentation – Adding custom CA certificates to system trust store
IETF RFC 5280 – Certificate path validation (trust anchors)
The wget error messages indicate that the certificate presented by api.newapp.comptia.org is not trusted because its issuer is not recognized by the local system. The best solution is to verify that the remote certificate is valid (signed by a legitimate CA) and then add that CA certificate to the local trusted certificate store.
Correct Option:
A. Verify the remote certificate is trustworthy, and add it to the local trusted certificates repository.
The error "not trusted" and "does not have a known issuer" means the local system lacks the root or intermediate CA certificate that signed the remote server's certificate. After verifying the certificate's chain (confirming it is not malicious), the administrator should add the appropriate CA certificate to the system's trust store (e.g., /etc/pki/ca-trust/source/anchors/ on RHEL, or /usr/local/share/ca-certificates/ on Debian) and update the trust store. This resolves the error permanently without bypassing security.
Incorrect Options:
B. Replace the remote certificate with a new self-signed CA and application certificate –
Replacing the remote certificate would affect all users, not just this server. A self-signed certificate would still be untrusted by default unless its CA is added locally. This is not the best solution.
C. Replace the expired CA certificate to permanently resolve the problem –
The error does not mention certificate expiration; it mentions issuer trust. The certificate may not be expired at all. This assumes an expiration issue that is not indicated.
D. Add option --no-check-certificate to wget command to permanently resolve the problem –
Using --no-check-certificate disables certificate validation entirely, exposing the system to man‑in‑the‑middle attacks. It is a temporary workaround, not a permanent resolution, and does not fix the root cause.
Reference:
man wget – --no-check-certificate option (insecure, not recommended for permanent use)
Red Hat / Debian documentation – Adding custom CA certificates to system trust store
IETF RFC 5280 – Certificate path validation (trust anchors)