What is a key architectural difference between NGINX and Apache?

NGINX is written in Java, while Apache is written in C.

NGINX uses an event-driven, asynchronous architecture, while Apache traditionally uses a process- or thread-based model.

NGINX uses a threaded model where each request is handled by a separate thread, while Apache uses an event-driven model.

NGINX can only serve static content, while Apache can serve both static and dynamic content.

An operations team runs a high-traffic static asset server (images, CSS, JS) and needs to maximize concurrent connections with minimal CPU overhead. They are comparing NGINX and Apache for this workload. Which architectural feature of NGINX makes it the better choice for this scenario?

Thread-based concurrency that allows parallel processing of a single request

Event-driven, asynchronous architecture that handles many connections per worker process

Process-per-connection model that isolates each request for maximum stability

Built-in PHP interpreter that eliminates the need for a separate application server

Which of the following is a key feature of NGINX as a web server?

Storing relational data in tables

Providing a graphical user interface for server management

Serving static content efficiently

Compiling source code into executable binaries

A startup is migrating from Apache to NGINX. Their current Apache setup uses .htaccess files for per-directory configuration and mod_rewrite for URL rewriting. The team wants to replicate this behavior in NGINX. What is the correct approach?

Use the mod_rewrite directives directly in the NGINX configuration file

Copy the .htaccess files to the same directories and NGINX will read them automatically

Install the Apache compatibility module for NGINX to enable .htaccess support

Move all per-directory rules into the NGINX server or location blocks and use the rewrite module

F5Certified Administrator NGINX

Domain 1Objective 1

Describe NGINX as a Web Server F5N1 Practice Questions (Page 3)

Part of the Given a scenario identify when to use NGINX domain, which makes up ~37% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~4–7 in this domain), expect 1–1 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

5concepts

Questions 11–15

11foundation · easy
What is a key architectural difference between NGINX and Apache?
Select an answer first
12foundation · easy
Which block in an NGINX configuration file is used to define settings that affect HTTP server traffic, such as virtual servers and location blocks?
Select an answer first
13application · medium
An operations team runs a high-traffic static asset server (images, CSS, JS) and needs to maximize concurrent connections with minimal CPU overhead. They are comparing NGINX and Apache for this workload. Which architectural feature of NGINX makes it the better choice for this scenario?
Select an answer first
14foundation · easy
Which of the following is a key feature of NGINX as a web server?
Select an answer first
15application · medium
A startup is migrating from Apache to NGINX. Their current Apache setup uses .htaccess files for per-directory configuration and mod_rewrite for URL rewriting. The team wants to replicate this behavior in NGINX. What is the correct approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N1

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