F5CAB1 Install, Initial Configuration, and Upgrade Practice Question
An administrator is preparing to install a new BIG-IP appliance in a data center where the management network does not have a DHCP server. The administrator connects to the console and completes the initial configuration. Which action must be taken to ensure the BIG-IP is reachable on the management network after the initial setup?
⚠ Common exam trap
The trap here is assuming that the management interface can use a self IP or VLAN group, when it actually requires a dedicated management IP configuration.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Assign a management IP address, netmask, and default gateway using the console configuration utility or tmsh.
In a network without DHCP, the management interface must be manually configured with a static IP address, netmask, and default gateway. This is accomplished during the initial console setup or later via tmsh. Without this step, the BIG-IP cannot be reached on the management network, preventing remote administration and further configuration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Assign a management IP address, netmask, and default gateway using the console configuration utility or tmsh.
Why this is correct
When no DHCP server is available, the administrator must manually configure the management IP address, netmask, and default gateway on the management interface. This is done through the console setup utility or tmsh commands like create sys management-ip. This ensures the BIG-IP is reachable on the management network for further configuration and administration.
- ✗
Enable the DHCP client on the management interface with a static fallback address.
Why it's wrong here
The BIG-IP management interface does not support a DHCP client with static fallback in the way described. While DHCP can be used, there is no automatic fallback to a static address if DHCP fails. In an environment without DHCP, the administrator must manually configure a static management IP. Enabling a DHCP client without a server would leave the interface without an address.
- ✗
Create a VLAN group that includes the management interface and assign an IP address to it.
Why it's wrong here
VLAN groups are used to aggregate multiple interfaces for redundancy or load balancing, but they are not used for the management interface. The management interface operates independently and does not participate in VLAN groups. Assigning an IP to a VLAN group would not provide management access and is not a supported configuration for the management port.
- ✗
Configure a self IP on the management VLAN using the tmsh command create net self.
Why it's wrong here
Self IPs are used for VLAN traffic and are typically configured on internal or external VLANs, not the management interface. The management interface requires a management IP address, not a self IP. Using create net self would not provide management access and could cause routing conflicts. The correct method is to assign a management IP address via the console setup or tmsh management-ip commands.
Visual reference
About these practice questions
Courseiva writes every F5CAB1 question from scratch — 80 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official F5 exam blueprint
This F5CAB1 practice question is part of Courseiva's free F5 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the F5CAB1 exam.