Examers.io
ExamsOrganizationsHow it worksPricingHelp & FAQ
F5 logo

F5Certified Administrator NGINX - Troubleshooting

Domain 2Objective 6

Describe How to Troubleshoot Location Precedence and Add_header Inheritance F5N4 Practice Questions (Page 1)

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 11 practice questions to prepare you well beyond it. (estimate)

11questions here
3free pages
4concepts

Questions 1–5

  1. 1application · medium

    An NGINX server is configured with add_header Cache-Control "no-store" at the server level. A location block for /api/ has add_header X-Request-ID "$request_id". A developer notices that responses from /api/ do not include the Cache-Control header. What is the most likely cause?

    Select an answer first
  2. 2foundation · easy

    Which location block will NGINX select for a request to /download/app.zip when the configuration contains the following blocks?

    Select an answer first
  3. 3application · medium

    An NGINX configuration has add_header X-Content-Type-Options "nosniff" at the http level. A server block for example.com has add_header X-Frame-Options "DENY". A location block for /static/ has no add_header directives. What headers are sent in responses for /static/logo.png?

    Select an answer first
  4. 4foundation · easy

    In NGINX, how are add_header directives inherited from a parent context to a child context?

    Select an answer first
  5. 5foundation · easy

    A request to /files/report.pdf unexpectedly matches a regex location instead of the intended prefix location. Which configuration mistake is the most likely cause?

    Select an answer first
Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

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.