A company has a public website and an internal admin panel on the same NGINX server. The admin panel is at /admin/ and should only be accessible from 203.0.113.0/24. The public site should be accessible to everyone. However, the current configuration has allow 203.0.113.0/24; deny all; in the server block, which is blocking the public site. What is the best fix?

Remove the deny all; from the server block and keep only allow 203.0.113.0/24;.

Move the allow and deny directives from the server block to the location /admin/ block.

Add allow all; after the deny all; in the server block.

Place the allow and deny directives in the http block instead.

After configuring IP restrictions, an administrator wants to confirm that a denied IP receives a 403 response and an allowed IP receives a 200 response. Which tool is most appropriate for this verification?

nginx -t to verify the configuration

ping from the allowed and denied IPs

curl from machines with the respective IPs

curl with the --resolve option to simulate requests from different IPs

A company runs multiple virtual hosts on a single NGINX server. They want to restrict access to the entire example.com site to only the partner network 198.51.100.0/24, while other sites on the same server remain unrestricted. Where should the allow and deny directives be placed?

Inside the server block for example.com

Inside the main configuration file outside any block

F5 Certified Administrator NGINX - Configuration:Demonstrate

Domain 2Objective 1

Demonstrate How to Restrict Access to NGINX Based on IP Address F5N3 Practice Questions (Page 1)

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

12questions here

3free pages

5concepts

Questions 1–5

1expert · hard
A company has a public website and an internal admin panel on the same NGINX server. The admin panel is at /admin/ and should only be accessible from 203.0.113.0/24. The public site should be accessible to everyone. However, the current configuration has allow 203.0.113.0/24; deny all; in the server block, which is blocking the public site. What is the best fix?
Select an answer first
2foundation · easy
After configuring IP-based access restrictions, which command should be used to test the configuration before applying it?
Select an answer first
3foundation · easy
Which HTTP status code would a client receive if NGINX denies its request due to an IP-based deny rule?
Select an answer first
4application · medium
After configuring IP restrictions, an administrator wants to confirm that a denied IP receives a 403 response and an allowed IP receives a 200 response. Which tool is most appropriate for this verification?
Select an answer first
5application · medium
A company runs multiple virtual hosts on a single NGINX server. They want to restrict access to the entire example.com site to only the partner network 198.51.100.0/24, while other sites on the same server remain unrestricted. Where should the allow and deny directives be placed?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N3

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

Demonstrate How to Restrict Access to NGINX Based on IP Address F5N3 Practice Questions (Page 1)

Questions 1–5

After configuring IP-based access restrictions, which command should be used to test the configuration before applying it?

Which HTTP status code would a client receive if NGINX denies its request due to an IP-based deny rule?

After configuring IP restrictions, an administrator wants to confirm that a denied IP receives a 403 response and an allowed IP receives a 200 response. Which tool is most appropriate for this verification?

A company runs multiple virtual hosts on a single NGINX server. They want to restrict access to the entire example.com site to only the partner network 198.51.100.0/24, while other sites on the same server remain unrestricted. Where should the allow and deny directives be placed?

Keep studying — Demonstrate how to restrict access