TheService Check Datedetermines whether a particular software version is allowed to run under the device's license.
* When installing or upgrading TMOS, the installer checks theService Check Datestored in the BIG-IP license file.
* If the license date isolderthan the minimum required for the target version, the software installation is blocked.
* This check happensspecifically during a software install, not during routine device operations.
Editing virtual servers or system startup do not trigger this validation.
Thus, the enforcement happensduring software installation.

The BIG-IP has two distinct planes:
Management-plane -> handled entirely by the management interface (MGMT) Data-plane (TMM) -> handles Self IPs, VLAN interfaces, and traffic processing To capture traffic on the management interface, only the management-side NICs may be used:
mgmt -> Logical name for the management interface
eth0 -> Physical Linux interface mapped to the management port on most BIG-IP platforms Both of these correctly capture inbound/outbound WebUI (HTTPS/443) traffic on the management port.
Why the correct answers are A and B
A). tcpdump -i eth0 -n port 443
On BIG-IP appliances and VMs, the management port maps to eth0 at the Linux OS level.
Capturing on eth0 correctly shows HTTPS traffic to the WebUI.
B). tcpdump -i mgmt -n port 443
mgmt is the BIG-IP alias for the management interface.
This is the preferred and most explicit capture interface for management-plane packet captures.

Comprehensive and Detailed Explanation From BIG-IP Administration - Install, Initial Configuration, and Upgrade:
BIG-IP Self IP addresses have an associated Port Lockdown feature that governs which protocols and services are permitted to communicate directly with that Self IP. By default, Self IPs may allow broader access than desired, making Port Lockdown a critical hardening control.
The Allow Custom option under Port Lockdown is the precise mechanism for administrators who need granular, port-specific filtering. When selected, only the explicitly listed TCP/UDP ports are permitted - all others, including port 443 (HTTPS), are implicitly denied. This satisfies the requirement of blocking 443 specifically while preserving access on other required ports.
The remaining options are incorrect for this scenario:
* Option A references SSH access control under System > Platform, which governs management-plane SSH - not Self IP service filtering.
* Option B disables the entire Self IP, removing all traffic handling, which is operationally disruptive.
* Option D - Allow None - blocks all traffic to the Self IP, not selectively port 443.
The Allow Custom approach provides the surgical precision required: administrators enumerate permitted ports, and everything outside that list - including 443 - is dropped.
Reference Topics: Self IP Port Lockdown, Network Security Hardening, Self IP Configuration - BIG-IP Administration Study Guide.

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.

The exhibit shows the configuration of aSelf IPwith:
* Port Lockdown: Allow Custom
* ACustom Listthat 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?
FTP
TCP 21
Not listed
#Not allowed
SSH
TCP 22
Listed
#Allowed
Telnet
TCP 23
Not listed
#Not allowed
Thus,SSHis the only traffic permitted through this Self IP configuration.