Provisioning determines:
Which BIG-IP modules are enabled (LTM, ASM, APM, AFM, DNS, etc.)
Their provisioning levels (None, Minimal, Nominal, Dedicated)
Two accurate ways to view provisioning settings are:
A). GUI -- System -> Resource Provisioning -> Module Allocation
This is the primary GUI screen showing:
All modules
Their provisioning level
System resource distribution impact
Administrators commonly use this page to confirm or change module provisioning.
D). TMSH -- list /sys provision
This tmsh command displays each module and its provisioning level:
sys provision ltm { level nominal }
sys provision asm { level none }
...
This is the authoritative CLI method for checking module provisioning configurations.

BIG-IP licensing information, including theService Check Date, is stored in the file:
/config/bigip.license
This file contains all license attributes downloaded from the F5 licensing server, including:
* License key
* Licensed modules
* Useful life date
* Service check date
TheService Check Datedetermines whether the system is eligible for upgrades to specific TMOS versions.
When reviewing upgrade readiness, administrators extract this value directly from the license file with:
grep "Service check date" /config/bigip.license
Why the other options are incorrect:
* /config/bigip.confstores BIG-IP configuration objects, not license metadata.
* /config/svc_chk_date.datisnota valid file in the licensing system; it does not contain license parameters.
* /config/BigDB.datstores internal database values, not licensing attributes.
Thus, only thebigip.licensefile contains the correct licensing information required for verifying upgrade eligibility.

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?
Not allowed
FTP TCP 21 Not listed
Allowed
SSH TCP 22 Listed
Not allowed
Telnet TCP 23 Not listed
Thus, SSH is the only traffic permitted through this Self IP configuration.

To understand:
* Which modules are licensed
* Which modules are provisioned
* The resource requirements (CPU / RAM) of each module
The administrator uses:
System > Resource Provisioning
This page displays:
* All modules present in the license
* Whether they are enabled or disabled
* Required memory to activate each module
* CPU and disk allocation information
* Provisioning level options (None / Minimal / Nominal / Dedicated)
This is the exact location where BIG-IP administrators evaluate module capacity before enabling or purchasing licensing upgrades.
Why the other options are incorrect:
A). Configuration > OVSDB
* Used for network virtualization integrations, not licenses or modules.
B). Software Management
* Used for software image installation, not licensing.
C). Configuration > Device
* Displays hostname, failover settings, device properties - not module resource requirements.
Thus, module licensing and memory requirement data are found under Resource Provisioning .