F5CAB1 Exam Dumps : BIG-IP Administration Install, Initial Configuration, and Upgrade

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?

FTP

TCP 21

Not listed

Not allowed

SSH

TCP 22

Listed

Allowed

Telnet

TCP 23

Not listed

Not allowed

Thus, SSH is the only traffic permitted through this Self IP configuration.

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 .

BIG-IP licensing information, including the Service 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

The Service Check Date determines 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.conf stores BIG-IP configuration objects, not license metadata.

/config/svc_chk_date.dat is not a valid file in the licensing system; it does not contain license parameters.

/config/BigDB.dat stores internal database values, not licensing attributes.

Thus, only the bigip.license file contains the correct licensing information required for verifying upgrade eligibility.