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?
Correct Answer:
B
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 B correct.
How should a BIG-IP Administrator check the provisioned CPU percent for a module?
(Choose two.)
Correct Answer:
CD
BIG-IP allocates CPU and memory resources based on module provisioning levels.
To view how much CPU a module is assigned, administrators must check provisioning information
from:
* C . GUI --- System Resource Provisioning
This page visually displays CPU allocation via color-coded bars.
Hovering over the CPU bar shows:
CPU usage percent per module
Which modules share CPU cycles
The system's total resource allocation
This is the primary GUI method.
* D . tmsh show /sys provision
This command displays detailed module provisioning information including:
Provisioned modules
Their provisioning level
CPU and memory allocation data
It is the authoritative CLI method for resource provisioning status.
Why the other options are incorrect:
* A . top
Shows real-time process usage, not provisioned CPU allocation.
* B . tmsh show /sys cpu
Displays CPU runtime utilization, not per-module provisioning.
* E . Statistics Dashboard
Only shows traffic / system runtime metrics, not provisioning resource allocations.
Therefore, C and D are correct.
For security reasons, a BIG-IP Administrator needs to specify allowable IP ranges for access to the Configuration Utility (WebUI).
The exhibit shows the User Administration section of the Configuration Utility.
The administrator could not find any setting that explicitly restricts access to the Configuration Utility. Which one of the following is a reason for that?
Correct Answer:
A
The screenshot shown is from theUser Administrationsection of the BIG-IP GUI. This section controls:
Root and Admin passwords
SSH Access
SSH IP Allow settings
However,it does not contain any controls for restricting access to the WebUI (TMUI).
BIG-IP does not provide TMUI access restrictions from this part of the GUI.
Access to the web-based Configuration Utility is controlled by thehttpd allow list, configured through TMSH:
tmsh modify /sys httpd allow {
This setting is not displayed in the User Administration panel, and in many BIG-IP versions, the httpd allow list isonly configurable from the CLI, not the GUI.
Therefore, the administrator cannot find the setting in the screen shown because:
TMUI access restriction isnotlocated in this GUI section
It must be configured usingtmshunder/sys httpd allow
This is why Option A is correct.
