Provisioning settings define which modules are enabled and how system resources are allocated to them.
These provisioning declarations are stored in:
/config/bigip.conf
This file contains:
Full module provisioning statements
TMSH-equivalent provisioning configurations such as:
sys provision ltm { level nominal }
sys provision asm { level nominal }
It is the primary system configuration file that stores all active provisioning details.

In BIG-IP, software images are installed on boot volumes (for example, HD1.1, HD1.2, HD1.3, etc.).
To install software on a new 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-volume keyword
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.

BIG-IP hardware platforms use chassis LEDs to indicate system health states.
A solid yellow status LED typically indicates a warning condition, such as:
A non-critical hardware alert
A temperature threshold nearing limit
A minor fan or sensor irregularity
Other non-fatal environmental or system conditions
This state reflects a warning-level alarm, meaning the unit is operational but requires investigation.

The exhibit shows the Current Resource Allocation for:
CPU
Disk
Memory
In particular, the Memory Allocation bar displays the modules that are currently provisioned.
Memory is the most reliable indicator because BIG-IP allocates memory only to modules that are actively provisioned.
From the exhibit:
MGMT (Management) - always present
TMM (Traffic Management Microkernel) - indicates LTM is provisioned
GTM - this label indicates that the DNS module is provisioned (GTM = Global Traffic Manager, now called DNS) APM - explicitly shown, indicating Access Policy Manager is provisioned Therefore, the provisioned modules are:
LTM (implied by TMM allocation)
DNS/GTM
APM
This matches Option C: LTM, DNS, APM.

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