Identify HTTP/SSH Access List to management-IP Address F5CAB4 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   What is the primary purpose of configuring an HTTP access list on the BIG-IP management interface?

   • ATo filter application traffic destined to virtual servers
   • BTo restrict which source IP addresses can access the management web UI
   • CTo encrypt all management traffic with SSL
   • DTo block all SSH access to the management interface
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A BIG-IP's management IP is 172.16.0.10. The HTTP access list is empty (no entries). An admin from 10.0.0.5 tries to access the web UI and succeeds. What does this indicate about the access list?

   • AThe access list is blocking all traffic except 10.0.0.5.
   • BAn empty HTTP access list allows all sources by default.
   • CThe management IP is on the same subnet as 10.0.0.5, so no filtering applies.
   • DThe SSH access list is also empty, so HTTP is allowed.
   Reveal Solution Discussion Select an answer first
4. 8expert · medium

   An admin configured an HTTP access list allowing 10.0.0.0/8 and an SSH access list allowing 172.16.0.0/12. From 10.1.1.1, HTTPS works but SSH fails. From 172.16.1.1, SSH works but HTTPS fails. What is the most likely explanation?

   • AThe access lists are correctly configured and enforced.
   • BThe SSH access list is blocking 10.1.1.1 from HTTPS.
   • CThe HTTP access list is blocking 172.16.1.1 from SSH.
   • DThe management IP is unreachable from 10.1.1.1.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is the purpose of testing connectivity from both allowed and denied source addresses when verifying an access list?

   • ATo check the throughput of the data plane
   • BTo measure the latency of the management interface
   • CTo confirm that the access list permits allowed sources and blocks denied sources
   • DTo verify the SSL certificate of the web UI
   Reveal Solution Discussion Select an answer first
6. 10expert · medium

   An admin needs to allow web UI access from 10.0.0.0/8 and SSH access from 172.16.0.0/12. After configuring both lists, an admin from 10.1.1.1 can access the web UI but cannot SSH. What is the most likely reason?

   • AThe SSH access list does not include 10.0.0.0/8, so SSH is denied.
   • BThe management IP is not reachable from 10.1.1.1.
   • CThe HTTP access list is also blocking SSH from 10.1.1.1.
   • DThe SSH service is disabled on the BIG-IP.
   Reveal Solution Discussion Select an answer first