What is a potential downside of disabling all ciphers that are not considered 'strong' (e.g., only allowing AES-GCM) on an NGINX server?

The server will automatically disable TLSv1.3

Increased CPU usage due to more complex encryption

Reduced compatibility with older clients that do not support those ciphers

Decreased security because weaker ciphers are more secure

When a client connects to an NGINX HTTPS server, which party's cipher preference is used by default during the TLS handshake?

The order defined by the operating system's OpenSSL configuration

The order defined in the ssl_protocols directive

What is the primary security benefit of disabling older TLS versions such as TLSv1.0 and TLSv1.1 on an NGINX server?

Improves performance by reducing handshake overhead

Ensures compatibility with all modern browsers

Reduces exposure to known vulnerabilities in those protocols

Increases the maximum allowed key length

F5 Certified Administrator NGINX - Configuration:Demonstrate

Domain 5Objective 3

Enable/Disable Ciphers and TLS Version F5N3 Practice Questions (Page 2)

Part of the Demonstrate how to enable HTTPS and associated security settings 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 13 practice questions to prepare you well beyond it. (estimate)

13questions here

3free pages

4concepts

Questions 6–10

6foundation · easy
Which directive, when set to 'on', makes NGINX use the server's cipher suite order instead of the client's?
Select an answer first
7foundation · easy
What is a potential downside of disabling all ciphers that are not considered 'strong' (e.g., only allowing AES-GCM) on an NGINX server?
Select an answer first
8foundation · easy
When a client connects to an NGINX HTTPS server, which party's cipher preference is used by default during the TLS handshake?
Select an answer first
9foundation · easy
Which NGINX directive is used to specify which TLS protocol versions are enabled for an HTTPS server?
Select an answer first
10foundation · easy
What is the primary security benefit of disabling older TLS versions such as TLSv1.0 and TLSv1.1 on an NGINX server?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N3

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. “F5N3” is a trademark of its owner, used for identification only.

Enable/Disable Ciphers and TLS Version F5N3 Practice Questions (Page 2)

Questions 6–10

Which directive, when set to 'on', makes NGINX use the server's cipher suite order instead of the client's?

What is a potential downside of disabling all ciphers that are not considered 'strong' (e.g., only allowing AES-GCM) on an NGINX server?

When a client connects to an NGINX HTTPS server, which party's cipher preference is used by default during the TLS handshake?

Which NGINX directive is used to specify which TLS protocol versions are enabled for an HTTPS server?

What is the primary security benefit of disabling older TLS versions such as TLSv1.0 and TLSv1.1 on an NGINX server?

Keep studying — Demonstrate how to enable HTTPS and associated security settings