A company is setting up a new internal NGINX server for a development environment. They do not want to purchase a certificate from a public CA. They need to enable HTTPS for testing purposes, and all developers will access the server by IP address. What is the most appropriate certificate solution?

Generate a self-signed certificate and configure NGINX to use it, accepting that browsers will show a warning.

Disable HTTPS and use only HTTP for the development environment.

Use a certificate from a public CA that is valid for the IP address.

Use a certificate from a public CA that is valid for a domain name, and map the IP to that domain in the hosts file.

Why is it important to configure the `ssl_ciphers` directive in NGINX?

To set the path to the SSL certificate

To specify which TLS protocol versions are allowed

To control which cryptographic algorithms are used for encryption

In an NGINX server block, what does the `ssl` parameter on the `listen` directive do?

It redirects HTTP traffic to HTTPS

It sets the SSL certificate file path

It enables SSL/TLS on the specified port

It specifies the port number for HTTPS traffic

Which directives are required in an NGINX server block to enable HTTPS for a website?

ssl_certificate and ssl_certificate_key

An administrator manages an NGINX server that currently serves a public website over HTTP on port 80. The team has obtained a valid TLS certificate and key and wants all visitors to be forced onto HTTPS automatically. The HTTPS server block already exists and works correctly on port 443. What is the minimal configuration change to the existing HTTP server block to achieve this?

Add `rewrite ^ https://$host$request_uri permanent;` inside the `location /` block only.

Change the `listen` directive in the HTTP block to `listen 80 default_server;`.

Add `return 301 https://$host$request_uri;` inside the HTTP server block.

Add `listen 443 ssl;` and `ssl_certificate` directives to the HTTP server block.

F5 Certified Administrator NGINX - Configuration:Knowledge

Domain 3Objective 1

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

Part of the Configure NGINX as a web server domain, which makes up ~21% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~2–4 in this domain), expect 1–1 from this objective — we provide 20 practice questions to prepare you well beyond it. (estimate)

20questions here

4free pages

7concepts

Questions 11–15

11application · easy
A company is setting up a new internal NGINX server for a development environment. They do not want to purchase a certificate from a public CA. They need to enable HTTPS for testing purposes, and all developers will access the server by IP address. What is the most appropriate certificate solution?
Select an answer first
12foundation · easy
Why is it important to configure the `ssl_ciphers` directive in NGINX?
Select an answer first
13foundation · easy
In an NGINX server block, what does the `ssl` parameter on the `listen` directive do?
Select an answer first
14foundation · easy
Which directives are required in an NGINX server block to enable HTTPS for a website?
Select an answer first
15application · medium
An administrator manages an NGINX server that currently serves a public website over HTTP on port 80. The team has obtained a valid TLS certificate and key and wants all visitors to be forced onto HTTPS automatically. The HTTPS server block already exists and works correctly on port 443. What is the minimal configuration change to the existing HTTP server block to achieve this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N2

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5N2” is a trademark of its owner, used for identification only.