nerdexam
CompTIA

XK0-005 · Question #851

Which of the following is a way to enable a production web server's communications with strong encryption and identity verification?

The correct answer is B. Creating a private key locally using openssl, creating a certificate request, sending the request to. To enable strong encryption and identity verification for a production web server, one must generate a private key, create a Certificate Signing Request (CSR), and have a trusted Certificate Authority (CA) sign it to issue an SSL/TLS certificate.

Security

Question

Which of the following is a way to enable a production web server's communications with strong encryption and identity verification?

Options

  • ACreating a key pair using ssh-keygen and using the generated key pair to secure the HTTPS
  • BCreating a private key locally using openssl, creating a certificate request, sending the request to
  • CCreating a 4096-bytes or longer self-signed certificate using openssl and using it to secure
  • DCreating a secret file using /dev/random as a source and using the generated file for HTTPS

How the community answered

(32 responses)
  • A
    6% (2)
  • B
    88% (28)
  • C
    3% (1)
  • D
    3% (1)

Why each option

To enable strong encryption and identity verification for a production web server, one must generate a private key, create a Certificate Signing Request (CSR), and have a trusted Certificate Authority (CA) sign it to issue an SSL/TLS certificate.

ACreating a key pair using ssh-keygen and using the generated key pair to secure the HTTPS

`ssh-keygen` is used to create SSH keys for secure shell access, not for generating SSL/TLS certificates to secure web server HTTPS.

BCreating a private key locally using openssl, creating a certificate request, sending the request toCorrect

This process accurately describes how to obtain a publicly trusted SSL/TLS certificate. A private key is generated and securely stored, then a CSR containing the public key and server identity is created. This CSR is submitted to a Certificate Authority (CA), which verifies the server's identity and issues a signed certificate, enabling secure HTTPS communication with identity verification.

CCreating a 4096-bytes or longer self-signed certificate using openssl and using it to secure

A self-signed certificate encrypts traffic but lacks validation from a trusted third-party CA, causing web browsers to display security warnings and making it unsuitable for public production environments requiring identity verification.

DCreating a secret file using /dev/random as a source and using the generated file for HTTPS

Generating a secret file from `/dev/random` is not the method for establishing strong encryption and identity verification for HTTPS; HTTPS relies on a public key infrastructure with certificates and private keys.

Concept tested: SSL/TLS certificate generation process

Source: https://www.openssl.org/docs/manmaster/man1/openssl-req.html

Topics

#SSL/TLS#PKI#Web Server Security#openssl

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full XK0-005 Practice