Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
What command will allow the BIG-IP Administrator to view the configured management IP of a BIG-IP system?
(Choose one.)
Comprehensive and Detailed Explanation (Paraphrased)
The BIG-IP stores the configured management IP address as a system configuration object under the /sys hierarchy.
To display configured (persistent) values, BIG-IP uses the tmsh 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 the actual 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.
Refer to the exhibit.
What traffic will be permitted to reach the BIG-IP?
The exhibit shows the configuration of a Self IP with:
Port Lockdown: Allow Custom
A Custom List that 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, SSH is the only traffic permitted through this Self IP configuration.
The device is currently on v15.1.2.1.
The BIG-IP Administrator needs to boot the device back to v13.1.0.6 to gather data for troubleshooting.
The system shows:
Sys::Software Status
Volume Product Version Build Active Status Allowed
HD1.1 BIG-IP 15.1.2.1 0.0.10 yes complete yes
HD1.2 BIG-IP 13.1.0.6 0.0.3 no complete yes
Which is the correct command-line sequence to boot the device to version 13.1.0.6?
To change the boot volume on a BIG-IP system from one installed TMOS version to another, the correct CLI tool is:
switchboot
The correct syntax uses the -b flag:
switchboot -b <volume>
This command marks the specified boot location as the one to be used on the next reboot.
Thus, to boot into HD1.2 which contains 13.1.0.6, the sequence is:
Mark HD1.2 as the next boot location:
switchboot -b HD1.2
Reboot the system:
reboot
This is the standard and officially supported method for selecting a different installed volume.
Why the other options are incorrect:
A . 'tmsh reboot HD1.2'
There is no such tmsh syntax.
Boot volume cannot be selected by adding a parameter to reboot.
C . switchboot -I HD1.2
The -I flag is invalid. Only -b is used.
D . 'tmsh switchboot HD1.2'
switchboot is not a tmsh command; it is a system-level shell utility.
Therefore, Option B is the correct and valid command sequence.
A BIG-IP Administrator discovers malicious brute-force attempts to access the BIG-IP device on the management interface via SSH.
The administrator needs to restrict SSH access to the management interface.
Where should this be accomplished?
The BIG-IP management interface (MGMT port) is controlled through System 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 the management interface must be done under:
System Configuration Device General
Which corresponds to Option C.
How can the BIG-IP Administrator tell when an unlicensed module has been provisioned?
The BIG-IP system has built-in licensing enforcement.
If an administrator provisions a module that the device is not licensed to run, the system will still allow the provisioning action to occur initially, but the system detects the mismatch and displays an alert.
What actually happens:
The GUI places a warning banner in the upper-left corner labeled something similar to:
''Provisioning Warning''
This appears immediately after provisioning a module that is not included in the active license.
The system remains in an ''inconsistent state'' until the module is disabled again or the license is updated.
This is the visual cue BIG-IP uses to indicate that a module was provisioned without valid licensing.
Why the other options are incorrect:
A . ''A BIG-IP does not allow unlicensed modules to be provisioned.''
Not true. BIG-IP does allow provisioning, but warns afterward.
B . ''A warning will appear when provisioning an unlicensed module.''
The warning does not appear during the provisioning step itself.
It appears after provisioning, in the main GUI, as a system banner.
49 questions covering all exam domains, starting from $20
5 domains from the F5 Networks F5CAB1 exam outline, with approximate weightings. Every sample question above is tagged with the domain it comes from
This section evaluates how BIG-IP processes application traffic on the data plane, covering traffic flow, main data path elements, basic load balancing ideas, and how security and performance settings influence user traffic. Understanding these concepts forms the foundation for configuring and managing data plane behavior.
This section evaluates skills in setting up BIG IP components that define data plane behavior, including virtual servers, pools, nodes, monitors, and profiles. Proper configuration ensures that applications run stably and efficiently in line with design goals.
This section covers running the control plane where BIG IP is set up and managed, including handling user accounts, roles, device options, and configuration handling. It addresses using both the graphical interface and command line for everyday administration tasks.
This section evaluates finding and fixing frequent issues that impact BIG IP functionality, involving work with logs, statistics, diagnostic utilities, and troubleshooting practices. The goal is to restore healthy traffic flow and dependable application delivery.
This section covers the full lifecycle of putting a BIG IP system into service and keeping it current, including installation, initial configuration, licensing, basic networking setup, and planning and performing software updates and hotfixes.
Common questions about the exam itself
