[Mar 05, 2026] F5 F5CAB1 Real Exam Questions and Answers FREE
Pass F5 F5CAB1 Exam Info and Free Practice Test
NEW QUESTION # 23
A BIG-IP Administrator needs to install a HotFix on a standalone BIG-IP device, which hasHD1.1as the Active Boot Location.
The administrator has already re-activated the license and created a UCS archive.
In which sequence should the administrator perform the remaining steps?
- A. Install HotFix in HD1.1, Reboot the BIG-IP device, Install UCS Archive
- B. Activate HD1.2, Install base Image in HD1.2, Install HotFix in HD1.2
- C. Install HotFix in HD1.2, Install base Image in HD1.2, Activate HD1.2
- D. Install base Image in HD1.2, Install HotFix in HD1.2, Activate HD1.2
Answer: D
Explanation:
When installing a HotFix on a BIG-IP device, F5 best practices require:
* Installing the base TMOS image on a new, unused boot volume (HD1.2)
* This ensures the upgrade happens on a clean volume.
* The existing active boot location remains untouched for rollback.
* Installing the HotFix onto the SAME new boot volume (HD1.2)
* HotFixes must be applied on top of a base version.
* They cannot be installed on an empty volume.
* They must match the base image version.
* Activating the new boot volume (HD1.2)
* The system reboots into the updated software stack.
* Activation happensafterbase + HotFix installation is complete.
This sequence is exactly shown inOption C:
Install base Image in HD1.2
Install HotFix in HD1.2
Activate HD1.2
Why the other options are incorrect:
A). Install HotFix before base image
* Impossible.
* HotFix requires an installed base version first.
B). Installing HotFix on HD1.1 (active boot volume)
* Not recommended.
* Upgrading in-place removes rollback safety.
* HotFix cannot be applied cleanly without applying base image first.
D). Activate HD1.2 before installing anything
* You cannot activate an empty boot volume.
* Activation only occurs after the base + HotFix software is installed.
NEW QUESTION # 24
The BIG-IP Administrator received a ticket that an authorized user is attempting to connect to the Configuration Utility from a jump host and is being denied.
The HTTPD allow list is configured as:
sys httpd {
allow { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
}
The jump host IP is172.28.32.22.
What command should the BIG-IP Administrator use to allow HTTPD access for this jump host?
- A. modify /sys httpd allow add { 172.28.32.22 }
- B. modify /sys httpd allow delete { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
- C. modify /sys httpd allow replace-all-with { 172.28.32.22 }
Answer: A
Explanation:
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 asingle host IPto the existing list.
* The object/sys httpd allowsupports actions such asadd,delete, andreplace-all-with.
* Because the goal is toaddone 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.
Why the other options are incorrect:
* Option A (replace-all-with)wouldoverwritethe entire allow list, removing existing permitted subnets- unacceptable.
* Option B (delete)wouldremovethe existing networks and not add the required host.
Therefore, the correct administrative action is toaddthe jump host's IP.
NEW QUESTION # 25
What will setting a Self IP to"Allow None"for Port Lockdown do?
- A. Block HA communications, causing the systems to report their peer as offline and go active-active.
- B. Default allow port 1026 access between peer devices and traffic processing across the network failover.
- C. Block HA communications, causing the systems to report their peer as online ready.
Answer: A
Explanation:
ThePort Lockdownfeature controls which services a Self-IP will respond to.
Setting a Self-IP toAllow Nonemeans:
* The Self-IP will not acceptanytraffic except the very limited, hard-coded HA ports such asTCP 4353 used for device trust and configuration sync.
* All other HA ports, including those needed for network failover and other HA mechanisms,are blocked.
When essential HA services cannot communicate, each device assumes its peer is down.
This results in:
* HA failover misbehavior
* Both devices thinking the other is offline
* Potentialactive-active condition, which is not intended and can cause traffic disruption Thus,Allow Nonecan break HA functionality unless the Self-IP is not used for HA links.
NEW QUESTION # 26
An F5 VE has been deployed into a VMware environment via an OVF file.
An administrator wants to configure the management IP address so the VE can be accessed for further setup.
Which two are valid methods for configuring the management-ip address? (Choose two.)
- A. Log into the remote console and configure the management IP through TMSH using:
create ltm management-ip <ip address>/<mask> - B. Log into the remote console and configure the management IP by running theconfigexecutable.
- C. Log into the remote console and configure the management IP by running thesetupcommand.
- D. Log into the remote console and configure the management IP through TMSH using:
create sys management-ip <ip address>/<mask>
Answer: B,D
Explanation:
A newly deployed BIG-IP Virtual Edition (VE) in VMware requires initial configuration of itsmanagement- ipaddress so it can be accessed over the network. F5 provides several valid mechanisms during initial console access:
A). Running the config utility
* The config script is available on new BIG-IP installations and VE deployments.
* It launches a guided text-based wizard allowing configuration of:
* Management IP
* Netmask
* Default route
* This is a standard and recommended method during first-time setup.
B). Using TMSH with create sys management-ip
* Administrators can enter TMSH directly from the console and run:
* create sys management-ip <ip>/<mask>
* The management-ip object resides undersys, not under ltm or any other module.
* This is the correct tmsh method for defining the management interface address.
Why the other options are incorrect:
C). create ltm management-ip
* There isnosuch object under /ltm.
* LTM handles traffic objects (virtual servers, pools), not system management interfaces.
D). Running the setup command
* The setup command is used for general system configuration butdoes not configure the management- ip.
* It is not the supported method for initial management IP assignment on VE deployments.
Therefore, the valid methods are running theconfigutility and using thesys management-ipcommand within TMSH.
NEW QUESTION # 27
The BIG-IP Administrator wants to manage the newly built F5 system through anin-band Self-IP.
The administrator has configured a VLAN and Self-IP and can ping the IP from their workstation, but cannot access the system viaSSHorHTTPS.
Whatport lockdownsettings should the BIG-IP Administrator use to allow management access on the Self-IP?
(Choose two.)
- A. The Self-IP port lockdown behavior could be adjusted toAllow Management
- B. The Self-IP port lockdown behavior could be adjusted toAllow Mgmt
- C. The Self-IP port lockdown behavior could be adjusted toAllow Default
- D. The Self-IP port lockdown behavior could be adjusted toAllow All
Answer: A,B
Explanation:
Self-IPs include a security feature calledPort Lockdown, which restricts which services respond on that Self- IP.
By default, Self-IPs block management access (SSH and HTTPS/TMUI), meaning an administrator cannot manage the device through in-band Self-IPs unless explicitly allowed.
Allow Mgmt / Allow Management
These settings enable only the management services required for administrative access, specifically:
* SSH (22)
* HTTPS/TMUI (443)
These options allow secure administration without opening unnecessary ports.
Why these are correct:
* They provide only the essential access for management.
* They follow F5 security best practices when using in-band admin access.
* They donotexpose all services, reducing the attack surface.
Why the other options are incorrect:
A). Allow Default
* This allows only a minimal set of system-required ports (e.g., failover, config sync), not SSH or HTTPS.
* Administrator access would still fail.
B). Allow All
* Opens all ports on the Self-IP, which isnot secure.
* Exposes services that should remain restricted.
Therefore,Allow Mgmt / Allow Managementare the correct choices.
NEW QUESTION # 28
A secondary administrator has been granted access to a BIG-IP device through itsManagement Interface, but is unable to access theConfiguration Utility (WebUI).
What command can be run from the CLI to capture the network traffic on themanagement interfaceand troubleshoot the issue?
(Choose two.)
- A. tcpdump -i mgmt -n port 443
- B. tcpdump -i eth0 -n port 443
- C. tcpdump -i management -n port 443
- D. tcpdump -i tun0 -n port 443
- E. tcpdump -i 0.0 -n port 443
Answer: A,B
Explanation:
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 toeth0at the Linux OS level.
* Capturing on eth0 correctly shows HTTPS traffic to the WebUI.
B). tcpdump -i mgmt -n port 443
* mgmtis the BIG-IP alias for the management interface.
* This is thepreferredand most explicit capture interface for management-plane packet captures.
Why the other options are incorrect:
C). tcpdump -i 0.0
* Interface0.0is the TMM switch interface used for data-plane packet captures.
* Itdoes NOTcapture management-plane traffic.
D). tcpdump -i tun0
* Used for tunnel interfaces (IPsec, VXLAN, etc.)
* Not related to management access.
E). tcpdump -i management
* There isnointerface named management on BIG-IP.
* The correct names are mgmt or eth0.
NEW QUESTION # 29
When using the tmsh shell of a BIG-IP system, which command will display the management-ip address?
- A. run /util bash ifconfig mgmt
- B. show /sys management-ip
- C. list /sys management-ip
Answer: C
Explanation:
Comprehensive and Detailed Explanation (Paraphrased from F5 BIG-IP Administration / Installation / Initial Configuration concepts) Within the BIG-IP Traffic Management Shell (tmsh), system configuration objects-including the management IP-are organized under the/syshierarchy. The management IP address is a configurable property stored in the system configuration and can be viewed using the tmshlistcommand, which displays configuration objects and their currently assigned values.
Why "list /sys management-ip" is correct
* The list command in tmsh is used todisplay configured system values, not runtime statistics.
* The object that holds the management IP settings on BIG-IP systems is located at:/sys management-ip
* Running the command:list /sys management-ipwill reveal the settings for the management IP interface, including the address, netmask, and any associated attributes.
* This is the standard method used during system setup and verification to confirm the management IP configuration.
This behavior aligns with BIG-IP administration procedures, where configuration information is retrieved usinglist, while operational data is retrieved usingshow.
Why the other options are incorrect
A). run /util bash ifconfig mgmt
* This command enters the Bash shell, then runs ifconfig to display the management interface.
* While this can show the management interface address, it isnot a tmsh-native command, and the question specifically asks for a tmsh command.
* Administrators use tmsh directly for configuration display rather than leaving the shell.
C). show /sys management-ip
* The show command displaysstatistics or operational data, not configuration values.
* The management-ip object does not maintain statistics; therefore show does not return the configuration details required.
* Only thelistcommand reveals stored configuration data such as IP address and netmask.
NEW QUESTION # 30
A BIG-IP Administrator upgrades the BIG-IP LTM to a newer software version. After the administrator reboots into the new volume, the configuration fails to load.
Why is the configuration failing to load?
- A. The license needed to be reactivated before the upgrade.
- B. The upgrade was performed on the standby unit.
- C. A minimum of at least two reboots is required.
- D. Connectivity to the DNS server failed to be established.
Answer: A
Explanation:
When upgrading to a newer TMOS software version, BIG-IP validates whether the current license is permitted to run that version.
This is controlled by theService Check Datein the device's license file.
If the Service Check Date is older than the minimum required for the target version:
* The systemboots into the new volume,
* Butfails to load the configuration,
* And will instead present messages indicating that the configuration cannot be applied due to aninvalid or outdated license.
This is a well-known behavior:
An outdated license, not reactivated before upgrade, causes configuration load failure after reboot into the new software.
Why the other options are incorrect:
A). Performed on the standby unit
* Upgrading a standby unit does not cause configuration load failure.
* Standby-only upgrades are standard best practice.
C). Two reboots required
* BIG-IP does not require two reboots during an upgrade.
* One reboot into the new volume is sufficient.
D). DNS connectivity failure
* DNS connectivity does not affect configuration loading.
* DNS is only needed for automatic license activation, not for applying config at boot.
Thus, the configuration failed to load because thelicense was not reactivated before the upgrade, making Option Bcorrect.
NEW QUESTION # 31
A BIG-IP Administrator plans to upgrade a BIG-IP device to the latest TMOS version.
Which two tools could the administrator leverage to verify known issues for the target versions? (Choose two.)
- A. F5 Bug Tracker
- B. F5 End User Diagnostics (EUD)
- C. F5 iHealth
- D. F5 Downloads
- E. F5 University
Answer: A,C
Explanation:
Comprehensive and Detailed Explanation (Paraphrased from F5 BIG-IP Administration Install, Initial Configuration, and Upgrade concepts) When performing a TMOS upgrade, F5 recommends validating the target software version to ensure that the release does not contain defects that may impact system behavior. The upgrade preparation process includes checking for known issues, validating compatibility, and reviewing advisory information for the intended version. Two primary F5 tools serve this purpose:
B). F5 iHealth
iHealth is a cloud-based diagnostic and analysis platform used to evaluate the operational state of a BIG-IP system.
Administrators upload a QKView file to iHealth to receive an automated assessment of the system. As part of upgrade planning, iHealth provides:
* Version-specific issue analysis, comparing the system's configuration and hardware against F5's internal catalog of published issues.
* Upgrade advisories, identifying potential risks such as deprecated features, module compatibility concerns, or changes in behavior between TMOS versions.
* Checks against known defects, allowing administrators to determine whether the target TMOS version contains issues relevant to their deployment.
This aligns with F5's recommended upgrade workflow, where iHealth is used before upgrading to confirm system readiness and detect software-level concerns.
D). F5 Bug Tracker
The Bug Tracker is F5's dedicated interface for reviewing software defects across TMOS releases.
It enables administrators to:
* Search forknown bugs by TMOS version, module, severity, or defect ID.
* Review thestatus of defects(open, resolved, fixed in later releases).
* Identify whether high-impact or security-related issues are associated with the target upgrade version.
F5 documentation emphasizes reviewing known defects prior to installation of new software images, making the Bug Tracker a critical resource for upgrade validation.
Why the other options are not correct
A). F5 End User Diagnostics (EUD)
EUD is used exclusively forhardware diagnostics(ports, memory, fans). It does not provide software-related issue verification and is not used for upgrade planning.
C). F5 University
This is atraining platform, not an operational tool. It does not provide defect listings or upgrade-specific warnings.
E). F5 Downloads
Although it provides access to software images and release notes, it isnot a tool for identifying known bugs.
Release notes summarize general fixes and features, but systematic bug verification requires iHealth or the Bug Tracker.
NEW QUESTION # 32
A BIG-IP device will be dedicated to functioning as a WAF, requiring only theASMmodule to be provisioned.
What provisioning level will ensure that the system allocatesall CPU, memory, and disk resourcesto this module exclusively?
- A. Dedicated
- B. Maximal
- C. Nominal
- D. Comprehensive
Answer: A
Explanation:
Provisioning defines how BIG-IP allocates system resources to modules. The provisioning levels include:
* Dedicated- allocatesallCPU, memory, and disk resources to a single module
* Nominal- standard resource allocation balanced with other modules
* Minimal- lowest level, used for basic utility needs
* None- module disabled
* Comprehensive / Maximal- not valid TMOS provisioning levels
Why "Dedicated" is correct
When a BIG-IP device is intended to runonly ASM(Web Application Firewall), the recommended way to maximize performance is to provision the module atDedicatedlevel.
WithASM: Dedicated:
* ASM receives theentire hardware capacity
* No other modules can or should be provisioned
* This is explicitly recommended when a device is used solely as a WAF platform Why other options are incorrect B). Comprehensive / C. Maximal
* These arenot valid provisioning modesin BIG-IP.
* TMOS supports: Nominal, Minimal, Large (module-specific), and Dedicated.
D). Nominal
* Shares resources with other modules
* Does not provide full system performance
* Not suitable when exclusive resource allocation is required
Thus,Dedicatedis the correct provisioning choice.
NEW QUESTION # 33
A BIG-IP Administrator discovers malicious brute-force attempts to access the BIG-IP device on the management interfacevia SSH.
The administrator needs to restrict SSH access to the management interface.
Where should this be accomplished?
- A. Network > Self IPs
- B. Network > Interfaces
- C. System > Configuration
- D. System > Platform
Answer: C
Explanation:
The BIG-IPmanagement interface (MGMT port)is controlled throughSystem settings, not through the Network menu.
SSH access on the management interface is configured here:
System # Configuration # Device # General # SSH Access / SSH IP Allow
This section allows the administrator to:
* Enable or disable SSH service
* Restrict SSH access to specific IP addresses or subnets
* Apply security policies to the management interface
Why the other options are incorrect:
A). Network > Interfaces
* Used for data-plane physical interface settings, not management plane SSH restrictions.
B). Network > Self IPs
* Controls in-band management or data-plane access, not the dedicated management port.
D). System > Platform
* Used for hostname, time zone, LCD contrast, hardware settings - not SSH security on the management port.
Therefore, restricting SSH access to themanagement interfacemust be done under:
#System # Configuration # Device # General
Which corresponds toOption C.
NEW QUESTION # 34
A BIG-IP device is licensed forLTM, ASM, APM, and AFM.
Currently, it will only be used forload balancingandweb application firewalling.
To ensure optimal performance and efficient resource utilization, which of the following module provisioning combinations is the best choice?
- A. LTM: Dedicated
ASM: Dedicated
APM: Minimal
AFM: Minimal - B. LTM: Nominal
ASM: Nominal
APM: None
AFM: None - C. LTM: Nominal
ASM: Nominal
APM: Minimal
AFM: Minimal - D. LTM: Dedicated
ASM: Dedicated
APM: None
AFM: None
Answer: B
Explanation:
BIG-IP provisioning determines how CPU, memory, and disk resources are allocated to each module. The goal is to provision only the modules required and at levels appropriate to their performance needs.
Requirements in the question
The device will be used for:
* LTM(Local Traffic Manager) # load balancing
* ASM(Application Security Manager) # WAF
No functions require:
* APM (Access Policy Manager)
* AFM (Advanced Firewall Manager)
Why Option C is correct
Provisioning bothLTMandASMatNominallevel provides:
* Adequate performance for production load
* Plentiful system resources while avoiding dedicating the entire system to a single module
* Balanced allocation without starving memory or CPU
SettingAPM: NoneandAFM: Noneensures unused modules consume zero resources.
Why the other options are incorrect
A). Dedicated provisioning for both LTM and ASM
* Two modules cannot both run in "Dedicated" mode.
* Dedicated mode allocatesallresources to a single module - the second module cannot be dedicated simultaneously.
B). LTM and ASM both Dedicated
* Same issue: only one module can be Dedicated at a time.
* Also unnecessary for load balancing + WAF.
D). Setting APM and AFM to Minimal
* Minimal still consumes memory and CPU.
* Unused modules should be set toNone.
Therefore,Option Cis the best provisioning strategy.
NEW QUESTION # 35
A BIG-IP Administrator needs to install aHotFixon a standalone BIG-IP device.
The device currently hasHD1.1as the Active Boot Location.
The administrator has already reactivated the license and created a UCS archive.
In which sequence should the administrator perform theremaining steps?
- A. Install HotFix in HD1.1, Reboot the BIG-IP device, Install UCS Archive
- B. Activate HD1.2, Install base Image in HD1.2, Install HotFix in HD1.2
- C. Install HotFix in HD1.2, Install base Image in HD1.2, Activate HD1.2
- D. Install base Image in HD1.2, Install HotFix in HD1.2, Activate HD1.2
Answer: D
Explanation:
When installing a software upgrade with a HotFix on BIG-IP, the correct workflow requires:
* Install the base TMOS imageon an unused boot volume
* Install the corresponding HotFixonto that same boot volume
* Activate the updated boot volumeto boot into the new software
This method ensures:
* The existing active system (HD1.1) is untouched
* The upgrade occurs in a new, clean volume (HD1.2)
* The HotFix applies properly to the same base image
* The administrator can revert to HD1.1 if issues occur
OptionCmatches the correct F5 upgrade sequence:
1. Install base image on HD1.2
2. Install HotFix on HD1.2
3. Activate HD1.2
Why the other options are incorrect:
A). Install HotFix before base image
* HotFixes must be appliedafterthe base image; not valid.
B). Installing a HotFix on the active boot location (HD1.1)
* Not recommended and does not use a clean new volume.
* Also does not involve installing the base image.
D). Activating HD1.2 before installing anything
* Cannot activate an empty or invalid boot volume.
Thus,Option Cis the correct sequence.
NEW QUESTION # 36
What are the two options for securing a BIG-IP's management interface?
(Choose two.)
- A. Block all management-interface administrative HTTPS and SSH service ports to prevent access.
- B. Restrict administrative HTTPS and SSH access to specific IP addresses or IP ranges.
- C. Limiting network access through the management interface to a trusted/secured network VLAN.
- D. Use the BIG-IP's Self-IP addresses for administrative access rather than the management interface.
Answer: B,C
Explanation:
Securing the BIG-IP management interface is a fundamental administrative responsibility. F5 best practices emphasize restricting who can reach the management port and ensuring that only authorized systems are allowed access.
A). Limiting management access to trusted network segments
F5 recommends placing the management interface on adedicated, isolated, and secured management network or VLAN, rather than exposing it to production or untrusted networks.
This reduces the attack surface by ensuring only trusted segments have visibility to administrative interfaces.
D). Restricting management access by IP or subnet
F5 BIG-IP uses the/sys httpd allowlist (for HTTPS) and configuration options insshd(for SSH) to control which IP addresses or subnets can access the device.
By specifying only known administrative IPs or ranges, unauthorized users cannot reach the login services.
Why the other options are incorrect
B). Blocking all management HTTPS/SSH ports
* This would prevent any administrative access and is not a viable security practice.
C). Using Self-IP addresses for administrative access
* F5 explicitly warns against using Self-IPs for management access unless strictly necessary.
* Self-IPs are exposed to the data plane and should not be used as the primary administrative interface.
NEW QUESTION # 37
The BIG-IP Administrator uses Secure Copy Protocol (SCP) to upload a TMOS image to the/shared/images/ directory in preparation for a TMOS upgrade.
After the upload is completed, what will the system dobeforethe image is shown in the GUI under:
System » Software Management » Image List?
- A. The system copies the image to /var/local/images/
- B. The system verifies the internal checksum
- C. The system performs a reboot into a new partition
Answer: B
Explanation:
When a TMOS image (.iso file) is uploaded into the/shared/images/directory, the BIG-IP performs an internal validation step before the ISO appears in the GUI.
1. The system verifies the internal checksum
* BIG-IP automatically reads the embedded checksum inside the ISO file
* Verifies integrity of the uploaded image
* Confirms the file is not corrupted or incomplete
* Ensures the image is a valid F5 TMOS software image
Only after this checksum verification succeeds does the image appear under:
System # Software Management # Image List
Why the other options are incorrect:
A). The system performs a reboot into a new partition
* Uploading an ISO file never triggers a reboot.
C). The system copies the image to /var/local/images/
* All valid TMOS images remain in/shared/images/.
* No copying occurs.
NEW QUESTION # 38
Which two items demonstrate thecreation of a new volumefor software images?
(Choose two.)
- A. tmsh install sys software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume
- B. tmsh install software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume
- C. Using the GUI, go toSystem > Disk Management, selectNew Volume. In the pop-up window, type the name or number of the new volume and clickApply.
- D. tmsh install /sys software image BIGIP-<version>.iso volume HD1.5 create-volume
- E. Using the GUI, go toSystem > Software Management > Available Images > Install, and in the Install Software Image pop-up window, type the new volume name or number and clickInstall.
Answer: B,C
Explanation:
In BIG-IP, software images are installed onboot volumes(for example, HD1.1, HD1.2, HD1.3, etc.).
To install software on anew volume, the administrator must instruct the system to create a new boot location before installation.
There are two correct ways to create a new volume:
A). tmsh command (with correct syntax)
tmsh install software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume This syntax correctly includes:
* install software image
* full path to ISO (/shared/images/...)
* volume name (HD1.5)
* create-volumekeyword
This instructs BIG-IP to create the new boot volume as part of the installation.
C). Using the GUI # System > Disk Management
From the Disk Management menu, the administrator can:
* Select "New Volume"
* Enter the volume identifier (e.g., HD1.5)
* Apply changes
This GUI method is officially supported and explicitly creates a new boot volume before installing the software.
Why the other options are incorrect:
B). Incorrect tmsh syntax
* Missing /shared/images/ path
* Incorrect command structure
D). Incorrect command structure
* Missing required keywords and correct command hierarchy
E). Software Management # Install does NOT create volumes
* This installs to anexistingvolume only
* The GUI install dialog does not create new boot volumes
Thus, onlyOption AandOption Cproperly create a new software volume.
NEW QUESTION # 39
A BIG-IP Administrator needs to purchase new licenses for a BIG-IP appliance.
The administrator needs to know:
* Whether a module is licensed
* The memory requirement for that module
Where should the administrator view this information in theSystem menu?
- A. Software Management
- B. Configuration Device
- C. Resource Provisioning
- D. Configuration OVSDB
Answer: C
Explanation:
To understand:
* Which modules arelicensed
* Which modules areprovisioned
* Theresource requirements(CPU / RAM) of each module
The administrator uses:
System Resource Provisioning
This page displays:
* All modules present in the license
* Whether they are enabled or disabled
* Required memory to activate each module
* CPU and disk allocation information
* Provisioning level options (None / Minimal / Nominal / Dedicated)
This is the exact location where BIG-IP administrators evaluate module capacity before enabling or purchasing licensing upgrades.
Why the other options are incorrect:
A). Configuration OVSDB
* Used for network virtualization integrations, not licenses or modules.
B). Software Management
* Used for software image installation, not licensing.
C). Configuration Device
* Displays hostname, failover settings, device properties - not module resource requirements.
Thus, module licensing and memory requirement data are found underResource Provisioning.
NEW QUESTION # 40
The BIG-IP Administrator needs to update access to the Configuration Utility to include the172.28.31.0/24and
172.28.65.0/24networks.
From the TMOS Shell (tmsh), which command should the BIG-IP Administrator use to complete this task?
- A. modify /sys httpd allow add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
- B. modify /sys httpd allow add { 172.28.31.0 172.28.65.0 }
- C. modify /sys httpd permit add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 }
Answer: A
Explanation:
Access to the BIG-IP Configuration Utility (TMUI) is controlled through the/sys httpd allowlist.
This list defines which IP addresses or subnets are allowed to connect to the management web interface.
To allow two new subnets-172.28.31.0/24and172.28.65.0/24-the administrator mustaddboth subnets to the existing list without removing current entries.
In tmsh, subnet entries must be specified innetwork/netmask format, for example:
172.28.31.0/255.255.255.0
The correct tmsh command to append these networks is:
modify /sys httpd allow add { 172.28.31.0/255.255.255.0 172.28.65.0/255.255.255.0 } Why the other options are incorrect:
Option B:
* IPs are listed without masks, which is invalid for subnet-based access control.
* The system requiresnetwork/netmaskformat.
Option C:
* The command uses permit instead of allow, which is not a valid attribute of /sys httpd.
* The correct keyword must beallow.
Thus, onlyOption Acorrectly adds both permitted subnets in the proper tmsh format.
NEW QUESTION # 41
......
Latest F5CAB1 Exam Dumps F5 Exam: https://www.freecram.com/F5-certification/F5CAB1-exam-dumps.html
New 2026 Latest Questions F5CAB1 Dumps - Use Updated F5 Exam: https://drive.google.com/open?id=14pnyn_tWqligIzBa7JrKzRmFdIuHeaUr