When accessing an intranet website, a certificate error is received. What can be done to move past the certificate error and ensure that the error is not received the next time the website is…

Question

Options

• Ainstall the website certificate into the web browser
• Bregister the web server with the web developer
• Cdisable TLS 2.0 in the advanced options of the web browser
• Dtrust the web developer for the application

• A
  73% (22)
• B
  7% (2)
• C
  3% (1)
• D
  17% (5)

Explanation

Installing the website's certificate into the browser's trusted certificate store (option A) resolves the error because the browser can now verify the site's identity against a known, trusted certificate - this is how internal/intranet sites self-signed or issued by a private CA get trusted without involving a public certificate authority. Option B is wrong because registering with a web developer has no technical effect on certificate trust chains. Option C is wrong because disabling TLS 2.0 is nonsensical (TLS 2.0 doesn't exist as a standard protocol, and disabling protocol versions doesn't resolve trust errors). Option D is wrong because "trusting the developer" is not a browser security mechanism - trust is established through certificates, not identity claims.

Memory tip: Think of it as adding the site to your browser's "trusted contacts list" - you install the certificate once, and the browser recognizes it every time after that.

No community discussion yet for this question.