A client reports that a specific request returns a 404 Not Found, but the same URI works when tested from another network. You suspect that NGINX is serving a cached 404 response. Which log or debugging technique would best confirm this?

Run 'nginx -t' to test the configuration for cache-related errors

Check the access log for the 'X-Proxy-Cache' header value

Enable the debug log for the error_log directive

Use tcpdump to capture traffic between NGINX and the upstream

F5Certified Administrator NGINX - Troubleshooting

Domain 2Objective 4

Describe How to Troubleshoot Various Response F5N4 Practice Questions (Page 5)

Part of the Troubleshoot basic use cases domain, which makes up ~60% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~6–12 in this domain), expect 1–2 from this objective — we provide 22 practice questions to prepare you well beyond it. (estimate)

22questions here

5free pages

6concepts

Questions 21–22

21foundation · easy
A client receives a 504 Gateway Timeout error. Which NGINX directive is most likely responsible for this error if it is set too low?
Select an answer first
22application · medium
A client reports that a specific request returns a 404 Not Found, but the same URI works when tested from another network. You suspect that NGINX is serving a cached 404 response. Which log or debugging technique would best confirm this?
Select an answer first

Finished these 2 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to F5N4

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

Describe How to Troubleshoot Various Response F5N4 Practice Questions (Page 5)

Questions 21–22

A client receives a 504 Gateway Timeout error. Which NGINX directive is most likely responsible for this error if it is set too low?

A client reports that a specific request returns a 404 Not Found, but the same URI works when tested from another network. You suspect that NGINX is serving a cached 404 response. Which log or debugging technique would best confirm this?

Keep studying — Troubleshoot basic use cases