Important F5 Networks F5CAB1 Exam Questions

Answer: C

Explanation:

The BIG-IP system has built-in licensing enforcement.

If an administrator provisions a module that the device is not licensed to run, the system will still allow the provisioning action to occur initially, but the system detects the mismatch and displays an alert.

What actually happens:

The GUI places a warning banner in the upper-left corner labeled something similar to:

''Provisioning Warning''

This appears immediately after provisioning a module that is not included in the active license.

The system remains in an ''inconsistent state'' until the module is disabled again or the license is updated.

This is the visual cue BIG-IP uses to indicate that a module was provisioned without valid licensing.

Why the other options are incorrect:

A . ''A BIG-IP does not allow unlicensed modules to be provisioned.''

Not true. BIG-IP does allow provisioning, but warns afterward.

B . ''A warning will appear when provisioning an unlicensed module.''

The warning does not appear during the provisioning step itself.

It appears after provisioning, in the main GUI, as a system banner.

Answer: B

Explanation:

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.''

Why the other options are incorrect:

A . Reboot into a new partition

No reboot occurs simply from uploading an image.

C . Copying into /var/local/images/

This directory is not used for ISO storage.

All valid images remain in /shared/images/.

Thus, the correct system action is checksum verification.

Answer: B

Explanation:

To identify which boot volume is currently active on a BIG-IP system, the correct command is:

tmsh show sys software status

This command displays:

All installed boot volumes (HD1.1, HD1.2, HD1.3, etc.)

The BIG-IP software version installed on each volume

The Active field, indicating which volume the system is currently booted from

The installation status (''complete'', ''in-progress'', ''allowed'')

This is the standard and authoritative way to determine the active boot location.

Why the other options are incorrect:

A . tmsh show sys version

Displays OS version, build, and date.

Does not show boot locations or which volume is active.

C . tmsh list sys software update

Shows software update configurations, not boot volume status.

Does not display which volume is active.

Answer: A

Explanation:

The screenshot shown is from the User Administration section of the BIG-IP GUI.

This section controls:

Root and Admin passwords

SSH Access

SSH IP Allow settings

However, it does not contain any controls for restricting access to the WebUI (TMUI).

BIG-IP does not provide TMUI access restrictions from this part of the GUI.

Access to the web-based Configuration Utility is controlled by the httpd allow list, configured through TMSH:

tmsh modify /sys httpd allow { <IP/subnet> }

This setting is not displayed in the User Administration panel, and in many BIG-IP versions, the httpd allow list is only configurable from the CLI, not the GUI.

Therefore, the administrator cannot find the setting in the screen shown because:

TMUI access restriction is not located in this GUI section

It must be configured using tmsh under /sys httpd allow

This is why Option A is correct.

Answer: A

Explanation:

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.