Interpret Port Lockdown Settings to Self-IP F5CAB4 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   A monitoring system reports that it can no longer reach the BIG-IP via SNMP. The port lockdown was recently changed from 'Allow Default' to 'Allow None'. What is the likely cause?

   • AThe SNMP community string is incorrect
   • BThe SNMP service has crashed on the BIG-IP
   • CThe monitoring system's IP address has changed
   • DThe 'Allow None' setting blocks all management services, including SNMP
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A BIG-IP Administrator is configuring a new Self-IP for a VLAN that will be used for management traffic. The administrator wants to ensure that only SSH and HTTPS are accessible on the Self-IP, while all other services are blocked. Which port lockdown setting should be applied?

   • AAllow All
   • BAllow None
   • CAllow Default
   • DAllow Custom
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   An administrator wants to allow SNMP monitoring from a specific management server to a Self-IP. Which custom port lockdown entry should be added?

   • ATCP port 161
   • BTCP port 162
   • CUDP port 161
   • DUDP port 162
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   A BIG-IP administrator needs to allow only SSH and HTTPS access to a Self-IP. Which port lockdown option should be selected?

   • AAllow All
   • BAllow Custom
   • CAllow Default
   • DAllow None
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   What is the security implication of setting port lockdown to 'Allow All' on a Self-IP?

   • AIt only allows traffic from the management network
   • BIt automatically enables encryption for all services
   • CIt permits all services, potentially exposing unnecessary management ports to the network
   • DIt blocks all management traffic, making the Self-IP unreachable
   Reveal Solution Discussion Select an answer first