Demonstrate How to Securely Serve Content (HTTP/HTTPS) F5N2 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   An administrator is configuring a new NGINX server block for `api.example.com`. They have a certificate file `cert.pem` and a private key `key.pem`. The server must listen on port 443 and also redirect all HTTP traffic on port 80 to HTTPS. The administrator writes the following configuration: ``` server { listen 80; server_name api.example.com; return 301 https://$host$request_uri; } server { listen 443 ssl; server_name api.example.com; ssl_certificate /etc/nginx/ssl/cert.pem; ssl_certificate_key /etc/nginx/ssl/key.pem; } ``` After reloading NGINX, the administrator finds that HTTPS requests are not working, but HTTP requests are correctly redirecting. What is the most likely cause?

   • AThe `server_name` directive is missing from the HTTPS block, so NGINX cannot match the request.
   • BThe `return 301` directive in the HTTP block is causing a redirect loop.
   • CThe `listen 443 ssl;` directive is missing the `http2` parameter, which is required for HTTPS.
   • DThe `ssl_certificate` and `ssl_certificate_key` file paths are swapped.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   What is the primary difference between HTTP and HTTPS when serving web content?

   • AHTTPS encrypts the data exchanged between the client and server, while HTTP sends it in plaintext
   • BHTTPS is faster than HTTP because it compresses data
   • CHTTPS is only used for static content, while HTTP is used for dynamic content
   • DHTTPS uses a different port number than HTTP
   Reveal Solution Discussion Select an answer first
4. 3expert · hard

   An NGINX server must support a legacy payment terminal that only supports TLS 1.0 and the RC4 cipher. The rest of the organization requires TLS 1.2 or higher with strong ciphers. The administrator must configure NGINX to serve both the legacy terminal and modern clients from the same IP address. What is the most appropriate approach?

   • AConfigure SNI-based server blocks on the same port 443, one with TLS 1.0 and one with TLS 1.2+.
   • BEnable TLS 1.0 globally and include RC4 in the cipher list, accepting the security risk.
   • CUpgrade the payment terminal's firmware to support TLS 1.2.
   • DUse a separate server block on a different port (e.g., 8443) for the legacy terminal with TLS 1.0 and RC4, and keep the main server block on 443 with modern protocols.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What is the effect of the `index` directive in an NGINX server block serving static content?

   • AIt sets the base directory for all static files
   • BIt redirects requests to the HTTPS version of the site
   • CIt specifies the default file to serve when a directory is requested
   • DIt enables directory listing
   Reveal Solution Discussion Select an answer first
6. 5application · easy

   A small business is setting up a public-facing NGINX web server. They need to secure traffic but have a limited budget and do not need extended validation. They want to avoid browser warnings and are comfortable with an automated issuance process. Which type of TLS certificate is most appropriate for this scenario?

   • AA Domain Validation (DV) certificate from a public CA, such as one obtained via Let's Encrypt.
   • BAn Organization Validation (OV) certificate from a public CA.
   • CA self-signed certificate generated with OpenSSL.
   • DAn Extended Validation (EV) certificate from a public CA.
   Reveal Solution Discussion Select an answer first