A user receives the following error message while browsing the Internet on a PC: The connection is . Upon inspection, a technician discovers the issue only occurs on the user's banking not private…

Question

Options

• AIgnore the error and accept the certificate.
• BReport the certificate error to the bank.
• CDownload an updated certificate.
• DStop and restart the certificate services.
• EReimage the desktop, as it contains malware.

• A
  4% (3)
• B
  3% (2)
• C
  9% (6)
• D
  67% (45)
• E
  16% (11)

Explanation

The certificate appears valid in the viewer but is triggering an error, and the issue is reproducible on a second PC-pointing to a service-level problem rather than a local browser or machine issue. Stopping and restarting certificate services (D) forces the local certificate validation service to flush cached state and re-evaluate the certificate chain, which can resolve inconsistencies between what the viewer displays and what the OS trust store reports. Accepting the error (A) is never safe on a banking site. Reporting to the bank (B) is the escalation path if the service restart fails. End users cannot download and replace server-side TLS certificates (C). Reimaging for malware (E) is not justified by the available evidence.

No community discussion yet for this question.