After deploying a new regex location, you notice that requests are not being routed as expected. You want to verify which location block is actually handling a specific request. Which approach is most effective?

Use the error log to see which location was selected.

Add a unique header in each location block using add_header and use curl -I to inspect the response headers.

Review the access log to see the upstream server that responded.

Run nginx -t to check for configuration errors.

What is the effect of the '^~' modifier on a prefix location in NGINX?

It converts the prefix location into an exact match location.

If the prefix matches, NGINX skips regex location evaluation and uses this location.

It requires the prefix to be followed by a regex pattern.

It makes the prefix match case-insensitive.

Which statement accurately describes the purpose of named regex captures in an NGINX location block?

They allow a portion of the request URI to be stored in a named variable, which can then be referenced in proxy_pass or other directives.

They enable case-insensitive matching for the entire location block, so that regex patterns match regardless of letter case.

They define a variable that stores the entire request URI, which can be used to override the default location matching order.

They create a variable that holds the URI path after the location prefix, which is automatically passed to the upstream server.

In an NGINX configuration, what does a location block with a regular expression match against?

The full URL including the scheme, host, and query string as sent by the client.

The decoded request body content when the request method is POST or PUT.

The entire raw request line including the HTTP method, path, and protocol version.

The normalized request URI, which is the path portion of the request line after the host and before the query string.

In an NGINX regex location, what does the pattern '^/user/([a-z]+)/profile$' capture when matching the URI '/user/john/profile'?

The string 'profile' as the first capture group.

The string 'john' as the first capture group.

The string '/user/john/profile' as the first capture group.

The string 'user' as the first capture group.

F5 Certified Administrator NGINX - Configuration:Knowledge

Domain 2Objective 2

Describe How to Configure Path Regex Routing F5N2 Practice Questions (Page 1)

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

11questions here

3free pages

6concepts

Questions 1–5

1application · medium
After deploying a new regex location, you notice that requests are not being routed as expected. You want to verify which location block is actually handling a specific request. Which approach is most effective?
Select an answer first
2foundation · easy
What is the effect of the '^~' modifier on a prefix location in NGINX?
Select an answer first
3foundation · medium
Which statement accurately describes the purpose of named regex captures in an NGINX location block?
Select an answer first
4foundation · easy
In an NGINX configuration, what does a location block with a regular expression match against?
Select an answer first
5foundation · easy
In an NGINX regex location, what does the pattern '^/user/([a-z]+)/profile$' capture when matching the URI '/user/john/profile'?
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.