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.

The Configuration utility is the primary interface used for configuring the BIG-IP system, accessible via a web browser.

The HTTPD allow list controls which IP addresses or subnets may access the Configuration Utility (TMUI) on the BIG-IP system. The Administrator already has two subnets allowed and needs to add a single host IP to the existing list.
The object /sys httpd allow supports actions such as add, delete, and replace-all-with.
Because the goal is to add one more entry without removing the existing permitted subnets, the correct command is:
modify /sys httpd allow add { 172.28.32.22 }
This appends the new host to the existing list while preserving the previously configured networks.

License reactivation updates the BIG-IP device's license file to ensure:
* TheService Check Dateis current
* The device is eligible to install the intended TMOS version
* Any module entitlement updates are received
Reactivationdoes not interrupt trafficand does not require a reboot, making it safe to performbeforethe maintenance window.
F5 best practices state:
* Performall non-impact tasks priorto the scheduled maintenance window
* Leave the window available for activities that require rebooting, such as the software installation itself Since license reactivation isnon-disruptive, it should be donebeforethe upgrade window starts.

When a TMOS ISO file is transferred to /shared/images/, the BIG-IP automatically performs a validation step:
Checksum Verification
Before the image becomes visible in the GUI, the system verifies the internal checksum embedded inside the ISO.
This ensures:
The file was fully transferred
The image is not corrupted
It matches the official F5 release signature
Only after passing this verification does the GUI display the ISO under "Available Images."