BIG-IP systems require all ISO images (base TMOS images and HotFix images) to be stored in a specific directory used for software installation:
/shared/images/
This directory:
Is the only supported location from which the BIG-IP software installation system validates and installs ISO files Is accessible by both the GUI and TMSH installers Has adequate storage space allocated specifically for images Is part of the shared partition that persists across reboots When transferring images via SCP, the administrator must copy them directly into
/shared/images/ so that:
The GUI (System Software Management Available Images) can detect the image TMSH install software image commands can reference it Other directories such as /local/images/ or /var/images/ are not valid storage paths for software images.

Within the BIG-IP Traffic Management Shell (tmsh), system configuration objects-including the management IP-are organized under the /sys hierarchy. The management IP address is a configurable property stored in the system configuration and can be viewed using the tmsh list command, which displays configuration objects and their currently assigned values.
Why "list /sys management-ip" is correct
* The list command in tmsh is used to display configured system values , not runtime statistics.
* The object that holds the management IP settings on BIG-IP systems is located at: /sys management-ip
* Running the command: list /sys management-ip will reveal the settings for the management IP interface, including the address, netmask, and any associated attributes.
* This is the standard method used during system setup and verification to confirm the management IP configuration.
This behavior aligns with BIG-IP administration procedures, where configuration information is retrieved using list , while operational data is retrieved using show .
Why the other options are incorrect
A). run /util bash ifconfig mgmt
* This command enters the Bash shell, then runs ifconfig to display the management interface.
* While this can show the management interface address, it is not a tmsh-native command , and the question specifically asks for a tmsh command.
* Administrators use tmsh directly for configuration display rather than leaving the shell.
C). show /sys management-ip
* The show command displays statistics or operational data , not configuration values.
* The management-ip object does not maintain statistics; therefore show does not return the configuration details required.
* Only the list command reveals stored configuration data such as IP address and netmask.

When you choose Automatic as the activation method in the License > Re-activate screen, the BIG-IP device itself contacts F5's license activation service over 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 the F5 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 of Automatic Activation.

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 .

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.