An admin has a location /old/ block with proxy_pass http://backend/new/;. A request for /old/page.html is received. The backend expects the path /new/page.html. However, the admin notices the backend receives /new/page.html. What is the correct explanation for this behavior?

NGINX stripped the /old/ prefix and prepended /new/, which is the same as replacing.

NGINX appended /new/ to the original URI, resulting in /old/new/page.html.

NGINX replaced the /old/ prefix with /new/ because proxy_pass includes a URI.

NGINX forwarded the URI unchanged because proxy_pass with a URI does not modify the path.

In NGINX configuration, what is the primary purpose of a location block?

To set the maximum number of simultaneous connections NGINX can handle

To match a portion of the request URI and apply specific configuration directives to that request

To define the IP address and port on which NGINX listens for incoming connections

To specify which backend server should receive all requests by default

In a location block, what does the proxy_pass directive typically specify?

The IP address of the client that is allowed to access the backend

The name of the log file where proxy requests are recorded

The file path where NGINX stores cached responses from the backend

The URL of the backend server or upstream group to forward requests to

In a location block, what happens to the request URI when proxy_pass is specified without a URI (e.g., proxy_pass http://backend;)?

The request URI is replaced with the root path '/'

The full original request URI is passed to the backend unchanged

The request is sent to the backend with an empty URI

The location prefix is removed from the request URI

What is the first step NGINX performs when it receives a request from a client?

Select a server block based on the request's Host header

Forward the request to the upstream server

Check the client's IP address against access rules

Select a location block based on the request URI

F5 Certified Administrator NGINX - Configuration:Knowledge

Domain 4Objective 1

Explain How Traffic Routing Is Handled in NGINX as a Reverse Proxy F5N2 Practice Questions (Page 3)

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

17questions here

4free pages

6concepts

Questions 11–15

11expert · easy
An admin has a location /old/ block with proxy_pass http://backend/new/;. A request for /old/page.html is received. The backend expects the path /new/page.html. However, the admin notices the backend receives /new/page.html. What is the correct explanation for this behavior?
Select an answer first
12foundation · easy
In NGINX configuration, what is the primary purpose of a location block?
Select an answer first
13foundation · easy
In a location block, what does the proxy_pass directive typically specify?
Select an answer first
14foundation · easy
In a location block, what happens to the request URI when proxy_pass is specified without a URI (e.g., proxy_pass http://backend;)?
Select an answer first
15foundation · easy
What is the first step NGINX performs when it receives a request from a client?
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.