All Obstacles During F5CAB1 Exam Preparation with F5CAB1 Real Test Questions
Fully Updated Free Actual F5 F5CAB1 Exam Questions
F5 F5CAB1 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 27
Which command will display thecurrent active volumeon a BIG-IP system?
- A. tmsh list sys software update
- B. tmsh show sys version
- C. tmsh show sys software status
Answer: C
Explanation:
To identify which boot volume is currently active on a BIG-IP system, the correct command is:
tmsh show sys software status
This command displays:
* All installed boot volumes (HD1.1, HD1.2, HD1.3, etc.)
* The BIG-IP software version installed on each volume
* TheActivefield, indicating which volume the system is currently booted from
* The installation status ("complete", "in-progress", "allowed")
This is thestandard and authoritativeway to determine the active boot location.
Why the other options are incorrect:
A). tmsh show sys version
* Displays OS version, build, and date.
* Doesnotshow boot locations or which volume is active.
C). tmsh list sys software update
* Shows software update configurations, not boot volume status.
* Does not display which volume is active.
NEW QUESTION # 28
A BIG-IP Administrator discovers malicious brute-force attempts to access the BIG-IP device on the management interfacevia SSH.
The administrator needs to restrict SSH access to the management interface.
Where should this be accomplished?
- A. System > Platform
- B. Network > Interfaces
- C. Network > Self IPs
- D. System > Configuration
Answer: D
Explanation:
The BIG-IPmanagement interface (MGMT port)is controlled throughSystem settings, not through the Network menu.
SSH access on the management interface is configured here:
System # Configuration # Device # General # SSH Access / SSH IP Allow
This section allows the administrator to:
* Enable or disable SSH service
* Restrict SSH access to specific IP addresses or subnets
* Apply security policies to the management interface
Why the other options are incorrect:
A). Network > Interfaces
* Used for data-plane physical interface settings, not management plane SSH restrictions.
B). Network > Self IPs
* Controls in-band management or data-plane access, not the dedicated management port.
D). System > Platform
* Used for hostname, time zone, LCD contrast, hardware settings - not SSH security on the management port.
Therefore, restricting SSH access to themanagement interfacemust be done under:
#System # Configuration # Device # General
Which corresponds toOption C.
NEW QUESTION # 29
Which two items demonstrate thecreation of a new volumefor software images?
(Choose two.)
- A. tmsh install software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume
- B. tmsh install sys software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume
- C. tmsh install /sys software image BIGIP-<version>.iso volume HD1.5 create-volume
- D. Using the GUI, go toSystem > Disk Management, selectNew Volume. In the pop-up window, type the name or number of the new volume and clickApply.
- E. Using the GUI, go toSystem > Software Management > Available Images > Install, and in the Install Software Image pop-up window, type the new volume name or number and clickInstall.
Answer: A,D
Explanation:
In BIG-IP, software images are installed onboot volumes(for example, HD1.1, HD1.2, HD1.3, etc.).
To install software on anew volume, the administrator must instruct the system to create a new boot location before installation.
There are two correct ways to create a new volume:
A). tmsh command (with correct syntax)
tmsh install software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume This syntax correctly includes:
* install software image
* full path to ISO (/shared/images/...)
* volume name (HD1.5)
* create-volumekeyword
This instructs BIG-IP to create the new boot volume as part of the installation.
C). Using the GUI # System > Disk Management
From the Disk Management menu, the administrator can:
* Select "New Volume"
* Enter the volume identifier (e.g., HD1.5)
* Apply changes
This GUI method is officially supported and explicitly creates a new boot volume before installing the software.
Why the other options are incorrect:
B). Incorrect tmsh syntax
* Missing /shared/images/ path
* Incorrect command structure
D). Incorrect command structure
* Missing required keywords and correct command hierarchy
E). Software Management # Install does NOT create volumes
* This installs to anexistingvolume only
* The GUI install dialog does not create new boot volumes
Thus, onlyOption AandOption Cproperly create a new software volume.
NEW QUESTION # 30
The Configuration Utility of a BIG-IP device is currently accessible via its management IP10.53.1.245from all VLANs.
The BIG-IP Administrator needs to restrict access so only hosts from the10.0.0.0/24subnet can access the Configuration Utility.
Which TMSH command accomplishes this?
- A. (tmos)# create /net acl MGMT.HTTP rule add { (permit tcp 10.0.0.0/24 10.53.1.245 http) (deny ip any any http) }
- B. (tmos)# create /net acl MGMT.HTTP rule add { (permit tcp 10.0.0.0 0.0.0.255 host 10.53.1.245 http) }
- C. (tmos)# modify /ltm httpd allow replace-all-with {10.0.0.0/24}
- D. (tmos)# modify /sys httpd allow replace-all-with {10.0.0.0/24}
Answer: D
Explanation:
BIG-IP controls access to the web-based Configuration Utility (TMUI) through the/sys httpd allowlist. This parameter specifies which client IPs or subnets may initiate HTTP/HTTPS connections to the management interface.
To restrict TMUI access toonlythe 10.0.0.0/24 subnet:
* The correct method is tomodify the HTTPD allow listso that it contains only this subnet.
* This requires replacing the entire current list with the new subnet using:
modify /sys httpd allow replace-all-with {10.0.0.0/24}
This ensures thatonlyclients within 10.0.0.0/24 can reach the Configuration Utility.
Why the other options are incorrect:
* Options A and Ccreate network ACL objects under /net acl, which apply to data-plane traffic, not management-plane TMUI access. TMUI access is not controlled by LTM ACLs but by the HTTPD allow directive.
* Option Bis incorrect syntax and references /ltm httpd, which is not the proper object; the correct hierarchy is /sys httpd.
Thus, only modifying the/sys httpd allowlist achieves the required restriction.
NEW QUESTION # 31
Which of the following areresource allocation (provisioning) settingsfor BIG-IP modules?
(Choose two.)
- A. Nominal
- B. Limited
- C. Dedicated
- D. Maximum
Answer: A,C
Explanation:
BIG-IP module provisioning determines howCPU, memory, and disk resourcesare allocated to each licensed module. F5 defines a specific set of supported provisioning levels.
Valid provisioning (resource allocation) settings
Nominal
* Allocates a standard, balanced amount of system resources to a module.
* Intended for typical production deployments where multiple modules may be provisioned at the same time.
Dedicated
* Allocatesall available system resourcesto a single module.
* Used when the BIG-IP device is dedicated to running only one module (for example, ASM-only or APM-only deployments).
* No other modules can be provisioned when one is set to Dedicated.
These two options are valid and supported provisioning levels.
Why the other options are incorrect
Maximum
* This is not a valid BIG-IP provisioning level.
* BIG-IP does not use "Maximum" as a resource allocation setting.
Limited
* This is also not a supported provisioning level.
* BIG-IP uses levels such as None, Minimal, Nominal, and Dedicated (module-dependent), not Limited.
NEW QUESTION # 32
An administrator is in the process of reactivating the license using the interface displayed in the exhibit.
What is the address of the license server to which the BIG-IP device must be able to establish an outbound connection in order to use theAutomatic Activation Method?
- A. callhome.f5.com
- B. ask.f5.com
- C. activate.f5.com
- D. license.f5.com
Answer: C
Explanation:
When you chooseAutomaticas the activation method in the License , Re-activate screen, the BIG-IP device itself contacts F5'slicense activation serviceover the Internet.
For successful automatic activation:
* The BIG-IP must have outbound network connectivity (typically via the management interface).
* DNS resolution and routing must allow it to reach theF5 license activation host(the one shown in option D).
* The device sends its dossier and registration key to that service and receives an updated license file in return, which is then installed automatically.
The other hostnames in the options are not used by BIG-IP for license activation, so they cannot be correct in the context ofAutomatic Activation.
NEW QUESTION # 33
A new logging solution is being implemented on the network. Policy requires keeping management traffic sent from the BIG-IPout of the management interface. After configuring the BIG-IP to forward messages to the new Syslog server, the BIG-IP Administrator notices that packets are being sentfrom a numbered data- plane Self IP.
What should the BIG-IP Administrator change to send the traffic out of thecorrect interface?
- A. Create a Management Route for the specific address/subnet of the syslog service via TMSH.
- B. Create a new Self IP in the same subnet as the management IP address using a route domain.
- C. Modify the port lockdown settings on the Self IP address to allow UDP port 514 traffic.
- D. Set the Management IP as the source address when configuring a Remote Syslog destination.
Answer: A
Explanation:
By default,management-plane trafficuses themanagement routing table, whiledata-plane trafficuses the TMM routing table.
Remote Syslog traffic ismanagement-planetrafficunlessa management route exists.
If noManagement Routematches the Syslog server's destination IP, the BIG-IP will instead:
* UseTMM routes, and
* Source the packets from aSelf IP
This is exactly what the administrator is observing.
To force Syslog traffic out the management port:
You must create aManagement Route, which is configured using:
tmsh create /sys management-route <name> gateway <ip> network <syslog subnet> This sends syslog traffic:
* Out of themanagement interface
* Using theManagement IPas the source
Thus,Option Bis correct.
Why the other options are incorrect:
A). Set the Management IP as the source address
* Source address selection is overridden by routing.
* Without a management route, traffic still goes out the data plane.
C). Create a new Self IP using a route domain
* Unnecessary and not related to management-plane routing.
* Syslog traffic should not rely on data-plane Self IPs.
D). Modify port lockdown on Self IP to allow UDP/514
* This would allow Syslog trafficintothe BIG-IP over a Self IP, not forceoutboundtraffic via management.
NEW QUESTION # 34
An administrator is in the process of reactivating the license using the interface displayed in the exhibit.
What is the address of the license server to which the BIG-IP device must be able to establish an outbound connection in order to use theAutomatic Activation Method?
- A. callhome.f5.com
- B. ask.f5.com
- C. activate.f5.com
- D. license.f5.com
Answer: C
Explanation:
When you chooseAutomaticas the activation method in the License Re-activate screen, the BIG-IP device itself contacts F5'slicense activation serviceover the Internet.
For successful automatic activation:
* The BIG-IP must have outbound network connectivity (typically via the management interface).
* DNS resolution and routing must allow it to reach theF5 license activation host(the one shown in option D).
* The device sends its dossier and registration key to that service and receives an updated license file in return, which is then installed automatically.
The other hostnames in the options are not used by BIG-IP for license activation, so they cannot be correct in the context ofAutomatic Activation.
NEW QUESTION # 35
A BIG-IP Administrator needs to install aHotFixon a standalone BIG-IP device.
The device currently hasHD1.1as the Active Boot Location.
The administrator has already reactivated the license and created a UCS archive.
In which sequence should the administrator perform theremaining steps?
- A. Install HotFix in HD1.2, Install base Image in HD1.2, Activate HD1.2
- B. Install base Image in HD1.2, Install HotFix in HD1.2, Activate HD1.2
- C. Install HotFix in HD1.1, Reboot the BIG-IP device, Install UCS Archive
- D. Activate HD1.2, Install base Image in HD1.2, Install HotFix in HD1.2
Answer: B
Explanation:
When installing a software upgrade with a HotFix on BIG-IP, the correct workflow requires:
* Install the base TMOS imageon an unused boot volume
* Install the corresponding HotFixonto that same boot volume
* Activate the updated boot volumeto boot into the new software
This method ensures:
* The existing active system (HD1.1) is untouched
* The upgrade occurs in a new, clean volume (HD1.2)
* The HotFix applies properly to the same base image
* The administrator can revert to HD1.1 if issues occur
OptionCmatches the correct F5 upgrade sequence:
1. Install base image on HD1.2
2. Install HotFix on HD1.2
3. Activate HD1.2
Why the other options are incorrect:
A). Install HotFix before base image
* HotFixes must be appliedafterthe base image; not valid.
B). Installing a HotFix on the active boot location (HD1.1)
* Not recommended and does not use a clean new volume.
* Also does not involve installing the base image.
D). Activating HD1.2 before installing anything
* Cannot activate an empty or invalid boot volume.
Thus,Option Cis the correct sequence.
NEW QUESTION # 36
Refer to the exhibit.
What traffic will be permitted to reach the BIG-IP?
- A. FTP
- B. Telnet
- C. SSH
Answer: C
Explanation:
The exhibit shows the configuration of aSelf IPwith:
* Port Lockdown: Allow Custom
* ACustom Listthat includes the following TCP ports:
* 443
* 22
Meaning of these ports:
* TCP 443# HTTPS (TMUI - web-based management)
* TCP 22# SSH (command-line remote access)
No other TCP, UDP, or protocol entries are listed; therefore, only these two services are allowed to reach the BIG-IP via this Self IP.
Evaluating the answer choices:
Option
Service
Port
Allowed?
FTP
TCP 21
Not listed
#Not allowed
SSH
TCP 22
Listed
#Allowed
Telnet
TCP 23
Not listed
#Not allowed
Thus,SSHis the only traffic permitted through this Self IP configuration.
NEW QUESTION # 37
When logged into thebash shellof a BIG-IP system, which of the following commands will display the management-ip address?
(Choose two.)
- A. show mgmt ip
- B. list / sys management-ip
- C. tmsh list /sys management-ip
- D. ifconfig mgmt
Answer: C,D
Explanation:
When logged into thebash shellof a BIG-IP system, there are two valid ways to view themanagement-ip address:
A). tmsh list /sys management-ip
* Even from the bash shell, the administrator can enter a tmsh command by typing:
* tmsh list /sys management-ip
* This displays:
* Management IP address
* Netmask
* Any configured management routes
* This is theofficial tmsh methodfor viewing the management-ip configuration.
C). ifconfig mgmt
* In the underlying Linux OS, the management interface maps to themgmtinterface.
* Running:
* ifconfig mgmt
displays:
* Assigned management IP
* Netmask
* Link-level status
* This is a valid Linux-level method used frequently for troubleshooting.
Why the other options are incorrect:
B). show mgmt ip
* Not a valid bash or tmsh command on BIG-IP.
D). list / sys management-ip
* Missing thetmshprefix.
* In bash, this will generate a syntax error.
* The correct form requires:
tmsh list /sys management-ip
NEW QUESTION # 38
A BIG-IP Administrator upgrades the BIG-IP LTM to a newer software version. After the administrator reboots into the new volume, the configuration fails to load.
Why is the configuration failing to load?
- A. The upgrade was performed on the standby unit.
- B. The license needed to be reactivated before the upgrade.
- C. A minimum of at least two reboots is required.
- D. Connectivity to the DNS server failed to be established.
Answer: B
Explanation:
When upgrading to a newer TMOS software version, BIG-IP validates whether the current license is permitted to run that version.
This is controlled by theService Check Datein the device's license file.
If the Service Check Date is older than the minimum required for the target version:
* The systemboots into the new volume,
* Butfails to load the configuration,
* And will instead present messages indicating that the configuration cannot be applied due to aninvalid or outdated license.
This is a well-known behavior:
An outdated license, not reactivated before upgrade, causes configuration load failure after reboot into the new software.
Why the other options are incorrect:
A). Performed on the standby unit
* Upgrading a standby unit does not cause configuration load failure.
* Standby-only upgrades are standard best practice.
C). Two reboots required
* BIG-IP does not require two reboots during an upgrade.
* One reboot into the new volume is sufficient.
D). DNS connectivity failure
* DNS connectivity does not affect configuration loading.
* DNS is only needed for automatic license activation, not for applying config at boot.
Thus, the configuration failed to load because thelicense was not reactivated before the upgrade, making Option Bcorrect.
NEW QUESTION # 39
The BIG-IP Administrator needs to update access to the Configuration Utility to include the172.28.31.0/24and
172.28.65.0/24networks.
From the TMOS Shell (tmsh), which command should the BIG-IP Administrator use to complete this task?
- A. modify /sys httpd permit add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
- B. modify /sys httpd allow add { 172.28.31.0 172.28.65.0 }
- C. modify /sys httpd allow add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
Answer: C
Explanation:
Access to the BIG-IP Configuration Utility (TMUI) is controlled through the/sys httpd allowlist.
This list defines which IP addresses or subnets are allowed to connect to the management web interface.
To allow two new subnets-172.28.31.0/24and172.28.65.0/24-the administrator mustaddboth subnets to the existing list without removing current entries.
In tmsh, subnet entries must be specified innetwork/netmask format, for example:
172.28.31.0/255.255.255.0
The correct tmsh command to append these networks is:
modify /sys httpd allow add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 } Why the other options are incorrect:
Option B:
* IPs are listed without masks, which is invalid for subnet-based access control.
* The system requiresnetwork/netmaskformat.
Option C:
* The command uses permit instead of allow, which is not a valid attribute of /sys httpd.
* The correct keyword must beallow.
Thus, onlyOption Acorrectly adds both permitted subnets in the proper tmsh format.
NEW QUESTION # 40
The monitoring team reports that the SNMP server is unable to poll data from a BIG-IP device.
What information will help the BIG-IP Administrator determine whether the issue originates from the BIG-IP system?
- A. The "Traffic Group" setting must use a floating Traffic Group.
- B. The "Port Lockdown" setting is preventing the SNMP server from polling data from the BIG-IP.
- C. The configuration on the exhibit is correct and other options should be explored.
- D. The "VLAN / Tunnel" setting must allow All Vlans.
Answer: B
Explanation:
The exhibit shows aSelf IPwith:
* VLAN:Data
* Port Lockdown:Allow None
Impact of "Allow None" on SNMP
When a Self IP is configured with:
Port Lockdown: Allow None
the BIG-IP blocksallservices and ports except a few hardcoded HA communication ports.
This means:
* UDP/161 (SNMP)is blocked
* UDP/162 (SNMP traps)is blocked
* The SNMP server cannot poll or receive data from the BIG-IP through this Self IP SNMP relies on access through the Self IP if out-of-band (mgmt interface) is not used.
Thus, the issue is directly caused byPort Lockdown = Allow None, which prevents SNMP communication.
Why the other options are incorrect:
B). Traffic Group must use a floating Traffic Group
* SNMP polling doesnotrequire floating Self IPs.
* Floating groups apply to HA failover IPs, not SNMP functionality.
C). VLAN/Tunnel must allow All VLANs
* Self IPs are always bound to a VLAN; SNMP doesnotrequire All VLANs.
* As long as the Self IP belongs to a reachable VLAN, SNMP can work.
D). Configuration is correct
* It is not correct:Allow Noneblocks SNMP and is the problem.
NEW QUESTION # 41
Which one of the following is aport and protocol combination allowedby theAllow Defaultsetting for Port Lockdown?
- A. TCP 80
- B. TCP 443
- C. UDP 8443
Answer: B
Explanation:
Port Lockdown controls which ports and protocols aSelf IPwill respond to.
TheAllow Defaultsetting permits only a predefined set of BIG-IP internal and required service ports.
The Allow Default listincludes:
* TCP 443# HTTPS (Management/TMUI access via Self-IP)
* TCP 4353 # CMI (device sync)
* TCP/UDP ports related to HA communication
* Other essential internal F5 ports
Why TCP 443 is correct:
* It is one of the officially allowed ports underAllow Default.
* It enables HTTPS/TMUI access through a Self IP.
Why the other options are incorrect:
A). TCP 80 (HTTP)
* Not allowed under Allow Default
* HTTP via Self-IP is blocked unless placed under Allow Custom
B). UDP 8443
* Not an F5 default service
* Not part of the Allow Default ports
NEW QUESTION # 42
The BIG-IP Administrator uses Secure Copy Protocol (SCP) to upload a TMOS image to the/shared/images/ directory in preparation for a TMOS upgrade.
After the upload is completed, what will the system dobeforethe image is shown in the GUI under:
System » Software Management » Image List?
- A. The system copies the image to /var/local/images/
- B. The system performs a reboot into a new partition
- C. The system verifies the internal checksum
Answer: C
Explanation:
When a TMOS image (.iso file) is uploaded into the/shared/images/directory, the BIG-IP performs an internal validation step before the ISO appears in the GUI.
1. The system verifies the internal checksum
* BIG-IP automatically reads the embedded checksum inside the ISO file
* Verifies integrity of the uploaded image
* Confirms the file is not corrupted or incomplete
* Ensures the image is a valid F5 TMOS software image
Only after this checksum verification succeeds does the image appear under:
System # Software Management # Image List
Why the other options are incorrect:
A). The system performs a reboot into a new partition
* Uploading an ISO file never triggers a reboot.
C). The system copies the image to /var/local/images/
* All valid TMOS images remain in/shared/images/.
* No copying occurs.
NEW QUESTION # 43
A secondary administrator has been granted access to a BIG-IP device through itsManagement Interface, but is unable to access theConfiguration Utility (WebUI).
What command can be run from the CLI to capture the network traffic on themanagement interfaceand troubleshoot the issue?
(Choose two.)
- A. tcpdump -i 0.0 -n port 443
- B. tcpdump -i eth0 -n port 443
- C. tcpdump -i mgmt -n port 443
- D. tcpdump -i management -n port 443
- E. tcpdump -i tun0 -n port 443
Answer: B,C
Explanation:
The BIG-IP has two distinct planes:
* Management-plane# handled entirely by the management interface (MGMT)
* Data-plane (TMM)# handles Self IPs, VLAN interfaces, and traffic processing To capture traffic on the management interface, only the management-side NICs may be used:
* mgmt# Logical name for the management interface
* eth0# Physical Linux interface mapped to the management port on most BIG-IP platforms Both of these correctly capture inbound/outbound WebUI (HTTPS/443) traffic on the management port.
Why the correct answers are A and B
A). tcpdump -i eth0 -n port 443
* On BIG-IP appliances and VMs, the management port maps toeth0at the Linux OS level.
* Capturing on eth0 correctly shows HTTPS traffic to the WebUI.
B). tcpdump -i mgmt -n port 443
* mgmtis the BIG-IP alias for the management interface.
* This is thepreferredand most explicit capture interface for management-plane packet captures.
Why the other options are incorrect:
C). tcpdump -i 0.0
* Interface0.0is the TMM switch interface used for data-plane packet captures.
* Itdoes NOTcapture management-plane traffic.
D). tcpdump -i tun0
* Used for tunnel interfaces (IPsec, VXLAN, etc.)
* Not related to management access.
E). tcpdump -i management
* There isnointerface named management on BIG-IP.
* The correct names are mgmt or eth0.
NEW QUESTION # 44
What command will allow the BIG-IP Administrator to view theconfigured management IPof a BIG-IP system?
(Choose one.)
- A. tmsh show sys management-ip
- B. tmsh list sys management-ip
- C. tmsh list sys management-route
- D. tmsh list net self
Answer: B
Explanation:
Comprehensive and Detailed Explanation (Paraphrased)
The BIG-IP stores the configured management IP address as asystem configuration objectunder the/sys hierarchy.
To display configured (persistent) values, BIG-IP uses thetmsh list command, not show.
Why tmsh list sys management-ip is correct
* The management IP configuration is defined under:
* /sys management-ip
* Running:
* tmsh list sys management-ip
displays:
* The configured management IP address
* Netmask
* Associated attributes
This command shows theactual configured management IP, which is what the question asks for.
Why the other options are incorrect
A). tmsh show sys management-ip
* The show command is used for runtime statistics and status.
* management-ip is a configuration object, not a statistics object.
C). tmsh list sys management-route
* Displays management routing information, not the management IP address itself.
D). tmsh list net self
* Displays Self IPs used on the data plane.
* Does not show the management interface IP.
NEW QUESTION # 45
The monitoring team reports that the SNMP server is unable to poll data from a BIG-IP device.
What information will help the BIG-IP Administrator determine whether the issue originates from the BIG-IP system?
- A. The "Traffic Group" setting must use a floating Traffic Group.
- B. The "Port Lockdown" setting is preventing the SNMP server from polling data from the BIG-IP.
- C. The configuration on the exhibit is correct and other options should be explored.
- D. The "VLAN / Tunnel" setting must allow All Vlans.
Answer: B
Explanation:
The exhibit shows aSelf IPwith:
* VLAN:Data
* Port Lockdown:Allow None
Impact of "Allow None" on SNMP
When a Self IP is configured with:
Port Lockdown: Allow None
the BIG-IP blocksallservices and ports except a few hardcoded HA communication ports.
This means:
* UDP/161 (SNMP)is blocked
* UDP/162 (SNMP traps)is blocked
* The SNMP server cannot poll or receive data from the BIG-IP through this Self IP SNMP relies on access through the Self IP if out-of-band (mgmt interface) is not used.
Thus, the issue is directly caused byPort Lockdown = Allow None, which prevents SNMP communication.
Why the other options are incorrect:
B). Traffic Group must use a floating Traffic Group
* SNMP polling doesnotrequire floating Self IPs.
* Floating groups apply to HA failover IPs, not SNMP functionality.
C). VLAN/Tunnel must allow All VLANs
* Self IPs are always bound to a VLAN; SNMP doesnotrequire All VLANs.
* As long as the Self IP belongs to a reachable VLAN, SNMP can work.
D). Configuration is correct
* It is not correct:Allow Noneblocks SNMP and is the problem.
NEW QUESTION # 46
......
Validate your F5CAB1 Exam Preparation with F5CAB1 Practice Test: https://testking.itexamdownload.com/F5CAB1-valid-questions.html